[ http://issues.apache.org/jira/browse/DERBY-1164?page=all ]
Håvard Mork updated DERBY-1164:
-------------------------------
Attachment: 1164_4.diff
Your suggestions are very helpful. I am attaching a new patch (1164_4.diff)
with some changes:
* Modified JDBCDisplayUtil to display a selection of columns, with column
widths set by ij.jj
* Added 'show indexes'
* Verifying that tables exist
There are still some problems:
* There are no standard way of getting current schema. Now using 'values
current schema'. For non-Derby dbms-es, the failure to return current schema
will lead to that i.e. DESCRIBE will return matching table names in all schemas
(with a SCHEMA column, though). Any smarter way to solve this?
* What information to print and column size is a subjective matter. It is
difficult to choose between one-line-fits-all, and ensuring that column values
are output fully.
As for viewing fk/pk in tables, I've chosen not to implement it now, but that
could be implemented later.
The patch passes derbytools and derbylang.
> '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, 1164_3.diff, 1164_4.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
