On 3/28/06, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > Kevin wrote: > > userId in TG_User is, in fact, a UnicodeCol. So, that implies that the > > column validator is not being applied before the query string is put > > together. It's hard to imagine that this is a new bug in SQLObject, > > but it's possible. > > Yes, however we are using our own SQLObject model for TG_User (our > Person object) which uses standard StringCol. Do you think this is a > problem?
Potentially. It really depends on how the database is going to feel if it gets handed a unicode string. As of 0.9a2, we have the decode filter turned on, so it's possible to get unicode objects coming in from the web. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
