> i'm still seeing the failures in the copy commands (the ones about the paths)
I just tested this on a different machine (to get it away from my
I was able to duplicate the failures. It looks like I need to update
the expected/ files as well.
I will get fixed ASAP.
> i'm not really sure if this matters.
> contrib_regression=# select 256::int2::int4;
> (1 row)
> contrib_regression=# select 256::uint2::int4;
> (1 row)
> contrib_regression=# select 256::int2::uint4;
> ERROR: cannot cast type smallint to uint4 at character 17
> STATEMENT: select 256::int2::uint4;
> ERROR: cannot cast type smallint to uint4
> LINE 1: select 256::int2::uint4;
To keep this type fairly simple, I was not planning to add these casts.
My intention was to handle just enough casting for the required
ASSIGNMENT and IMPLICIT casts and to
gracefully handle the int4 type since naked numbers are implicitly cast to int4.
> otherwise seems fine
Thank you very much for your review!
I am still working on adding comments to the uint.c file. I am hoping
to have that completed tonight.
Have you had a chance to look over the RESTRICT selectivity functions
I implemented to handle the
cross-type problem? Is that what you had in mind?
In response to
pgsql-patches by date
|Next:||From: Gregory Stark||Date: 2008-09-22 17:41:48|
|Subject: Re: get_relation_stats_hook()|
|Previous:||From: Jaime Casanova||Date: 2008-09-22 00:29:17|
|Subject: Re: [PgFoundry] Unsigned Data Types [1 of 2]|