On Wed, 27 Feb 2002, Dave Rolsky wrote: > You've lost me. Nothing prevents you from having Class::DBI or Alazbo use > ODBC or ADO on Windows or any other OS.
No, but most database abstractions treat ODBC naively as a whole, not a passthrough interface through which you access other databases. Thus abstractions tend to have generic "ODBC" classes, rather than doing what AnyDBD does and figures out the underlying database you're connecting to, and using the appropriate class for that DB. > _Right now_, Alzabo only supports MySQL and Pg directly. If you wanted to > use Alzabo with ODBC, you'd have to write a certain amount of code to > enable it do so. OTOH, If you used DBIx::AnyDBD, which already works with > ODBC, you'd have to write a lot of SQL (depending on how complex your app > is) that you wouldn't have to write with Alzabo. > > Either way you'd have to write some code. With Alzabo, once it existed > you could reuse it for your next ODBC app. With DBIx::AnyDBD, you'd have > to write custom SQL every time. I'm not suggesting people use AnyDBD to write apps with (I do suggest it regularly, but that's not what I was discussing here). I was talking about frameworks. Alzabo (and other DB abstractions) should use DBIx::AnyDBD for it's internal database abstraction. That's all I'm suggesting here. -- <!-- Matt --> <:->Get a smart net</:->
