Użytkownik Ed Leafe napisał:
> The two work on different things. 'Limit' limits the amount of data
> returned by the database; 'fetchmany' is used by the local dbapi
> cursor*after* the data is returned from the database to iterate through the
> returned records a few at a time. The fetch* methods don't affect the amount
> of data returned from the database; they are completely local.
>
I understand what you mean by 'local' but I'm afraid it isn't so simple
as you wish.
It strongly depends on cursor implementation, e.g. named cursors.
But right, it's not a universal solution supported by all backends.
> What it seems you are thinking of is the offset part of the limit
> clause, which is typically used in getting "pages" of data at a time. Right
> now our db layer doesn't support all the different syntaxes, but if you
> enter: biz.setLimit("100 offset 200"), you'll get 100 rows back starting with
> the 200th row.
>
>
I'm using this method now, but it's very unhandy.
I need dynamic cursor that grows on demand, on user request,
e.g. when record pointer reaches page size limit.
But it's very hard to achieve without framework support.
I'm currently working on custom dCursorMixin class that will allow
paged result fetching. I will let you know about results.
--
Regards
Jacek Kałucki
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]
