Hi,
>
> I need to solve the "lost update problem" (when two users are editing
> the same database record, one's changes are lost when they both save
> it). I'm thinking about putting original version of the record in the
> hidden field (serialied by Storable) and upon saving do SELECT ... FOR
> UPDATE, compare freshly SELECTed data with original data from the hidden
> field and UPDATE&COMMIT if it corresponds or ROLLBACK otherwise. How
> reasonable is it?
Another idea would be to have a sequence field, which is automaticly
incremented for every update. (You can do this without modifying your code
with a DBIx::Recordset filter) and only passing this sequence number around
and comparing it before updating the record.
> I'd expect a lot of people have the same problem, what do you do? Can
> you think of any way how to make this generaly usable, maybe as some
> general Perl modul? Or perhaps integrate it into Recordset? I happen to
> use Recorset in this project: Gerald, how hard would it be to extend
> Recordset with this feature?
>
Shouldn't be to hard to get this into Recordset, maybe it's enough to just
define some filters
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
