Gerald Richter wrote:
>
> >
> > This definitely saves the overhead of passing around another version
> > of data, but requires a modification of all table structures. I don't
> > see how it can be done with a Recordset filter, could you give me a
> > clue?
> >
>
> $db -> TableAttr ($tabname, '!Filter', { '\\updatecnt' => [ sub
> 'updatecnt_seq.nextVal' }, undef, DBIx::Recordset::rqUPDATE ] }) ;
>
After a tiny bit of thinking maybe simple field
last_update TIMESTAMP
would be even simpler. It could even be automatically updated from a
DB trigger, so I'd only need to modify UPDATEs as you proposed
$set -> Update (\%params, { id => $fdat{id}, last_update =>
$fdat{last_update} })
Does Recordset's Update method return how many rows where updated? How
will I know it failed?
- Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
