Re: problem with timezone parsing

On Wed, Feb 18, 2009 at 04:56:37PM +0100, Federico Di Gregorio wrote:

> > The OID values for these built in types are fixed.  If they could
> > change from installation to installation or version to version, then
> > it would not be safe to include the values in a header file.
> > 
> > So when it says "#define TIMESTAMPTZOID  1184" in
> > /usr/include/postgresql/catalog/pg_type.h, you can depend on that
> > being a constant.
> 
> That's exactly what I meant.

OK. I'll let the cross-check with psycopg2.DATETIME.values
in there for good measure anyway.

Now, this doesn't yet answer the question why the custom
caster didn't work for all of those OIDs - although it
should 'cause the very first action it did was to pass its
input to the original caster. Hmm.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346