Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <26044295.1161048516729.JavaMail.jira@brutus>
Date: Mon, 16 Oct 2006 18:28:36 -0700 (PDT)
From: "James F. Adams (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-457) Support for equivalent of Oracle's
 describe command
In-Reply-To: <989998940.1121249590435.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-457?page=comments#action_12442763 ] 
            
James F. Adams commented on DERBY-457:
--------------------------------------

I believe this can be closed.  This functionality appears to be implemented by 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
>
> 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