Hi, Kristian from the mailing list kindly offered to help me with the development of the JDBC support for DataObjects. After a hiatus over the last 2-3 months, I have been working this weekend on a lot of cleanup + making the building/test process easier, to ease the barrier to contributing.
One thing Kristian rightly brought up was a duplication of effort in one area: JDBC support requires Java/JDBC drivers (in JAR form) from each of the database vendors. However, we wrap these up as Ruby Gems (named do_jdbc-*) for easy installation. You'll find these drivers in the jdbc-drivers/ directory in the DO repository. These are kept separate from the DataObjects drivers (named do_* -- NOTE confusingly, but for back of better term, we're also using the term "drivers"). The Java/JDBC driver JARs are not bundled with the DO drivers for a couple reasons: - General decoupling (this makes sense when you see the question below) - Gem versioning of JDBC drivers reflect the vendor's JDBC driver version, NOT the DO version. - Licensing: DB vendors use a variety of different o/s licenses: Apache, some BSD, MySQL use GPL. The team behind the activerecord-jdbc-adapter however are doing exactly the same thing! (see the drivers/ directory in the AR-JDBC git repo) When I started out on JDBC support we weren't using Hoe, and activerecord-jdbc-adapter had slightly older versions of the JDBC driver JARs in their repository (I wanted to start out by coding against the latest versions). However, we're now also using Hoe. The only thing I did differently/on top of what the activerecord-jdbc-adapter team are doing, is my addition of a custom 'buildr' buildfile as a tool for going out and pulling the latest JARs from Maven repositories. Kristian asked why we're duplicating effort here, and if there are any political reasons for this. The answer is unequivocally no. So the question is to DM list whether we're OK with getting rid of our own JDBC driver Gem wrappers, and using those provided by the activerecord-jdbc-adapter? It would save us from having to publish yet more gems (do_jdbc-derby, do_jdbc-mysql, etc.) with each DO/DM release: Instead it'll be a matter of depending on what the AR-JDBC project has already published: jruby -S gem install jdbc-derby jruby -S gem install jdbc-mysql jruby -S gem install jdbc-postgres etc. I've copied Nick Sieger who did maintains activerecord-jdbc-adapter to give him a heads up on this. Thanks for your thoughts, 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 -~----------~----~----~----~------~----~------~--~---
