Server side cursor in Valentina Server // Codebase Database API

[Ruslan Zasukhin]

On 8/9/06 1:56 AM, "Robert Sneidar" <bobs at twft.com> wrote:

Hi Robert,

> This is fine for manageably sized tables. But I have read posts to
> the runrev list that trying to load large cursors can crash
> Revolution. It has been suggested that limits be issued in SQL
> statements to ensure the size of a cursor is not too large.

1) well, I think you have hear this problem about e.g. MySQL, which has only
client-side cursors. I.e. It loads all found records into RAM of client.
Of curse this will not work for big results.

Valentina Server has as client side cursors so Server-side cursors, which
load into Client only required record. In Valentina 2.5 we even will improve
this technique.

> At that  point I would be paging through a table, especially for report
> generation, and I am not sure how to do that.

Well, report generation best of all todo on server side.
And move to client only result.
 
> But all objections aside, I am going to have to get into the nuts and
> bolts of SQL to make this happen, AND in the process of making the
> old Foxpro code into Revolution code, I am going to have to rewrite
> whole sections of code to account for the new SQL methods, and that
> is the really daunting thing for me. If I can use the "navigational
> model" then my recoding becomes quite manageable.

I think you need play with this and that ways.

See results. Again, may be exists sense for you write own small
layer-wrapper around db.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]