Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ODBC Statements do not respect the driver SQL_ATTR_MAX_ROWS setting. [ODBC74] #73

Open
firebird-automations opened this issue Sep 21, 2009 · 6 comments
Open

ODBC Statements do not respect the driver SQL_ATTR_MAX_ROWS setting. [ODBC74] #73

firebird-automations opened this issue Sep 21, 2009 · 6 comments
Assignees
@irodushka @alexpotapchenko
Labels
affect-version: 2.0 affect-version: 3.0 Beta priority: minor type: bug

Comments

@firebird-automations
Copy link

Submitted by: Clinton L. Warren (justdoro)

The driver does not respect the SQL_ATTR_MAX_ROWS setting.

Select a table with n rows (say, 100).

Create a select statement that has its SQL_ATTR_MAX_ROWS setting set to 10 rows.

Executing the select will return all 100 rows.

Similar tests against the SQL Server ODBC driver and the MySQL ODBC driver return 10 rows.
@firebird-automations
Copy link
Author

Commented by: Clinton L. Warren (justdoro)

This was tested with Delphi using the ADO components by setting the ADOQuery.MaxRecords property to 10. Using ODBCTrace showed that ADO is setting SQL_ATTR_MAX_ROWS on the ODBC sql statement.

@firebird-automations
Copy link
Author

Modified by: @alexpotapchenko

assignee: Alexander Potapchenko [ lightfore ]

@firebird-automations
Copy link
Author

Modified by: @alexpotapchenko

Fix Version: 2.1 Beta [ 10410 ]

@firebird-automations
Copy link
Author

Modified by: @alexpotapchenko

Version: 2.0 RC2 [ 10320 ]

Fix Version: 2.1 Beta [ 10410 ] =>

@firebird-automations
Copy link
Author

Modified by: @alexpotapchenko

Version: 2.0 [ 10044 ]

Version: 2.0 RC2 [ 10320 ] =>

@firebird-automations
Copy link
Author

Commented by: Julien Nabet (julien2412)

I submitted a patch to review here:
#1

@irodushka irodushka self-assigned this Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@irodushka irodushka

@alexpotapchenko alexpotapchenko

Labels
affect-version: 2.0 affect-version: 3.0 Beta priority: minor type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@irodushka @alexpotapchenko @firebird-automations