Re: problem with timezone parsing
Federico Di Gregorio <fog-NGVKUo/i/[email protected]>
| Newsgroups | gmane.comp.python.db.psycopg.devel |
|---|---|
| Organization | initd.org |
| Message-ID | <[email protected]> |
Il giorno mer, 18/02/2009 alle 23.28 +0900, James Henstridge ha scritto: > > Frederico said, that using DATETIME.values is safe because > > the OIDs are taken from my PostgreSQL headers. But what > > happens if locally I have PG 8.1 installed while the remote > > server runs PG 8.3 (and assuming the OIDs happen to not be > > identical) ? > > 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. federico -- Federico Di Gregorio http://people.initd.org/fog Debian GNU/Linux Developer [email protected] INIT.D Developer fog-NGVKUo/i/[email protected] Do I know what a rhetorical question is? -- Homer Simpson _______________________________________________ Psycopg mailing list Psycopg-IAPFreCvJWPBWskQ1e/[email protected] http://lists.initd.org/mailman/listinfo/psycopg
signature.asc
(application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkmcL7QACgkQvcCgrgZGjetyuQCeJa3Kmhq4DOPK8mCW98TQbpCx +gQAoLChilUDpzC3wWnSstuQotJ553Hs =vKUt -----END PGP SIGNATURE-----