> > > What exactly are the ramifications of the 'use_unicode=1' parameter > > in the dburi? > > use_unicode=1 is a MySQLDB setting indicating that youd like all your > strings returned/received as Python unicode objects which will be > encoded by the MySQLDB api. > > > Why can't the String() type in SqlAlchemy play well when > > use_unicode=1? > > well it *does*, it just returns whatever MySQLDB gives you. > > > Or should 'use_unicode=1' be avoided since it forces all columns to be > > treated as unicode? > > if you dont want *every* string to be unicode, you should probably > turn this feature off and use SQLAlchemy's Unicode type for those > columns which you do want unicode. > > But also, String() may not be the best type for "pickled" data > anyway. SQLAlchemy's own PickleType uses the Binary type, which on > MySQL uses a column of type "BLOB".
Yes, I noticed their support for that. So, I suppose that I could use the non-s versions (load,dump) and place them in the PickleType/Blob column. Why do you say that string may not be the best type for pickled data? (and thanks for the speedy response... very helpful). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
