The problem is probably not with psycopg, but with Python's time structures
such as mxDateTime. The strftime() function in Linux and Windows is one of many
date/time functions that do not support anything less than seconds. You can
circumvent this by using PostgreSQL's type conversion functions to pass a
formatted string back to psycopg:
=> SELECT to_char(now(), 'HH:MM:SS.MS');
You can then parse the string yourself.
Eric Radman | http://eradman.com
On 20:30 Mon 26 Jul , Marc Saric wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Hi all,
> is anyone here who has some experience with psycopg
> This is certainly unrelated to WebWare, but the psycopg-list has been
> silent so far.
> I have a problem with TIMESTAMPS, they get mangled (milliseconds cut
> off, millisecond-separator beeing a "," instead of ".") by psycopg and I
> don't know why.
> Currently I use PyGreSQL because of this, but it lacks certain functions
> (support for BLOB-insertion, string-escaping) and is in general badly
> documented (the DB2.0-API compliant adapter, not the old one).
> Thanks in advance.
> - --
> Marc Saric http://www.marcsaric.de
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----