It is likely to be a problem with timezones. Zope recognizes one
particular date format as UTC and not local. If that sounds like
the problem, I can provide a patch.
On Sat, 25 Feb 2006, Kevin Carlson wrote:
Recently moved to a new server farm and am having a problem with dates
from
Turns out that the times and timezones are the same on all machines. In
doing some other reading online I discovered an email where same thing
was happening with PostgreSQL. The other interesting thing is that
MySQL DATE columns are displayed as one day earlier but MySQL DATETIME
columns are
On 2/25/06, Kevin Carlson [EMAIL PROTECTED] wrote:
Turns out that the times and timezones are the same on all machines. In
doing some other reading online I discovered an email where same thing
was happening with PostgreSQL. The other interesting thing is that
MySQL DATE columns are
Recently moved to a new server farm and am having a problem with dates
from MySQL that are rendered using strftime. The date in MySQL is
correct (e.g. 2005-01-22) but if the date is rendered with strftime the
date displayed is one day earlier (e.g., 2005-01-21). MySQL and Zope
are on
+---[ Kevin Carlson ]--
| Recently moved to a new server farm and am having a problem with dates
| from MySQL that are rendered using strftime. The date in MySQL is
| correct (e.g. 2005-01-22) but if the date is rendered with strftime the
| date displayed is one day
