Are you using Python 2.4?
I've seen other people here on the list having problems witht he
DateTime module and it being a day off. Search the archive on
'strftime' and hope.
2005/10/15, Kirk Strauser [EMAIL PROTECTED]:
I'm upgrading our server from a FoxPro backend to PostgreSQL, using the
On Saturday 15 October 2005 01:24, Andreas Jung wrote:
If you speak of DateTime instances then you should be able to write
to two-line testcase that shows the issue with a standard Zope
installation.
If you can provide such a testcase we are able to look at it in detail.
date =
--On 16. Oktober 2005 10:41:19 -0500 Kirk Strauser [EMAIL PROTECTED] wrote:
On Saturday 15 October 2005 01:24, Andreas Jung wrote:
If you speak of DateTime instances then you should be able to write
to two-line testcase that shows the issue with a standard Zope
installation.
If you can
I'm upgrading our server from a FoxPro backend to PostgreSQL, using the
Psycopg connector. My problem is that the old database returned timestamps
as a %m/%d/%Y-formatted string, while Psycopg returns a DateTime object
(I'm using the internal module, not mxDateTime). Whenever I use strftime
--On 15. Oktober 2005 01:19:56 -0500 Kirk Strauser [EMAIL PROTECTED] wrote:
I'm upgrading our server from a FoxPro backend to PostgreSQL, using the
Psycopg connector. My problem is that the old database returned
timestamps as a %m/%d/%Y-formatted string, while Psycopg returns a
DateTime
