Well Class::DBI folows different logic and IMHO somehow it feels strange - as the trs80 said :
Class::DBI Intro
Class::DBI can be a powerful way of interacting with your databases, but it really requires a large scale project to reap the benefits and be worth the performance hit you take vs. doing traditional SQL queries. When using Class::DBI you are adding dynamic accessors for much of the data and the overhead of the method calls for all your operations. The benefit is less code, referral integrity (cascading delete), rollbacks in non transaction databases, reduction in lines of code, and increased portability since Class::DBI handles the abstraction across multiple database sources.
If you are working on a large scale database centric application or you want to learn more about OO Perl Class::DBI is a good place to start.
I intended this for simple projects ...
