| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Brendan Jurd" <direvus(at)gmail(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: quote_literal with NULL |
| Date: | 2007-10-10 15:12:31 |
| Message-ID: | 470CA58F.EE98.0025.0@wicourts.gov |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
>>> On Wed, Oct 10, 2007 at 4:57 AM, in message
<37ed240d0710100257r149a8d2cmb671b69a1673eb54(at)mail(dot)gmail(dot)com>, "Brendan Jurd"
<direvus(at)gmail(dot)com> wrote:
> On 10/10/07, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> On Wed, 2007-10-10 at 14:57 +1000, Brendan Jurd wrote:
>>
>> > Wouldn't it be more useful if quote_literal(NULL) yielded the text value
> 'NULL'?
>>
>> I don't think you can change that now. There could be code out there
>> that relies on that behaviour.
>>
>
> Bummer. But I take your point. If there's a good chance someone is
> going to have their application murdered by a change here, best to
> leave it alone.
In particular, it seems like exactly what you would want for values
you're going to use in an INSERT or the SET clause of an UPDATE.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-10-10 15:14:20 | Re: Timezone database changes |
| Previous Message | Tom Lane | 2007-10-10 15:04:53 | Re: Skytools committed without hackers discussion/review |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-10-10 15:55:20 | Re: quote_literal with NULL |
| Previous Message | Tom Lane | 2007-10-10 13:33:42 | Re: Preliminary patch for tsearch example dictionaries/parsers in contrib |