Speaking of cursors ...

[Ruslan Zasukhin]

on 7/4/03 20:10, Tim Davis at timdavis at amug.org wrote:

> Hi,
> 
>   I see the advantage of holding open a cursor when server-side, but
> much less so for client-side. In an effort to minimize restrictions due
> to record locking of large queries, is there a capability in SQL and/or
> Valentina to limit the size of the cursor, ie. max number of records to
> hold in cursor? 

In the current version no.

> (Then of course one could create a new cursor for the
> next batch of the 'found set', ie. two parameters to define the cursor
> limits Start = 50, Size = 25.) (I have not found this in my SQL books,
> but have used this in database related software.) If someone does a
> query and the found set is hundreds of records, they may need all of
> them, and it may be wasteful to open them all as ReadWrite locking out
> other users. I think a limited cursor size might help.

Hmm guys.

I just only have realize that CLIENT CURSOR do NOT lock records on server
side.

As only copy of result table is loaded to the RAM of local computer,
Sever unlock records.

So we can use CLIENT cursor even for LOCAL dbs as flag/command to create TMP
table with result of query and unlock records immediately .
In this way you get stable SNAPSHOOT of data, and unlock records in main
table.

Although of course creation of TMP table on HDD will take some time.

-- 
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
-------------------------------------------------------------