Skip to content

Expose sql_type for columns in resultset #167#168

Open
jstastny-cz wants to merge 1 commit into
mkleehammer:masterfrom
jstastny-cz:nativeSQLTypes
Open

Expose sql_type for columns in resultset #167#168
jstastny-cz wants to merge 1 commit into
mkleehammer:masterfrom
jstastny-cz:nativeSQLTypes

Conversation

@jstastny-cz

Copy link
Copy Markdown

No description provided.

@mkleehammer

Copy link
Copy Markdown
Owner

@jstastny-cz This looks clean, but I'm wary about adding something to the interface without knowing what someone would do with it. I'm not sure how one would make use of this information. What was the use case for this? Thanks.

@jstastny-cz

Copy link
Copy Markdown
Author

@mkleehammer Hello, we used pyodbc for ODBC interface/driver tests. What we needed to do was to check the actual SQL data type returned by the driver.

@matthias-github

Copy link
Copy Markdown

If I understand the PR correctly, then we have the same use case. I am using pyodbc to generate SQL Server create tables DDL based on the result set. If the actual SQL type is returned, we can create exact DDL. Right now we are creating approximate DDL.

@celestialorb

Copy link
Copy Markdown

Yes please! We have a use case that requires us to know the actual SQL type behind the column. We have been unable to come up with a clean workaround.

@bkline

bkline commented Feb 27, 2026

Copy link
Copy Markdown
Contributor

@mkleehammer If the Waiting for info label is still appropriate, wouldn't it be appropriate to describe what information is still needed, beyond what has been provided in the responses above?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants