Closed
Description
Migrated issue, originally created by Anonymous
sqlalchemy 0.3.8
exp_table = Table("foo", metadata, autoload=True)
File "build\bdist.win32\egg\sqlalchemy\schema.py", line 166, in call
File "build\bdist.win32\egg\sqlalchemy\engine\base.py", line 809, in reflecttable
File "build\bdist.win32\egg\sqlalchemy\databases\oracle.py", line 342, in reflecttable
sqlalchemy.exceptions.AssertionError: Can't get coltype for type 'TIMESTAMP WITH TIME ZONE' on colname 'FOO_CREATED_DATE'
Attachments: oratimezones.patch
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
No branches or pull requests
Activity
sqlalchemy-bot commentedon Jul 28, 2007
Changes by Michael Bayer (@zzzeek):
sqlalchemy-bot commentedon Dec 27, 2008
Michael Bayer (@zzzeek) wrote:
this just raises a warning in 0.4 and 0.5 so is relatively harmless. Adding the type is targeted for post 0.5.0.
sqlalchemy-bot commentedon Dec 27, 2008
Changes by Michael Bayer (@zzzeek):
sqlalchemy-bot commentedon Feb 25, 2010
Catherine Devlin (@catherinedevlin) wrote:
TIMESTAMP WITH TIME ZONE support for Oracle + accompanying unittests
sqlalchemy-bot commentedon Feb 25, 2010
Changes by Catherine Devlin (@catherinedevlin):
sqlalchemy-bot commentedon Feb 25, 2010
Changes by Michael Bayer (@zzzeek):
sqlalchemy-bot commentedon Mar 19, 2010
Michael Bayer (@zzzeek) wrote:
cdda68a
sqlalchemy-bot commentedon Mar 19, 2010
Changes by Michael Bayer (@zzzeek):