"Diez B. Roggisch" <[EMAIL PROTECTED]> writes: > This is standard behaviour even with oracle. As the dimensions of a text > column have to have an upper limit for efficiency reasons, you can either > use a fixed-width encoding like ucs2 or even ucs4, wasting awfully lots of > bytes, or you have to cap the size.
The size of the columns should be determined by the database encoding. If I create an UTF-8 database then char(1) should be able to store *any* char that can be represented in UTF-8. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
