Oracle between 12 and 18 changed the max_identifier_length. Normally using the version property of a connection works to know what the max len is, but since Oracle allows customizing the compatible version, it may not be correct in all cases.
A property on the connection would simplify this use case.
This has came up in sqlalchemy here sqlalchemy/sqlalchemy#11879.
Sqlalchemy at the moment uses the current query "SELECT value FROM v$parameter WHERE name = 'compatible'" to get the compatible version and from it set the max_identifier_length. The issue is that the v$parameter view (?) may not be visible to the user of the connection
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4