cursor/api

[Ruslan Zasukhin]

On 2/10/05 1:42 AM, "Ralf Sander" <ralf at end-if.de> wrote:

> Cursor way:
> I need to use "knolocks" because "kreadonly" lets only one user read a
> record.

NO!

Many users can read. Nobody will not be able write.


> Works good so far. If a record has been deleted outside the cursor, the
> record has just no values in the cursor, the record don't become nil.

> Also no problem with reused RecIDs. Will I get the same results with a
> served database?

Yes, but you describe strange things.

> But I see a possible problem with speed. I have to store a sql search
> request as a string for the current view of one user. If the user adds
> a (existing-not new)  record to the current view, the sql request has
> to be modified and re-performed. Could this be a problem, if the
> current search is very complex respectively would the api way be much
> faster?

If you use Vcursor and add records using Vcurosr.AddREcord()
Then new record is right here.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------