Skip to content

Conversation

Meehdi
Copy link

@Meehdi Meehdi commented Oct 9, 2025

Description

This PR improves the detection of Oracle's MAX_STRING_SIZE configuration by querying the database_properties system view directly instead of relying on exception-based control flow.

Changes

  • Replace the varchar2(32000) cast attempt with a direct query: SELECT property_value FROM database_properties WHERE property_name = 'MAX_STRING_SIZE'

Related Issue

Fixes HHH-19852


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.


https://hibernate.atlassian.net/browse/HHH-19852

@hibernate-github-bot
Copy link

hibernate-github-bot bot commented Oct 9, 2025

Thanks for your pull request!

This pull request appears to follow the contribution rules.

› This message was automatically generated.

@Meehdi Meehdi force-pushed the HHH-19852-oracle-extended-maximum branch from 37ba8ec to 97595c4 Compare October 14, 2025 08:00
…ct query

Query database_properties view directly instead of attempting a
varchar2(32000) cast to determine if MAX_STRING_SIZE is EXTENDED.

HHH-19852 fix condition

HHH-19852 fix fomatting problem
@Meehdi Meehdi force-pushed the HHH-19852-oracle-extended-maximum branch from 97595c4 to 223e55e Compare October 14, 2025 16:26
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