From: Paul R. <pa...@ma...> - 2009-05-30 13:28:14
|
I like the way we vary between top+bottom posting :) One thing we need to look at/document is steps to convert db to utf8. At the moment, we have checks to show tables/columns in mysql that aren't converted to utf8 but haven't documented the process to convert them - I'm personally trying to work out whether it's just a case of doing ALTER TABLE -> charset(utf8), or whether we need to look at individual data / dump/restore. The information on the internet i've read personally seems to be a bit contradictory on this. Paul ----- "Victor Boctor" <vb...@gm...> wrote: > Ping for the other devs. > > On Fri, May 22, 2009 at 12:02 AM, Gianluca Sforna <gi...@gm...> > wrote: > > On Thu, May 21, 2009 at 10:27 AM, Victor Boctor <vb...@gm...> > wrote: > >> Hi all, > >> > >> In the last couple of days I did some triaging of the issues that > are > >> targeted for 1.2.x in an attempt to know the issues that would > block > >> branching and stabilization (i.e. an RC). If you are aware of > >> something that needs to be done before then, please raise here and > >> target the issue to 1.2.x in the bug tracker. > > > > Right now, I'm not aware of any blocker bugs for 1.2 (despite I'm > not > > looking so closely to the tracker these days); instead I've got > > reports it's working better than 1.1 for many people on MSSQL and > > pgsql. > > > > The only feature I'm working on which is (IMHO) in a good state for > > inclusion is voting, AKA bug 668, but I'd surely not block a 1.2 > > release because of it... > > > > Thank for looking into this > > > > G. > > > > > > |