Progress being made - need more help.

[Barry G. Sumpter]

I wonder if there is a bit more to it than that.

i.e. pessimistic locking vs optimistic locking etc.

Pessimistic - Open for editing and leave open and locked open until updated.

Optimistic - Open and retrieve field data and close.
             Display field data for changes.
		 Press update button.
		 Open for update, update, and close.

I've always coded for the Optimistic locking.
    Get in, do my thing, get out.
     
The pessimistic locking (lock out) is for the record that has the potential
of being updated by more than one source(/person).

It's been a long time since I worked on a non-proprietary server database.
I was thinking the server would take care of this for you or at least
default to one or the other.

Just got back from a 24klm sprint on the road bike so I might be babbling.

AMB




-----Original Message-----
From: valentina-bounces at lists.macserve.net
[mailto:valentina-bounces at lists.macserve.net] On Behalf Of Sean Wilson
Sent: Sunday, 13 September 2009 6:57 AM
To: Valentina Developers
Subject: Re: Progress being made - need more help.

> In SQLite, Edit is used to make the RecordSet editable and obtain a  
> lock on the record - this is not required in Valentina?

If you look at Ruslan's example of SqlSelect, there is a kReadWrite 
parameter - this makes the cursor editable (you can write to it). I 
think you also need a "server-side" cursor, even though you may not be 
doing anything server related (the kServerSide parameter). Both of these 
parameters will be covered in the WIKI, I'm sure.
So: if you select an existing record, and if the cursor is ReadWrite, 
then you can effectively edit it.
_______________________________________________
Valentina mailing list
Valentina at lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina