[Wellington-pm] Perl database stuff....
dan.horne at redbone.co.nz
Mon Jan 8 20:24:33 PST 2007
Whoops - I made a typo in the mail. The last line should read: But I'd be
keen to revisit this if anyone has got any pointers...
> -----Original Message-----
> From: wellington-pm-bounces+dan.horne=redbone.co.nz at pm.org
> [mailto:wellington-pm-bounces+dan.horne=redbone.co.nz at pm.org]
> On Behalf Of Dan Horne
> Sent: Tuesday, 9 January 2007 5:22 p.m.
> To: 'Wellington Perl Mongers (Perl user group)'
> Subject: Re: [Wellington-pm] Perl database stuff....
> > -----Original Message-----
> > From: wellington-pm-bounces+dan.horne=redbone.co.nz at pm.org
> > On Behalf Of Sam Vilain
> > Sent: Monday, 8 January 2007 6:49 p.m.
> > So, once good solution is to have a (hidden to the
> > user) "object version" field, which is sent to the user
> with the rest
> > of their information, and confirmed to match the row during
> the update
> > cycle.
> A lot of the Java ORMs have this approach to optimistic
> locking built in, but as far as I can see, none of the Perl
> ORMs do. I tried looking at the internals of DBIx::Class to
> figure out how to add support for this as a component, but
> basically got swamped by the details - I couldn't figure out
> how to trasparently compare the version numbers. But if
> anyone has any ideas on how to do this if anyone has got any
> Wellington-pm mailing list
> Wellington-pm at pm.org
More information about the Wellington-pm