-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Network support for bi-directional cursors #7051
Comments
Implementation fully supports the packet prefetch logic existed before. However, it's enabled only for fetchNext() and fetchPrior() operations, other scrolling options discard the priorly prefetched rows (if any) and switch to fetching one-by-one. There should be no performance difference in uni-directional fetching between regular and scrollable cursors, except the server-side caching cost for scrollable cursors. Network protocol changes:
|
Test will be added after migration to pytest/firebird-driver framework. |
QA note. |
This ticket complements #1189. The original implementation of bi-directional (aka scrollable) cursors covered only the engine and API, thus being limited to PSQL and embedded connections using DSQL. The complete implementation, however, should also support scrollable cursors for remote connections as well. The remote protocol needs to be extended for that.
The text was updated successfully, but these errors were encountered: