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

display_size and internal_size of Cursor.description or incorrect #3103

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

display_size and internal_size of Cursor.description or incorrect #3103

monetdb-team opened this issue Nov 30, 2020 · 0 comments
Labels
bug Client interfaces normal

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2012-06-18 16:23:47 +0200
From: @gijzelaerr
To: clients devs <>
Version: 11.9.7 (Apr2012-SP2) [obsolete]

Last updated: 2012-07-17 13:57:43 +0200

Comment 17367

Date: 2012-06-18 16:23:47 +0200
From: @gijzelaerr

User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0
Build Identifier:

This information is not in a query result and can not be retrieved without issuing a seperate SQL query. This would mess with the current API state, so probably not a good idea. The DB API specs dictate that these values should then be 'None'.

Reproducible: Always

Comment 17385

Date: 2012-06-26 11:06:07 +0200
From: @sjoerdmullender

You should mine the ODBC and JDBC implementations. They manage to figure out the information.
In particular, ODBC uses the call mapi_set_size_header() (which sends an "X" command "sizeheader 1" to the server--this can be done in Python as well) to get extra information in the result set header of each subsequent query. Also, the prepare variant of a query returns all sorts of useful information.

Comment 17432

Date: 2012-07-09 13:51:18 +0200
From: @gijzelaerr

This bug has been resolved in the Jun2012 branch.

http://dev.monetdb.org/hg/MonetDB/rev/002c2ba3b38a

Comment 17433

Date: 2012-07-09 13:52:02 +0200
From: @gijzelaerr

I should have said 'resolved in Jul2012 branch'.

sorry.

Comment 17484

Date: 2012-07-17 13:57:43 +0200
From: @grobian

Fix released in Jul2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Client interfaces normal
Projects
None yet
Development

No branches or pull requests

1 participant