Re: [HACKERS] string_to_array with empty input

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: justin <justin(at)emproshunts(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)enterprisedb(dot)com>, Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] string_to_array with empty input
Date: 2009-04-01 17:23:18
Message-ID: B30A76B4-3912-4125-BADD-B2ABA1ABEC5C@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Apr 1, 2009, at 10:05 AM, justin wrote:

> string_to_array('',',')::INT[] works as proposed
>
> But
> string_to_array(',,,', ',' )::INT[] Fails
> or
> string_to_array('1,2,,4', ',' )::INT[] Fails .
>
>
> I'm trying to understand the difference between a empty string to a
> string with many blank entries between the delimiter.
> Consider ',,,,,,' = '' once the delimiter is removed . Yet
> Seven zero length entries were passed. How is that going to be
> handled????

Right, it's making a special case of '', which does seem rather
inconsistent to me.

Best,

David

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Aleksey Tsalolikhin 2009-04-01 17:58:28 Re: SELinux problem rsync'ing WAL logs
Previous Message David E. Wheeler 2009-04-01 17:20:28 Re: [HACKERS] string_to_array with empty input

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-04-01 17:36:40 Re: More message encoding woes
Previous Message David E. Wheeler 2009-04-01 17:20:28 Re: [HACKERS] string_to_array with empty input