[ http://issues.apache.org/jira/browse/DERBY-1164?page=comments#action_12373519 ]
Daniel John Debrunner commented on DERBY-1164: ---------------------------------------------- Copying the metadata queries into ij ties ij directly to a specific version of the database engine. I don't believe this is a good direction. ij is intended as a fairly neutral JDBC client that works against any database engine. While it may be ok to tailor ij for Derby, having to need a specific version of ij to talk to a specific version of Derby will cause problems. It would be interesting for you to provide a patch that uses the DatabaseMetData methods directly and displays the resultant ResultSets using the standard ij code. The we could think about the "nice layout", what's nice to you maybe horrible to someone else. > 'show tables' and 'describe' commands in ij > ------------------------------------------- > > Key: DERBY-1164 > URL: http://issues.apache.org/jira/browse/DERBY-1164 > Project: Derby > Type: New Feature > Components: Tools > Reporter: Håvard Mork > Priority: Trivial > Attachments: 1164.diff, 1164_2.diff > > New users migrating from mysql are familiar with commands 'show tables' and > 'describe' to respectively display all permanent tables, and show fields in > a given table. These are not standard sql, but I suggest to implement them > only in the IJ tool for user-friendliness. > As suggested in db-dev, using DatabaseMetaData should provide the necessary > query strings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
