On Wed, 27 Feb 2002, Matt Sergeant wrote: > > Just like with DBIx::AnyDBD, you'd have to have one subclass per RDBMS, > > and custom code it for each (well, actually MySQL and Postgres share the > > same syntax for outer joins these days). > > > > But with Alzabo you wouldn't need to do that! Of course, it only support > > MySQL and Pg right now ;) > > Right, and only on Unix (i.e. not transparent through ODBC/ADO). This is > why I said "broken" in an earlier email.
You've lost me. Nothing prevents you from having Class::DBI or Alazbo use ODBC or ADO on Windows or any other OS. _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. Depending on how complex your apps are, one or the other may be preferable. -dave /*================== www.urth.org we await the New Sun ==================*/
