On Sun, Feb 26, 2006 at 08:06:10PM -0500, Daniel Convissor wrote:
Oh, and the create table statements don't specify the character set. I'll add that in the patch.
Hmm... I now see that update 169 changes the character set on the tables. But the process checks for the database's default character set before running. If the default character set is already UTF-8, it doesn't run. This check was put in the initial commit, 1.186, by unconed. I feel that may be a mistaken attempt at being efficient. Just because a database's default character set is UTF-8 doesn't mean the necessary tables have that default and that the columns in said tables are that character set. It seems the process should run no matter what. Thoughts? --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409