db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2019) IJ's describe command does not handle quotes very well
Date Mon, 30 Oct 2006 14:10:16 GMT
IJ's describe command does not handle quotes very well
------------------------------------------------------

                 Key: DERBY-2019
                 URL: http://issues.apache.org/jira/browse/DERBY-2019
             Project: Derby
          Issue Type: Bug
          Components: Tools
    Affects Versions: 10.2.1.6, 10.3.0.0
            Reporter: John H. Embretsen
            Priority: Minor


In IJ, the describe <table | view> command does not handle quotes very well. Current
behavior is:

a) Double quotes:

IJ does not recognize describe command when encountering double quotes.

    ij> create table "CamelCaseTable" (col1_in_cct int);
    0 rows inserted/updated/deleted
    ij> describe "CamelCaseTable";
    ERROR 42X01: Syntax error: Encountered "describe" at line 1, column 1.

I'm assuming that it should be possible to execute the describe command on case-sensitive
table names.

b) Single quotes:

IJ describes all tables in current schema when encountering two single quotes after the describe
command.

    ij> create table table1 (col1_table1 int);
    0 rows inserted/updated/deleted
    ij> create table table2 (col1_table2 int);
    0 rows inserted/updated/deleted
    ij> describe '';
    COLUMN_NAME         |TYPE_NAME|DEC&|NUM&|COLUM&|COLUMN_DEF|CHAR_OCTE&|IS_NULL&
    ------------------------------------------------------------------------------
    COL1_TABLE1         |INTEGER  |0   |10  |10    |NULL      |NULL      |YES
    COL1_TABLE2         |INTEGER  |0   |10  |10    |NULL      |NULL      |YES
    
    2 rows selected

In case b), it does not make a difference whether the single quotes actually surround a valid
table name, some garbage, or nothing at all.

I must admit that b) seems like a useful feature, listing all columns in all tables in a schema,
but it's usage is not very intuitive, nor is it documented, so this may be a bug.


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