Pathologically Eclectic Rubbish Lister | |
PerlMonks |
Re^7: DB persistence framework for Perl Classesby tadamec (Beadle) |
on Oct 18, 2004 at 19:35 UTC ( [id://400295]=note: print w/replies, xml ) | Need Help?? |
Are you saying that you want to update some objects and then commit some of your changes but not all of them? Nope. Just plain old, simple transactions.
Say, for example, I'd like to update 10,000 records in a database from a command-line script and I'd also like to read/update one record at a time in a web page. Currently, I have two different Class::DBI ancestors to handle the one-off changes, and another to handle batching the mass updates into smaller chunks so the transaction logs in the database don't get hammered. Some of my problems stem, I'm sure, from enforcing least-privilege at the database and application levels; my Apache database user has privileges to update a very limited set of tables and can read almost all the tables, where the command line processes can update most tables. The web user updates one record at a time, while the command line process almost always updates in large batches. Class::DBI seems to get confused in the Apache environment if I have transactions enabled in the Web base class and I haven't figured out a way around this other than doing a $obj->dbi_commit() after every read. This is, in my opinion, really a Bad Idea, as you shouldn't commit a record that you haven't changed and probably don't have write access to begin with.
In Section
Meditations
|
|