Re: [HACKERS] More char()/ascii()

2008-02-20 Thread Tom Lane
Gregory Stark <[EMAIL PROTECTED]> writes: > "Andrew Dunstan" <[EMAIL PROTECTED]> writes: >> Fixing it would be trivial, I'm sure, but is it really a problem? > The "char" data type which I was mistakenly using is enough of a wart that it > probably doesn't matter what we do with it. There aren't a

Re: [HACKERS] More char()/ascii()

2008-02-20 Thread Gregory Stark
"Andrew Dunstan" <[EMAIL PROTECTED]> writes: > Gregory Stark wrote: >> Also, I thought we said this would be an error: >> >> postgres=# select length("char"(0)); >> length >> 0 >> (1 row) >> >> > > IIRC, we said chr(0) would give you an error, and it does. I don't recall any > d

Re: [HACKERS] More char()/ascii()

2008-02-20 Thread Andrew Dunstan
Gregory Stark wrote: Also, I thought we said this would be an error: postgres=# select length("char"(0)); length 0 (1 row) IIRC, we said chr(0) would give you an error, and it does. I don't recall any discussion of "char"(0), but no doubt a few brain cells have died s

[HACKERS] More char()/ascii()

2008-02-20 Thread Gregory Stark
Also, I thought we said this would be an error: postgres=# select length("char"(0)); length 0 (1 row) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!