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.
  • Hey, nice evil idea to create packages for all tables. I wrote [0beta.co.uk] a similar module for the Google Gears database with JavaScript and I might steal the idea :)
  • Years ago I worked on a very impressive ORM that was written in-house (not by me). It had lots of kinks, but one of the nice things was something like this:

    "Gimme a report of sales per store in Texas, per salesman."

    Um, OK.

    # The actual API was different
    my $dataset = dataset({
        data  => [qw/sales store salesman/],
        where => { state => 'Texas' },
        group => ['salesman'],
    });

    Notice anything interesting? There's no FROM or complicated joins. You just

  • For doing the small scale stuff I like DBIx::Simple's approach of pure DBI + syntactic vitamins.

    For the cases when going full ORM is overkill.
  • I would just like to second the comment on DBIx::Simple --- the philosophy of this module: $dbh->query(what_you_want_back() is excellent and it would be great to talk to SQLite through this interface rather than a clunky ORM. DBIx::Simple plus SQLite without locking problems would be great. Maybe the ORLite layer should create temporary tables to avoid locking up the db by taking a journal/log of updates and writing to temporary tables (i.e., files)? A similar temporary table technique was used to over