Stories
Slash Boxes
Comments

use Perl

All the Perl that's Practical to Extract and Report

use Perl Log In

[ Create a new account ]

Qiang (5577)

Qiang
(email not shown publicly)
http://www.goodspot.ca/

Journal of Qiang (5577)

Thursday May 17, 2007

10:33 AM

database layer separation

[ #33297 ]

we are not writing big Perl software yet. most of them are small and few medium. We started with plain DBI and i am getting tired of writing prepare, execute, selectall_arrayref($sql,{Slice=>{}},@bind) quickly now.

I don't want to introduce ORM just yet as it is a pretty big change and i got lots other things to push to our Perl development. but I definitely see it as the way to go in the long run if our Perl development get bigger.

after some searching, I have found DBIx::Simple - a thin layer to DBI. I like the syntax and it is simple enough. tried asked other monks opinion on perlmonks and no answer so far.

I will spend more time to try it out. if it all goes well, DBIx::Simple will become one of our standard modules among TT and CGI::Application.

List all Journal entries

database layer separation More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

It’s great (Score:1)

by Aristotle (5147)

But I saw that you found my review, so you know that already.

I’m using it now. I have no complaints at all, it’s excellent.
- Re: (Score:1)
  
  by sigzero (5768)
  
  Where is your review?
  - Re: (Score:1)
    
    by Aristotle (5147)
    
    Here you go: A brief survey of the DBI usability layer modules on the CPAN [perlmonks.org]
  - Try Rose (Score:1)
    
    by Ron Savage (5224)
    
    Rose is another interface to databases. IMHO it's the best because it has the most Perl-like interface, so it fits effortlessly into the way Perl programmers think.
    - Re: (Score:1)
      
      by Aristotle (5147)
      
      If you want to go down that road, I’d suggest DBIx::Class instead.
DBIx::Dictionary (Score:1)

by izut (6269)

I have the same problem you're having, so I wrote DBIx::Dictionary, which is not a replacement for DBIx::Simple, but helps you to have your SQL logic separated from your program. Used along with DBIx::Placeholder::Named, you can have a good abstraction layer for your applications :-)

Take a look if it looks promising, and drop a note if you have some problem ;-)

--
Igor Sutton