On Jun 4, 8:07 am, Jeremy Evans <[email protected]> wrote: > Between 3.11.0 and 3.12.0 I made a change to the the way the encoding > was set in the MySQL adapter (http://github.com/jeremyevans/sequel/ > commit/0adf8f14371fccff213cc9cd347611e642e32e44). This fixed the OPs > case, but it appears to have broken other cases. One workaround that > fixes both cases is making it so Sequel does not read the client > default group by default, but I think that would break backwards > compatibility for people that are relying on that feature. > > Anyway, if you use MySQL and understand the issues, please take a look > athttp://code.google.com/p/ruby-sequel/issues/detail?id=300and add > your comments. > > If I don't get any responses, I'll probably end up reverting the > previous patch and not reading the client default group by default, > using the patch at (http://pastie.org/967778.txt).
Thanks to some advice from tmm1, this got sorted out: http://github.com/jeremyevans/sequel/commit/a9115795dbae1c7d518ebd4341e6d674b97a8780 I'm willing to do a 3.12.1 release for just this patch if there will be a lot of people affected by this (I honestly don't know), so if you would like a point release made, please speak up here. Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en.
