Hello, I read http://www.sqlalchemy.org/trac/wiki/06Migration and did not see a mention of any changes to type mapping or casting.
I am currently using 0.5.5. While developing an application I found that generating tables from a declarative model resulted in undesirable / incorrect column types, so I had to create the tables using a SQL script directly. Also, percious had to add explicit casting into Sprox to make sure that integer column values from the db were cast as ints, which is not needed for PostgreSQL, MySQL or SQLite. We have worked around these issues, but it just seems that the Oracle adapter is not behaving like those of other databases. Is this intended behaviour or a known issue? NB. I just read about the related changes in trunk now, I haven't tested it yet. On a related note, I am afraid I am likely unable to contribute code to SA myself. However, for what it's worth, I can offer to host dedicated virtual machines in our racks, running the free Oracle Express Edition, for any SA developers who would benefit from such access. -- Thanks & Regards, Teemu Yli-Elsila --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
