RE: SQL Auditing Help - Sol 10, 10.2.0.2

From: "Powell, Mark" <mark.powell2@xxxxxx>
To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
Date: Wed, 27 Jan 2010 14:29:18 +0000

 
I think it is very bad practice to use an Oracle reserved word as a table 
column name.  I have had trouble querying a couple of Oracle views/base tables 
because the table had column names that were or had become key words.  Having 
to modify SQL statements to place double quotes around the names is both a pain 
and makes for less readable SQL.


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Rich Jesse
Sent: Tuesday, January 26, 2010 5:21 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: SQL Auditing Help - Sol 10, 10.2.0.2

Might it be something silly like using a keyword ("TIMESTAMP") as a column name?

Just a knee jerk to what I see.  I know, I know, Oracle Corp does it.  For this 
particular, I use "TIME_STAMP".  Not sure that helps, but it's a shot...

Rich

> create table oracle.master_audit
> (DBNAME varchar2(10),
> OS_USERNAME varchar2(255),
> TIMESTAMP date,
> USERNAME VARCHAR2(30),
> USERHOST VARCHAR2(128),
> TERMINAL VARCHAR2(255))
> Partition by range (TIMESTAMP)
> (


--
//www.freelists.org/webpage/oracle-l


--
//www.freelists.org/webpage/oracle-l

References:
- SQL Auditing Help - Sol 10, 10.2.0.2
  - From: Newman, Christopher
- Re: SQL Auditing Help - Sol 10, 10.2.0.2
  - From: Rich Jesse

RE: SQL Auditing Help - Sol 10, 10.2.0.2

Other related posts: