db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-457) Support for equivalent of Oracle's describe command
Date Tue, 17 Oct 2006 02:15:36 GMT
     [ http://issues.apache.org/jira/browse/DERBY-457?page=all ]

Andrew McIntyre resolved DERBY-457.
-----------------------------------

    Fix Version/s: 10.2.1.8
       Resolution: Duplicate

Agreed. Resolving as duplicate of DERBY-1164.

> Support for equivalent of Oracle's describe command
> ---------------------------------------------------
>
>                 Key: DERBY-457
>                 URL: http://issues.apache.org/jira/browse/DERBY-457
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.0.2.1
>            Reporter: simmi iyer
>            Priority: Minor
>             Fix For: 10.2.1.8
>
>
> Most of the databases provide a descibe command that displays the columns and their data
types for a table.
> Using dblookup for this purpose is too heavy-duty. Dblookup is more like reverse engineering
tool i.e. generating schema description from a schema.

-- 
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

        

Mime
View raw message