On Sun, Jan 11, 2009 at 11:27 PM, Dirkjan Bussink <[email protected]> wrote: > > > On 11 Jan 2009, at 22:58 , kolach wrote: > >> What am I missing. Are there some additional connection params? > > First of all, JRuby support is really still in it's infancy and is in > heavy development. Building != all working correctly. Don't really > expect stuff be working everywhere, there are still specs failing so > we won't put the stamp "ready" onto it for some time. > > This issue is actually known, I don't know the details, but as far as > I know, it's not trivial in JDBC to set the connection encoding. The > API for JRuby and MRI will be same, so there is not hidden option and > there never will be. > > If you have experience with Java / JRuby and are willing to help out > with these issues, please feel free to join the effort in making JRuby > a fully supported platform for DataObjects / DataMapper. > > -- > Regards, > > Dirkjan Bussink
Dirkjan is right that JRuby support is still in its infancy. However, there are many gaps in our specs, so its important for people to start playing with it - even with real world apps -, and start giving feedback on what works and what is badly broken! The JDBC variants of the DO drivers do not currently set the character set encoding on MySQL properly. However, they should default to utf8. If you'd be able to make this into an issue in the issue tracking tool (http://datamapper.lighthouseapp.com/), I'll definitely look into (and also see if we can incorporate more thorough testing of character sets into DataObjects' suite of test/specs). Many thanks, Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
