🚀 go-pugleaf

> Hi, Piero!

Hi Mark!

> BeginTrans and Commit / Rollback are not concurrency controls - they are
> to allow you to safely back out of incomplete operations where multiple
> updates must fully complete or not have any effect at all. You still
> need to use Edit() to lock the records you are about to change.
> Regardless of whether you use transactions, you can attempt incompatible
> updates, but client-server databases should generally detect that and
> throw exceptions which you can use for rollback and retry.

Sorry, I did not mean to doubt of your skills. I was just saying that IMHO
if you want to assure consistency in a multi-user environment you have to
use transaction control. period.

> In any event, best performance is with server side cursors, because then
> only the minimum records needed are transmitted across the network. Also
> forward only cursors, though rarely practical for non web apps, are
> fastest. Static cursors are second fastest.

Thanks. You're saying that it is possible to have a batch update system with
server side cursors? Anyway I'm gonna try this in a few days.

>
> If you have to use a client side cursor, make sure to use moModifiedOnly
> for the MarshalOptions.

Yes, I supposed.
BTW, congratulations for the Temporal Doorway, I liked its look and feel.