From erik at hollensbe.org Sat Mar 1 01:32:50 2008 From: erik at hollensbe.org (Erik Hollensbe) Date: Fri, 29 Feb 2008 22:32:50 -0800 Subject: [ruby-dbi-users] M4DBI: Models In-Reply-To: <6c9d9ef0802271115we99d569j6e10643c35088565@mail.gmail.com> References: <6c9d9ef0802271115we99d569j6e10643c35088565@mail.gmail.com> Message-ID: <200802292232.50443.erik@hollensbe.org> On Wednesday 27 February 2008 11:15:19 databaseofgrace.5.pistos at geoshell.com wrote: > 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. Sounds awesome! This IMO is exactly how DBI should be used, as a lower-level API to databases. Do you have a repository I can track? SInce Ruby/DBI has an anemic test suite at the moment, the test suite you have might provide some very useful checks for Ruby/DBI... I'd love to be able to leverage it. Thanks, -- Erik Hollensbe From timuckun at gmail.com Sun Mar 9 23:28:48 2008 From: timuckun at gmail.com (Tim Uckun) Date: Mon, 10 Mar 2008 16:28:48 +1300 Subject: [ruby-dbi-users] ADO adapter. Message-ID: <855e4dcf0803092028h25f11b98o450cc90e208c0ae@mail.gmail.com> Hello all. I would like to get in touch with the person who is responsible for the ADO driver. I have some code I would like to submit as a patch. I have git installed so I would also like the URL of the code so I can pull it. Thanks. From erik at hollensbe.org Mon Mar 10 01:51:38 2008 From: erik at hollensbe.org (Erik Hollensbe) Date: Sun, 09 Mar 2008 22:51:38 -0700 Subject: [ruby-dbi-users] ADO adapter. In-Reply-To: <855e4dcf0803092028h25f11b98o450cc90e208c0ae@mail.gmail.com> References: <855e4dcf0803092028h25f11b98o450cc90e208c0ae@mail.gmail.com> Message-ID: <47D4CC6A.3070703@hollensbe.org> Tim Uckun wrote: > Hello all. > > I would like to get in touch with the person who is responsible for > the ADO driver. I have some code I would like to submit as a patch. > > I have git installed so I would also like the URL of the code so I can pull it. > URL: git://hollensbe.org/git/ruby-dbi.git Very soon we will not be supporting the Windows-based DBD's, but we're looking for someone to manage these. If you have any interest, let me know privately. -Erik From timuckun at gmail.com Mon Mar 10 06:12:42 2008 From: timuckun at gmail.com (Tim Uckun) Date: Mon, 10 Mar 2008 23:12:42 +1300 Subject: [ruby-dbi-users] ADO adapter. In-Reply-To: <47D4CC6A.3070703@hollensbe.org> References: <855e4dcf0803092028h25f11b98o450cc90e208c0ae@mail.gmail.com> <47D4CC6A.3070703@hollensbe.org> Message-ID: <855e4dcf0803100312n691fe977x269326cd322b838c@mail.gmail.com> > Very soon we will not be supporting the Windows-based DBD's, but we're > looking for someone to manage these. If you have any interest, let me > know privately. I am disappointed to hear that. i don't know if I want the responsibility of maintaining the codebase but I will think about it. Thanks for the git URL. BTW does this mean you are not interested in the patches? From erik at hollensbe.org Mon Mar 10 08:56:49 2008 From: erik at hollensbe.org (Erik Hollensbe) Date: Mon, 10 Mar 2008 05:56:49 -0700 Subject: [ruby-dbi-users] ADO adapter. In-Reply-To: <855e4dcf0803100312n691fe977x269326cd322b838c@mail.gmail.com> References: <855e4dcf0803092028h25f11b98o450cc90e208c0ae@mail.gmail.com> <47D4CC6A.3070703@hollensbe.org> <855e4dcf0803100312n691fe977x269326cd322b838c@mail.gmail.com> Message-ID: <47D53011.8090707@hollensbe.org> Tim Uckun wrote: >> Very soon we will not be supporting the Windows-based DBD's, but we're >> looking for someone to manage these. If you have any interest, let me >> know privately. >> > > I am disappointed to hear that. i don't know if I want the > responsibility of maintaining the codebase but I will think about it. > > Thanks for the git URL. > > BTW does this mean you are not interested in the patches Yes, we *are* interested in the patches. The core issue (that I should have explained better earlier, but I just got back from the bar :) is that we're eventually breaking the DBDs out into separate gems for separate maintainership, similar to how Perl manages DBI and its related DBDs. Chris and myself have no access to windows testing resources and the databases in particular, and we both consider testing to be crucial to how development takes place. To top this, neither of us are Windows developers, making low-level work painful and error-prone (which doesn't benefit anyone, really). So, since we can't really *test* ADO and SQLServer and other Windows-based databases, we're unfortunately unable to support them directly. What would be our ideal situation is that these DBDs do not disappear but are picked up by someone that has the same interest in testing that we do and enough drive to maintain these against a DBI/DBD standard that evolves with time. And hey, that person gets a free test suite to accompany the DBD. ;) Right now I can almost predict, considering the state of other DBDs that I've worked on, that when the current spec is followed, it's followed poorly. We're looking to limit the burden of supporting all these databases by allowing others to maintain DBDs that they can test against so we can focus on making DBI and DBDs better as a whole by allowing more people to work on them, write tests for them, release them independently. I HTH. It's not that we don't want to support them, it's that it's really not practical to do so for a number of reasons. We are looking for a windows person that can help us with the project as a lead developer and hope to find that person before our first feature release. -Erik From erik at hollensbe.org Wed Mar 12 18:29:33 2008 From: erik at hollensbe.org (Erik Hollensbe) Date: Wed, 12 Mar 2008 15:29:33 -0700 Subject: [ruby-dbi-users] Oracle vs. OCI8 driver Message-ID: <200803121529.33872.erik@hollensbe.org> Hello, What I've been doing the last few days is attempting to get Oracle working so I can test the oracle drivers. Chris Maujean (the oracle guru of the two of us) has been strapped for time lately, so he handed it off to me and said, "Port it to ruby-oci8". FTR, this is the only thing that's holding the 0.2.0 release up, with the current constraints on what we're able to maintain. What I found out where a couple of things unbeknownst to me: 1) OCI8 comes with a DBD that (presumably) is actively maintained. The last release was on 11/25/2007. 2) The "Oracle" DBD is supports the Oracle 7 interface on RAA. Since I was using 8i when it was "old" about 6-7 years ago, I would be heartily surprised if Oracle 7 is still in frequent use. Those who are using the Oracle DBD on 8i and above would probably be better off using the OCI8 DBD if they aren't. 3) I forgot that oracle is lacking simple things like a boolean type, therefore rendering a great deal of the "general" test suite useless without a lot of case statements on the dbtype. So in lieu of all of this, I'm proposing: 1) That we deprecate the Oracle driver, politely asking that those that need it maintain it, which is the direction we're heading anyways. 2) We modify the test suite to test against OCI8, outright skipping the types testing (but making sure the rest works) until 0.4.0 starts development, which is going to have a strong focus on type handling. Complaints/flames/ideas? -- Erik Hollensbe From databaseofgrace.5.pistos at geoshell.com Fri Mar 14 00:05:11 2008 From: databaseofgrace.5.pistos at geoshell.com (databaseofgrace.5.pistos at geoshell.com) Date: Fri, 14 Mar 2008 00:05:11 -0400 Subject: [ruby-dbi-users] Oracle vs. OCI8 driver In-Reply-To: <200803121529.33872.erik@hollensbe.org> References: <200803121529.33872.erik@hollensbe.org> Message-ID: <6c9d9ef0803132105v64bbb441pfb5bb373c6b6df16@mail.gmail.com> On 12/03/2008, Erik Hollensbe - erik at hollensbe.org wrote: > So in lieu of all of this, I'm proposing: > > 1) That we deprecate the Oracle driver, politely asking that those that need > it maintain it, which is the direction we're heading anyways. > > 2) We modify the test suite to test against OCI8, outright skipping the types > testing (but making sure the rest works) until 0.4.0 starts development, > which is going to have a strong focus on type handling. > > Complaints/flames/ideas? This sounds reasonable to me. Better to get the release out and show the world that DBI is alive and kicking. Any complaints raised after the fact can be dealt with as they come up. -- Pistos http://blog.purepistos.net From erik at hollensbe.org Fri Mar 14 07:25:53 2008 From: erik at hollensbe.org (Erik Hollensbe) Date: Fri, 14 Mar 2008 04:25:53 -0700 Subject: [ruby-dbi-users] Oracle vs. OCI8 driver In-Reply-To: <6c9d9ef0803132105v64bbb441pfb5bb373c6b6df16@mail.gmail.com> References: <200803121529.33872.erik@hollensbe.org> <6c9d9ef0803132105v64bbb441pfb5bb373c6b6df16@mail.gmail.com> Message-ID: <200803140425.53075.erik@hollensbe.org> On Thursday 13 March 2008 21:05:11 databaseofgrace.5.pistos at geoshell.com wrote: > On 12/03/2008, Erik Hollensbe - erik at hollensbe.org wrote: > > So in lieu of all of this, I'm proposing: > > > > 1) That we deprecate the Oracle driver, politely asking that those that > > need it maintain it, which is the direction we're heading anyways. > > > > 2) We modify the test suite to test against OCI8, outright skipping the > > types testing (but making sure the rest works) until 0.4.0 starts > > development, which is going to have a strong focus on type handling. > > > > Complaints/flames/ideas? > > This sounds reasonable to me. Better to get the release out and show > the world that DBI is alive and kicking. Any complaints raised after > the fact can be dealt with as they come up. Yeah, that's the idea. Tonight will probably be our release night (been trying to get it out all week, but things came up), after I test/integrate some patches from Mike Pomraning to the Pg driver. I'll be sure to let this list know as soon as 0.2.0 release hits the floor. If anyone has any questions, I tried to answer some things about 0.2.0 (and a bit about 0.4.0) in the news section of the project page. -- Erik Hollensbe From erik at hollensbe.org Sun Mar 16 16:11:23 2008 From: erik at hollensbe.org (Erik Hollensbe) Date: Sun, 16 Mar 2008 13:11:23 -0700 Subject: [ruby-dbi-users] 0.2.0 released Message-ID: <200803161311.23297.erik@hollensbe.org> http://rubyforge.org/forum/forum.php?forum_id=22766 for release details, and here's the long-form changelog: http://code.hollensbe.org/?p=ruby-dbi.git;a=summary Run the tests, break things, fill the tracker up. Thanks to everyone on these lists for your help! -- Erik Hollensbe