From cmaujean at gmail.com Sat Feb 23 17:42:05 2008 From: cmaujean at gmail.com (Christopher Maujean) Date: Sat, 23 Feb 2008 14:42:05 -0800 Subject: [ruby-dbi-users] Test message Message-ID: <239ccc370802231442y2b61395ei10eb0c170fefd72e@mail.gmail.com> Making sure this thing works as expected. --Christopher Maujean From erik at hollensbe.org Sat Feb 23 17:42:59 2008 From: erik at hollensbe.org (Erik Hollensbe) Date: Sat, 23 Feb 2008 14:42:59 -0800 Subject: [ruby-dbi-users] Test message In-Reply-To: <239ccc370802231442y2b61395ei10eb0c170fefd72e@mail.gmail.com> References: <239ccc370802231442y2b61395ei10eb0c170fefd72e@mail.gmail.com> Message-ID: <200802231442.59406.erik@hollensbe.org> On Saturday 23 February 2008 14:42:05 Christopher Maujean wrote: > Making sure this thing works as expected. Ack. -- Erik Hollensbe From erik at hollensbe.org Sun Feb 24 21:33:00 2008 From: erik at hollensbe.org (Erik Hollensbe) Date: Sun, 24 Feb 2008 18:33:00 -0800 Subject: [ruby-dbi-users] Git repository, DBD testing and DBD::Pg changes Message-ID: <200802241833.00319.erik@hollensbe.org> I've posted some of this in the news already. There is a git repository at git://hollensbe.org/git/ruby-dbi.git that you can clone and edit at your leisure. It's a full import of the CVS project, and our initial additions (described below). We're trying to encourage others getting involved in the development effort. Please generate your patches on that repo and NOT the CVS repo. Also, if you like getting your patch integrated quickly, write tests that I can apply seperately (to watch them fail), so I can determine that your patch is the fix for said issue. DBD testing is there, if only for the DBD::Pg driver for now. Please see test/DBD_TESTS for information on creating a configuration which allows you to specify which DBDs to test and how you link them to a database. It's all more ad-hoc than I like it but it's a working solution and gets us on our way. DBD::Pg is now based on the 'ruby-pg' driver and contains working LOB and ::bytea support (which is slow due to a bug in the 'pg' driver), and a gaggle of other bugfixes. Next on my list is getting the mysql tests to work with the new DBD testing framework, and whacking a number of bugs in the mysql DBD. After that, I will be rebasing DBD::SQLite and DBD::SQLite3 on the mature ruby-sqlite* modules by Jamis Buck. This is gearing up for a 0.1.2 release, which will be a long-awaited bugfix release. DBI will not see an API change until at least 0.2.0, but we will be integrating bugfixes as we encounter the ability to test them. -- Erik Hollensbe From databaseofgrace.5.pistos at geoshell.com Wed Feb 27 14:15:19 2008 From: databaseofgrace.5.pistos at geoshell.com (databaseofgrace.5.pistos at geoshell.com) Date: Wed, 27 Feb 2008 14:15:19 -0500 Subject: [ruby-dbi-users] M4DBI: Models Message-ID: <6c9d9ef0802271115we99d569j6e10643c35088565@mail.gmail.com> Hello all. I'm glad to see DBI getting some attention again. I've tried ActiveRecord, Og and Sequel, but after all is said and done, I feel most at home with DBI. :) http://rome.purepistos.net/m4dbi/rdoc http://rome.purepistos.net/m4dbi/examples/ I just wanted to start publicizing a project I've begun recently: M4DBI - Models for DBI. I agree with the general philosophy of keeping DBI a lean and low-level means of accessing one's database. At the same time, I enjoy the convenience of the ORMs in that they let me work with models and relationships between them in a nice, Ruby-ish way. I don't care much for the SQL-alike constructs that other ORMs try to give, so I made M4DBI: all the power and low-level feel of DBI, but with models. M4DBI is heavily spec'ed, with nearly 99% c0 code coverage: http://rome.purepistos.net/m4dbi/rcov/ and I and another user are using it in a few places. -- Pistos http://blog.purepistos.net