This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: More thoughts on DBI
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
The more I think about it, the more I'm leaning towards a wrapper for libdbi as part of a DBI rewrite. I've already signed up on the devel and user mailing lists, and I've helped eliminate a few compiler warnings.
Adding a third party dependency really doesn't bother me at all. Let's face it, half the standard library already has a third party dependency. This is not an issue. Plus, it means someone else gets to do all the heavy lifting, while I provide a simple wrapper. And, in theory, it should be faster with a C backend.
All that being said, I still haven't decided for sure that I'll take this approach. I'll probably layout the desired API, see how well I can bend the C backend into a Ruby frontend, and see how things progress. If I like them, great. If not, I'll ditch libdbi and go with a pure Ruby approach.
While writing this, I was just thinking it would be nice to have something like Perl's Test::MockDBI in Ruby. Quick, someone write that.
Previous Topic
