what is good solution for support NULL inside string_to_arrayfunction?
in [PgSql]
|
Prev: [HACKERS] what is good solution for support NULL inside string_to_array function?
Next: what is good solution for support NULL inside string_to_array function?
From: Josh Berkus on 3 May 2010 20:55 > quietly removing NULL is maybe good for compatibility but is wrong for > functionality. I agree. I wasn't aware of this little misfeature. Default display for NULL should be a zero-length string. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Andrew Dunstan on 3 May 2010 23:18 Tom Lane wrote: >> Default display for NULL should be a zero-length string. >> > > That's just as broken as Pavel's suggestion. Unless you have something > that is guaranteed distingishable from the output of any non-null value, > you really can't make a significant improvement here. > > > Right. This is the problem we solved in CSV processing by distinguishing between quoted and unquoted values that could be null - the CSV rule is that a null value isn't quoted. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Steve Crawford on 7 May 2010 13:53
Tom Lane wrote: > Josh Berkus <josh(a)agliodbs.com> writes: > >>> quietly removing NULL is maybe good for compatibility but is wrong for >>> functionality. >>> > > >> I agree. I wasn't aware of this little misfeature. >> > > >> Default display for NULL should be a zero-length string. >> > > That's just as broken as Pavel's suggestion. Unless you have something > that is guaranteed distingishable from the output of any non-null value, > you really can't make a significant improvement here. > > regards, tom lane > > Is this, perhaps, a generalized case of this long-running discussion from last year?: http://archives.postgresql.org/pgsql-hackers/2009-03/msg01350.php Cheers, Steve -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |