Skip to content

Conversation

@ucko
Copy link
Contributor

@ucko ucko commented May 30, 2024

Let column_size exceed column_cur_size for BLOBs, whose reported maximum may have been merely nominal, and doesn't really matter because their storage is generally allocated separately, based on actual result sizes.

Split from #555.

Let column_size exceed column_cur_size for BLOBs, whose reported
maximum may have been merely nominal, and doesn't really matter
because their storage is generally allocated separately, based on
actual result sizes.

Signed-off-by: Aaron M. Ucko <[email protected]>
@freddy77
Copy link
Contributor

freddy77 commented Jun 2, 2024

I suppose server should not report a size lesser than the returned data (that is should consider TEXTSIZE setting). But yes, currently code won't have any issue with this and maybe is not respected for data sent to the server. Some tests here are maybe too strict. On the other side these tests should not be compiled in production and so they should not trigger and I don't see any failure during testing. Did you manage to reproduce?

@ucko
Copy link
Contributor Author

ucko commented Jun 17, 2024

I didn't directly encounter a situation where this change helped, but AFAICT it did in fact originally compensate for a server-side bug (probably in an OpenServer instance, quite possibly in instance-specific code) that has since been fixed. 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