Skip to content

Conversation

@aafemt
Copy link
Contributor

@aafemt aafemt commented May 20, 2025

No description provided.

@aafemt aafemt marked this pull request as ready for review May 21, 2025 16:09
@aafemt
Copy link
Contributor Author

aafemt commented May 23, 2025

Commit "Return isc_dsql_error prefix" has been undone because it caused more problems than solved.

@aafemt aafemt marked this pull request as draft May 30, 2025 16:23
@aafemt aafemt marked this pull request as ready for review May 31, 2025 21:03
@aafemt aafemt marked this pull request as draft June 1, 2025 08:18
@aafemt aafemt marked this pull request as ready for review June 1, 2025 13:16
@mrotteveel
Copy link
Member

@dyemanov @hvlad Can one on you review and merge this?

@dyemanov dyemanov self-requested a review June 15, 2025 13:46
@aafemt
Copy link
Contributor Author

aafemt commented Jun 17, 2025

@asfernandes Do you have a testcase that fail on this build?

@dyemanov
Copy link
Member

dyemanov commented Jul 4, 2025

Just one question: are your changes really needed for VARCHAR parameters?

@aafemt
Copy link
Contributor Author

aafemt commented Jul 4, 2025

IMHO, yes. Some libraries do with them the same as with CHAR: overrun maximum length in characters as derived from maximum length in bytes while still fit to the storage. Besides, it suits to the standard's requirement to silently cut trailing blanks if they don't fit on store. Lastly it may help with API backward compatibility if longer VARCHARs are ever allowed.

@dyemanov dyemanov merged commit 35aae92 into FirebirdSQL:master Jul 4, 2025
23 checks passed
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.

3 participants