For the most part, all this module offers is the ability to call existing methods of DBI by different names -
It's not an alternative approach to database programming, as other modules are. Thus far, all others aim at:
- Removing OO, leaving pure simplicity (EZDBI)
- Abstracting SQL, leaving pure perl code that's transformed into SQL (DBIx::Abstract, DBIx::Easy)
- Remove the statement-idea completely (DBIx::DWIW)
The basics of DBI are very good, imho. I want an alternative that has OO, difference between connection and query statement, and does not abstract the SQL. Further, I want it to provide only simple features - no caching, no thousand-and-one ways of binding variables :)
That didn't exist, so I created one myself, just like everyone has done before. I have then documented it, and I have the dummy result object for easing error handling.
If this module would do more than call existing methods by different names, I had probably used another name, DBIx::Extra or something like that. This is not to _add_ functionality (it does remove functionality).
U28geW91IGNhbiBhbGwgcm90MTMgY
W5kIHBhY2soKS4gQnV0IGRvIHlvdS
ByZWNvZ25pc2UgQmFzZTY0IHdoZW4
geW91IHNlZSBpdD8gIC0tIEp1ZXJk