Bug #91550 | DatabaseMetaData specifies incorrect extra name characters | ||
---|---|---|---|
Submitted: | 4 Jul 2018 21:47 | Modified: | 9 Apr 2024 20:49 |
Reporter: | Raphael Enns | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.1.46 / 6.0.6 / 8.0.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[4 Jul 2018 21:47]
Raphael Enns
[5 Jul 2018 12:25]
Chiranjeevi Battula
Hello Raphael Enns, Thank you for the bug report. Verified based on internal discussion with dev's. Thanks, Chiranjeevi.
[9 Apr 2024 20:49]
Daniel So
Posted by developer: Added the following entry to the C/J 8.4.0 changelog: "DatabaseMetaData.getExtraNameCharacters() returned '#' and '@', which are not allowed in unquoted schema object names. With this fix, it returns '$' as the only "extra" character allowed in unquoted identifiers."