Please remember that almost everyone that uses Oracle knows exactly what "oci" is. Also, "oci" isn't quite the best way of integrating with Oracle anymore (although it does certainly work!), so I would suggest having a stub named "oracle" and keeping the "oci" one as it is until someone gets around to implementing the preferred "thin" approach.
On 2/27/06, David Heinemeier Hansson <[EMAIL PROTECTED]> wrote: > > It's always kind of bugged me that the Oracle adapter is named "oci", > > seems odd relative to all the other adapters. > > > > Would the core group be open to a patch that renamed this "oracle", w/ > > the required stubs to maintain backwards compatibility? > > > > Or am I being too nit-picky? > > It's legacy from when we had two adapters. I think a rename with stubs > would be good. Do patch. > -- > David Heinemeier Hansson > http://www.loudthinking.com -- Broadcasting Brain > http://www.basecamphq.com -- Online project management > http://www.backpackit.com -- Personal information manager > http://www.rubyonrails.com -- Web-application framework > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core > _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
