Skip to content

tds_fix_column_size: Allow full size for output columns.#589

Closed
ucko wants to merge 1 commit into
FreeTDS:masterfrom
ucko:ncbi-2024-05-full-output-size
Closed

tds_fix_column_size: Allow full size for output columns.#589
ucko wants to merge 1 commit into
FreeTDS:masterfrom
ucko:ncbi-2024-05-full-output-size

Conversation

@ucko
Copy link
Copy Markdown
Contributor

@ucko ucko commented May 30, 2024

If an output column of type VARCHAR(n) or the like has no current size, send the type's maximum size; otherwise, the server will fill in only the first character/byte.

Split from #555.

If an output column of type VARCHAR(n) or the like has no current
size, send the type's maximum size; otherwise, the server will fill in
only the first character/byte.

Signed-off-by: Aaron M. Ucko <ucko@ncbi.nlm.nih.gov>
@ucko ucko mentioned this pull request May 30, 2024
@freddy77
Copy link
Copy Markdown
Contributor

freddy77 commented Jun 2, 2024

This looks like a workaround for a problem in upper layer libraries. This function is supposed to make sure we don't screw with protocol level. I know ODBC is supposed to fill what it wants to be the size of the returned data, not leave as 0. I suppose that each library should detect this wrong request and report to the user. Need some more investigation.

@ucko
Copy link
Copy Markdown
Contributor Author

ucko commented Jun 17, 2024

Ah, yeah, looks like the CTLIB API (my primary concern) works fine without this change these days, and already didn't need it in 1.0; I can't readily speak for the other two. Withdrawing accordingly.

@ucko ucko closed this Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants