[
https://issues.apache.org/jira/browse/DERBY-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen closed DERBY-4430.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
All the tests ran cleanly in my environment. Committed revision 836277.
Thanks for working on this, Sylvain!
> Make ij's SHOW and DESCRIBE commands more db agnostic
> -----------------------------------------------------
>
> Key: DERBY-4430
> URL: https://issues.apache.org/jira/browse/DERBY-4430
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.6.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Sylvain Leroux
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: DERBY-4430.ij.out, DERBY-4430.patch, DERBY-4430.sql
>
>
> ij's SHOW and DESCRIBE commands use DatabaseMetaData in order to be portable
> to other databases than Derby, and in many cases they work fine with other
> databases. However, the variants of the commands that take a table name or a
> schema name assume that unquoted identifiers are converted to and stored in
> upper case internally. This is not true for all databases, and since these
> commands don't accept quoted identifiers, there's currently no way to access
> tables/schemas that are not all upper case.
> One possible fix is to make the identifier() method in ij.jj use the
> DatabaseMetaData methods storesLowerCaseIdentifiers(),
> storesMixedCaseIdentifiers() and storesUpperCaseIdentifiers() to decide
> whether it should convert the identifier to lower case, keep it unchanged, or
> convert it to upper case. Currently, that method always converts the
> identifiers to upper case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
