2 Replies Latest reply on Mar 24, 2016 4:22 PM by Gary Graham-Oracle

    SQL Developer - Describe command with comments bug

    lazyman65

      I'm using SQL Developer 4.1.3.20 (build Main 20.78)

       

      When I enter a describe table command that also contains comments (using either the /* */  or the double dash "--")

      SQL Developer seems to be taking the last word in my comments as the item it is trying to describe.

       

      I tried it a few different ways:

      1) describe  table_1;   /* child table of table_2 */

      RESULT:   ERROR: object */ does not exist

       

      2) describe  table_1;   -- child table of table_2

      RESULTS:  It actually does a describe on table_2 instead of table_1 as requested.

       

      3) describe  table_1;   -- my comment table_that_does_not_exist

      RESULTS:  ERROR: object TABLE_THAT_DOES_NOT_EXIST does not exist

       

      In all instances the comment text is turned grey as expected, so it seems to be recognizing it as a comment.

      I know its a minor issue but was curious if others have same issue?

       

      Curtis.

        • 1. Re: SQL Developer - Describe command with comments bug
          When I enter a describe table command that also contains comments (using either the /* */  or the double dash "--")

          SQL Developer seems to be taking the last word in my comments as the item it is trying to describe.

          As a workaround put the comments on a line by themselves - for example BEFORE the desc statement.

          • 2. Re: SQL Developer - Describe command with comments bug
            Gary Graham-Oracle

            Note that placing the DESC on the same line with a comment also does not work in SQL*Plus...

            SQL*Plus: Release 11.2.0.2.0 Production on Wed Mar 23 18:03:26 2016

             

            Copyright (c) 1982, 2014, Oracle.  All rights reserved.

             

             

            Connected to:

            Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production

             

            SQL> desc employees /* test */

            Usage: DESCRIBE [schema.]object[@db_link]

            SQL>

            ...so it looks like rp0428's suggestion is best.

             

            Edit: And SQLcl behavior in recent internal builds matches SQL*Plus behavior exactly in this regard.