| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Broken handling of NULLs in TG_ARGV |
| Date: | 2015-05-01 21:27:58 |
| Message-ID: | 5543EFDE.5060000@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/30/15 6:44 PM, Tom Lane wrote:
> There isn't any such thing as a genuine SQL NULL argument; the examples
> you provided are just text strings, not SQL NULLs. In order to make them
> be actual nulls, we would have to redefine the arguments as being
> expressions of some sort, which is problematic for backwards-compatibility
> reasons. It also seems like rather a lot of new mechanism to add for
> something with (evidently) near-zero user demand.
Ahh, I thought the array started life as an actual array, not char **.
So yeah, not nearly as easy to fix. :(
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-05-01 21:36:31 | Re: CTE optimization fence on the todo list? |
| Previous Message | Peter Geoghegan | 2015-05-01 21:07:06 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |