On Sep 17, 2008, at 12:44 PM, Kevin Dangoor wrote:
>
> I have some of my columns defined as Column('foo', Unicode). This
> worked fine with MySQL, but a change made in r4705 appears to have
> broken this. Prior to 4705, that would generate a TEXT column in the
> create table. This was switched to just VARCHAR.
>
> MySQL 5.0.45 does not accept VARCHAR without a length, and from what I
> see in the MySQL docs, this is the case all the way through MySQL 6.
>
> I have SQLAlchemy generate my tables and I also have an sqlalchemy-
> migrate migration in place to create a new table, which is how I
> spotted this. Am I missing something, or is this a bug?
Greetings Mr. Dangoor -
We've strictified the difference between String() and Text() in 0.5
such that String() doesn't implicitly go from VARCHAR to TEXT without
a length. So in your case you want to use UnicodeText.
- mike
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
