in reply to Re^8: Input on Lightweight SQL Query Templating?
in thread Input on Lightweight SQL Query Storage?

"tell me your db layout", which is pretty annoying when you're still developing the app and your layout is this in a flux

I agree. DBIx::Class gets around this (Rose::DB might too, I'm not sure) with auto loading schema. It also has facilities to do bulk operations on resultsets, not just rows. The only real downside to ORMs which are at the level and quality of Rose and DBIC are that they are slower than straight DBI. Yes, they are only harder to follow/code at first but once you are in them they make reading the intention of DB code much easier than wading through SQL and will shave off nearly all the boring repetitive parts and can even make the really difficult parts pretty easy (like versioning, object inflation, and normalization of behavior across DB engines).

  • Comment on Re^9: Input on Lightweight SQL Query Templating?

Replies are listed 'Best First'.
Re^10: Input on Lightweight SQL Query Templating?
by siracusa (Friar) on Apr 28, 2009 at 02:30 UTC
    "tell me your db layout", which is pretty annoying when you're still developing the app and your layout is this in a flux

    I agree. DBIx::Class gets around this (Rose::DB might too, I'm not sure) with auto loading schema.

    FWIW, Rose::DB::Object can indeed inspect your database and create appropriate Perl classes, either in memory or on disk as *.pm files, including column data types, foreign keys, and other relationships between tables. There's an example in the tutorial.

      I had a feeling. Rose's reputation is great. The only reason I haven't used it is I came to DBIC (via CDBI) first and it hasn't let me down yet. :) I think it's fabulous that Perl boasts two ORMs of this caliber.