From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Brendan Jurd <direvus(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add function for quote_qualified_identifier? |
Date: | 2007-09-14 17:43:10 |
Message-ID: | 200709141743.l8EHhA418806@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---------------------------------------------------------------------------
Brendan Jurd wrote:
> Hi hackers,
>
> I note that we currently expose the usefulness of the quote_identifier
> function to the user with quote_ident(text).
>
> Is there any reason we shouldn't do the same with quote_qualified_identifier?
>
> We could just add a quote_qualified_ident(text, text) ... it would
> make forming dynamic queries more convenient in databases that use
> multiple schemas.
>
> Clearly a DBA could just create this function himself in SQL (and it
> wouldn't be difficult), but is that a good reason not to have it in
> our standard set of functions?
>
> Would be happy to cook up a patch for this.
>
> Cheers,
> BJ
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-09-14 17:50:16 | Re: PL/TCL Patch to prevent postgres from becoming multithreaded |
Previous Message | Tom Lane | 2007-09-14 17:38:22 | Re: invalidly encoded strings |
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-09-14 17:50:16 | Re: PL/TCL Patch to prevent postgres from becoming multithreaded |
Previous Message | Tom Lane | 2007-09-14 17:38:22 | Re: invalidly encoded strings |