Re: The Oracle Inconsistencies List -- please add to it!

From: <johnvue_at_gte.net>
Date: Thu, 13 Aug 1998 11:48:31 GMT
Message-ID: <6qujr7$rl8$1@news-1.news.gte.net>

On Wed, 12 Aug 1998 03:27:51 GMT, johnvue_at_gte.net wrote:
>Why do your fingers want to type "select name from v$logfile" or
>"create tabespace data1 default storage (pct_increase 0)" even though
>they don't work? Because Oracle makes it harder than it has to be.
 

>Actually, pctincrease is a reserved word so it couldn't be used as
acolumn name.  

Not quite true. Take a look at the examples below.

 Oracle7 Server Release 7.3.3.4.0 - Production Release  With the distributed and parallel query options  PL/SQL Release 2.3.3.4.0 - Production

 SQL> create table z1 (pctincrease number(9));

 Table created.

As you can see PCTINCREASE is a reserved word but Oracle allows it to be used as a column name. Now there DEFINITELY are reserved words that can't be used as column names unless you surround them with quotes. The following examples illustrate this point:

 SQL> create table z1(CREATE number(9));  create table z1(CREATE number(9))

                *

 ERROR at line 1:
 ORA-00904: invalid column name  

 SQL> create table z1("CREATE" number(9));

 Table created.  

See what you get for not testing your own advice??? Oracle makes you pay :). As a matter of fact, you've just added another "inconsistency" to the list! Oracle requires some reserved words with quotes and allows others without quotes. Thanks! Received on Thu Aug 13 1998 - 06:48:31 CDT