Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • But I won't be using it because named placeholders like that is already built in to DBD::Pg.

    However if I was trying to write portable code that needed to handle lots of SQL, I definitely would use that.
    • Hi btilly!

      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
  • With respect to DBIx::Dictionary, the concept of phrasebooks as introduced by this article: The Phrasebook Design Pattern [perl.com], the Class::Phrasebook [cpan.org], and the newer (and more actively maintained) Data::Phrasebook [cpan.org] can be a wealthy source of layout for the set of named queries.
    • The point in DBIx::Dictionary is have a real DBI subclass that support the phrasebook design pattern, and make it can even be subclassed by other DBIx::* classes like DBIx::Simple.

      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