Slash Boxes
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

use Perl Log In

Log In

[ Create a new account ]

jk2addict (4946)

  (email not shown publicly)
AOL IM: chrislaco (Add Buddy, Send Message)
Yahoo! ID: (Add User, Send Message)

Journal of jk2addict (4946)

Monday October 22, 2007
03:59 PM

If I Had a Hammer

[ #34732 ]

After a thread on the dbix-class mailing list about rollback and transactions, I find myself wanting a language wide transaction scope for Perl.

One of the things I like about .NET 2.0 is the transaction scope, wherein anything that is transaction-aware can participate in a transaction scoped block of code, even things that have nothing to do with databases, like file system operations.

If I wanted to update a db (DBI, or DBIC, RDBO, Muldis, an any other) record, update a copy in subversion, plop out a new static html page, and send a confirmation email, it would be keen to wrap that all up in one transaction scope.

My brain melts at the thought of how one would even go about making such a framework in Perl, but it would be a damn fun project.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I fully expected to see a reply already, along the lines of "this is how you'll do it in perl 6..."
    • I've seen the P6 page on transactional scalars, ref, etc, but it still reads a little thin on the overall picture. I didn't do a lot of searching though.

      And of course, that's Perl6, which at this point isn't 'real' for me yet.
  • ...has a comment that its on_release can be used to implement transactional mechanics. That comment was there for good reason - I've actually used it that way.

    It is a little bare-bones though. OK, a lot bare-bones.