Robin Munn wrote:
> The solution here would be to either change the definition of the
> visit (and other) tables to use "timezone=False" in their SQLAlchemy
> column definitions, ...
Does this really suffice? I found that it does not work with the
current and SVN versions of SQLAlchemy. Only after adding the following
line to Column's init method in schema.py, everything worked as
expected:
self.timezone = kwargs.pop('timezone', True)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
