Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Dealing with table names in functions


  • From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
  • To: Jim Nasby <decibel(at)decibel(dot)org>
  • Cc: "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org>
  • Subject: Re: Dealing with table names in functions
  • Date: Thu, 22 Mar 2007 09:40:10 -0400
  • Message-id: <20070322134010(dot)GC4102(at)alvh(dot)no-ip(dot)org>

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.



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group