kenderson, > > I am running ruby 1.8.6 and MySQL 4.1.20. Recommend to > > update? > > MySQL 4.1 is only receiving end-of-life support from MySQL now, so > it's probably a good idea to upgrade. They aren't applying any more > bug fixes to MySQL 4.1, the only fixes will be security related fixes.
I should add that even though I'm recommending you upgrade, I am willing to update DataMapper so it works with older versions of databases. My only concern would be that the code path not diverge too much from the normal path. If for example, we had to maintain a completely different set of SQL generation methods for one version of a database as another I probably would not be inclined to support that version. As of right now regular testing is only happening against the latest stable versions of each DB. Once I, or someone else in the community, gets the time to set up a proper CI system this could change. We would then be able to set up multiple DBs and run the specs against them on each change, whereas now we have to do it manually and it is too time consuming to be done consistently. -- Dan (dkubb) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
