as Christophe says, you should simply replace UTF-8 with utf8 and it should work!
On May 13, 2011, at 1:31 PM, Christophe COEVOET wrote: > Le 13/05/2011 12:06, davidj a écrit : >> OK, it seems that a bug in doctrine dbal configuration parsing is >> under review by fabpot. >> I keep commenting on >> http://groups.google.com/group/symfony-users/browse_thread/thread/a58464ca7c946a > Your issue is not a bug. It is the Doctrine expected behavior as I said > previously: it does not set any encoding when creating the tables, relying on > the default encoding set when you created your database. > > -- > Christophe | Stof > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
