My excitement died a few minutes ago. That patch is enough for compilation, but you get many runtime errors. It started with the migrations task complaining about some sql modes which do not exist in 4.1 (in do_mysql_ext.c). I fixed those, then I got errors while trying to access the "information_schema" table - another mysql 5 feature. I grep-ed "information_schema" and it is used in at least 3 modules. It is easier for me to migrate to mysql 5 than to figure out what needs to be patched.
Tiberiu :( On Mar 2, 12:59 am, Mr_Tibs <[email protected]> wrote: > Hi Alex, > > Thanks so much! I've applied the patch, repackaged the do_mysql gem > and it did build the native extensions on the machine with the 4.1 > mysql libraries. I haven't tested the functionality yet. I'll try it > tomorrow. > > Thanks again, > Tiberiu Motoc > > On Feb 28, 3:53 am, Alex Coles <[email protected]> wrote: > > > On Sat, Feb 28, 2009 at 3:10 AM, Mr_Tibs <[email protected]> wrote: > > > > ... > > > > I have one other quick question to an issue that I came across when > > > compiling the native gems on the remote machine: does module do_mysql > > > compile with mysql 4.1 libraries? > > > See this posting on the DataMapper > > list:http://groups.google.com/group/datamapper/msg/70d9d1d662ab1879 > > > 4.1 isn't officially supported, but you can try applying Dirkjan's > > patch and see if it works for you (it would be helpful for the project > > if you can report back if it works or not!). > > > Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
