,
Column('username', Unicode),
Column('realname', Unicode),
Column('address', Unicode)
Column('phone', Unicode)
# etc...
)
Thanks,
--
Teemu Yli-Elsilä
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send
limit?
Thanks,
--
Teemu Yli-Elsilä
--~--~-~--~~~---~--~~
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
we need are succinct and definitive
tests that illustrate the behaviors in question.
As I said above, I will create such tests for you soon.
Thanks again,
--
Teemu Yli-Elsilä
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
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