add support for dynamic (non-static) column types in Firebird Proxy #36928
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref #33781.
Changes proposed in this pull request:
FirebirdColumnSizeLoader now retrieves both COLUMN_SIZE and SEGMENT_SIZE for BLOB fields during metadata collection. This enables obtaining the actual length for all dynamic data types.
In FirebirdPrepareStatementCommandExecutor, the calculated column length is stored in the columnLength variable, which is then directly passed to FirebirdReturnColumnPacket and used when forming the DESCRIBE response. As a result, the client receives accurate, real column sizes.
During metadata loading, the computed sizes are stored in the thread-safe FirebirdSizeRegistry and synchronized at the table level. This ensures that additional queries are executed only once — during metadata collection — while subsequent accesses use the cached data.
Before committing this PR, I'm sure that I have checked the following options:
./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.