Re^4: Class::DBI weirdness sql error

[trwww]

I'll concede that Class::DBI doesn't abstract the database perfectly. Not even close. But CDBI abstracts a database well enough to be extremely useful when used within its constraints. When I see someone suggesting otherwise, I feel compelled to respectfully object.

To keep the talk technical, It seems that your main complaint is that CDBI "gets in the way..." Whenever CDBI is getting in your way, you simply do a:

my $dbh = CDBI::SubClass->db_Main

and you are back to doing plain database calls. So at the very least, it is a very handy database connection manager.

Regards,

[JavaFan]

Oh, I'm quite aware how to "get around" Class::DBI. I do that all the time. That's I'm doing it all the time says enough, doesn't? ;-)

And I still maintain that it doesn't abstract the database one iota. I won't deny you (and many others) find it useful, but that doesn't mean it abstracts the database.