Re: [Sqlalchemy-tickets] [sqlalchemy] #1785: postgres timestamp broken in 0.6
Brought to you by:
zzzeek
Menu
▾
▴
Re: [Sqlalchemy-tickets] [sqlalchemy] #1785: postgres timestamp broken in 0.6
|
From: sqlalchemy <mi...@zz...> - 2010-04-28 01:09:43
|
#1785: postgres timestamp broken in 0.6
----------------------+-----------------------------------------------------
Reporter: guest | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone:
Component: postgres | Severity: no triage selected yet
Keywords: | Status_field: needs questions answered
----------------------+-----------------------------------------------------
Changes (by zzzeek):
* status_field: awaiting triage => needs questions answered
Comment:
I'm not familiar with this behavior in any version of SQLAlchemy, and
there's no special meaning to "func.TIMESTAMP" I can find going back to
0.3 (only CURRENT_TIMESTAMP and similar). Can you please specify version
and attach a test script. You can use the compiler extension for now.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1785#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|