Re: Dealing with table names in functions - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Dealing with table names in functions
Date
Msg-id 20070322134010.GC4102@alvh.no-ip.org
Whole thread Raw
In response to Dealing with table names in functions  (Jim Nasby <decibel@decibel.org>)
Responses Re: Dealing with table names in functions  (Reece Hart <reece@harts.net>)
List pgsql-general
Jim Nasby wrote:
> Is there a safe way to deal with tables being passed into a function,
> specifically in terms of what schema they're in? I can just blindly
> accept a text string and hope that it's always evaluated in the
> correct search_path context, but that doesn't seem so good. OTOH, if
> I accept an OID, there's no great way to pass that to most of the
> rest of the system... I can cast the OID to regclass, but that
> doesn't get me a fully-qualified name.

Pass the optionally qualified name and cast it to regclass.  It will
work correctly when the name is not qualified, applying search_path, and
it will also work when the name is qualified.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-general by date:

Previous
From: "Andy Dale"
Date:
Subject: xpath_list() function
Next
From: Magnus Hagander
Date:
Subject: Re: to_tsvector in 8.2.3