I updated last week DBIx::Placeholder::Named to version 0.07, which is more compliant with DBI - accepting PlaceholderSuffix and PlaceholderPrefix keys - after I presented it on Amsterdam.pm meeting. I can say that I was surprised that nobody yelled with some module doing the exact same thing...
And continuing the things-I-would-like-to-see-on-DBI I wrote DBIx::Dictionary, which tries to add, in the same clean way DBIx::Placeholder::Named does with named placeholders, query dictionary functionality.
It integrates well with DBIx::Placeholder::Named, and currently only supports Config::General configuration files. I'm planning to add support for some SQL compliant configuration file.
I'd like to hear from you what you think about those modules!
That looks useful... (Score:1)
However if I was trying to write portable code that needed to handle lots of SQL, I definitely would use that.
Re: (Score:1)
Actually, the DBIx::Placeholder::Named module was conceived in part of rewriting some functionalities of Tao::DBI, for example inheriting properly DBI, and one of its goals is provide named placeholders to database drivers that doesn't support it (like MySQL and SQLite, for instance).
The cool part about this project is if you want (or need) to deploy your application in some database other than postgresql, you can possibly do that without much effort.
Using DBIx::Dictionary as top layer for DBIx an
Igor Sutton
Phrasebooks (Score:1)
Re: (Score:1)
I wanted to write it with the same thinking I had in mind when wrote DBIx::Placeholder::Named, which was inspired by yours Tao::DBI: small and straight to the point.
Hope this clarifies the idea behind those modules
Igor Sutton