From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Markus Bertheau ☭ <twanger(at)bluetwanger(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: quote_boolean() and friends missing |
Date: | 2005-06-20 14:01:20 |
Message-ID: | 2081.1119276080@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Markus Bertheau =?UTF-8?Q?=E2=98=AD?= <twanger(at)bluetwanger(dot)de> writes:
> I'm writing an application with a lot of PL/pgSQL and am constructing
> SQL queries on the fly. The quote_literal() and quote_ident() functions
> proved very much needed. Similarly, I need functions that return the SQL
> representation of all the other datatypes, not just TEXT: quote_boolean
> (), quote_date() and so on. For the sake of completeness I think these
> functions should exist. While the use of to_char() resp. decode() for
> some types is possible, it does feel like a workaround to me. Opinions?
> Do these functions belong in the PostgreSQL core?
What exactly do you think they would do? There is no analogy to
inserting escape characters for those other datatypes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Bertheau ☭ | 2005-06-20 14:05:28 | Re: quote_boolean() and friends missing |
Previous Message | Tom Lane | 2005-06-20 13:35:52 | Re: [PATCHES] default database creation with initdb |