This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: Reworking DBI
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
Michael Neumann, unfortunately, has recently decided he doesn't want to work on the DBI package any more and gave me admin status on the project. Oh, joy.
Well, that really kinda sucks, since I consider DBI to be one of the most important packages for Ruby. Well, for any language really (for whatever equivalent each language has).
So, what should I do? I have one bug fix I know I'd like to implement, but DBI has larger problems. First and foremost is speed. At least, that's what people tell me. I know some PG users on IRC say they use the PG calls directly rather than using the DBI wrapper because DBI is too slow. I've never personally benchmarked this. I guess none of my database code needed to worry about it.
I also wonder about the whole layout. Why is DBI a module, for example? Does anyone mix it in? Or was it just for the sake of a namespace? I don't really understand that.
I've also toyed with the idea of just starting from scratch. Should I do my own thing? Should I wrap something like libdbi?
Previous Topic
