[sqlalchemy] Re: Oracle timestamp and postgres datetime compatibility

2009-12-04 Thread Nicola Lacquaniti
Indeed was a fault of mine. I haven't noticed that, in my code, before assigning the value I converted the datetime.datetime.now() to string. So the backend tries to assign a string, and not a date. With postgres it dosn't matter (if the client and the server has the same localization...) because

[sqlalchemy] Re: Oracle timestamp and postgres datetime compatibility

2009-12-03 Thread Nicola Lacquaniti
I tried the same thing, but I obtain an 'ORA-01843: not a valid month' message from the backend. This is my model: class BaseObject(Base, Dictionaryable): __tablename__ = 'baseobj' id = Column(Integer, Sequence((__tablename__+'id_seq')[-30:]), autoincrement=True,