Re: [sqlalchemy] Re: Custom UTC DateTime Type with Custom insert functionality

2011-02-09 Thread Michael Bayer
OK that ticket is complete if you feel like trying the default tip or 0.6 branch: 0.6: http://hg.sqlalchemy.org/sqlalchemy/archive/rel_0_6.tar.gz tip: http://hg.sqlalchemy.org/sqlalchemy/archive/default.tar.gz On Feb 9, 2011, at 12:52 AM, Michael Bayer wrote: Yeah, thats because the

[sqlalchemy] Re: Custom UTC DateTime Type with Custom insert functionality

2011-02-08 Thread chris e
I now have the code below, but the _oracle_utc_timestamp function is never called, even when I do explicitly set a value. class UTCTimestamp(TypeDecorator): impl = TIMESTAMP # add the UTC time zone info to naive timestamps def process_result_value(self, value, dialect) : if

Re: [sqlalchemy] Re: Custom UTC DateTime Type with Custom insert functionality

2011-02-08 Thread Michael Bayer
The TypeDecorator is not used for defaults. You set default=utc_timestamp() on your Column.The SQL expression is rendered directly in the INSERT when no value given, no bind params used. On Feb 8, 2011, at 10:13 PM, chris e wrote: I now have the code below, but the

[sqlalchemy] Re: Custom UTC DateTime Type with Custom insert functionality

2011-02-08 Thread chris e
I understand that's the case for defaults, but to test the code I actually set a value for one of the columns that is of type UTCTimestamp, and the compiler extension was never called. I'm stumped. That said, I can keep moving, I've decided to just use oracle timestamps without timezones, and

Re: [sqlalchemy] Re: Custom UTC DateTime Type with Custom insert functionality

2011-02-08 Thread Michael Bayer
Yeah, thats because the compiler extension, wrapped directly around _BindParamClause, is not called on an insert, when the bind is generated within the compile. That is why I made ticket #2042. Not going to work until I get around to that. It would work if you generated the bindparam()