Re: [PgFoundry] Unsigned Data Types [1 of 2]
От | Tom Lane |
---|---|
Тема | Re: [PgFoundry] Unsigned Data Types [1 of 2] |
Дата | |
Msg-id | 27485.1220746204@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [PgFoundry] Unsigned Data Types [1 of 2] ("Jaime Casanova" <jcasanov@systemguards.com.ec>) |
Ответы |
Re: [PgFoundry] Unsigned Data Types [1 of 2]
|
Список | pgsql-patches |
"Jaime Casanova" <jcasanov@systemguards.com.ec> writes: > On Sat, Sep 6, 2008 at 3:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> postgres=# select -256::uint1; >>> ERROR: uint1 out of range >> >> No, that's just because this is parsed as -(256::uint1) > actually, i thought that case is right but the -255::uint1 returning a > negative number (aka -255) is what bothers me Well, again, that's -(255::uint1). I suppose uint1 hasn't got a negation operator (what would it do??), so probably the sequence of events is to form 255::uint1, then implicitly promote it to some signed type or other (most likely int4), then negate. Not much to be done about this unless you want to get rid of the implicit coercion to signed types, which would probably defeat most of the purpose. Now, if (-255)::uint1 fails to throw error, that would be a bug IMHO. Casting any negative value to uint ought to fail, no? regards, tom lane
В списке pgsql-patches по дате отправления: