On Jan 18, 2008, at 5:29 PM, Hermann Himmelbauer wrote:
> Am Freitag, 18. Januar 2008 22:43 schrieb Michael Bayer:
>> On Jan 18, 2008, at 10:59 AM, Hermann Himmelbauer wrote:
>>> Hi,
>>> I have a table that looks appr. like this (I deleted some columns):
>>>
>>> table_acc = Table(
>>> 'konto', metadata,
>>> Column('kontoid', Integer, primary_key=True, key='accid'),
>>>
>>> What can I do about this? It seems, that "now()" is not recognized,
>>> but how is
>>> this possible?
>>>
>>> I am using SA 0.4.1, SA0.4.2p3 + Python-2.4.4 and sqllite.
>>
>> with sqlite use func.current_timestamp() instead of now().
>
> Yes, this did the trick - thank's a lot!
> One more question: I user sqlite only for testing my database
> application, for
> the real thing I'll use MaxDB and/or postgresql; Will
> func.current_timestamp() work for these databases, or should I set
> up some
> proxy function that returns either now() or current_timestamp()
> regarding to
> the database?
>
func.current_timestamp() should be supported on most dbs (not sure
about MaxDB), but its also a "generic" function right now so it should
fire off the appropriate equivalent if its not available on a
particular DB. we should probably add "now()" as a generic as well.
its a new feature we havent built out yet.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
