Re: Is this a bug?

From: DA Morgan <damorgan_at_psoug.org>
Date: Thu, 04 Jan 2007 08:52:18 -0800
Message-ID: <1167929539.262625@bubbleator.drizzle.com>

Anurag Varma wrote:
> DA Morgan wrote:

>> EscVector wrote:
>>> Anurag Varma wrote:

> -snip-

>>>> You are right .. it should be a bug. However, probably not easy
>>>> to fix ...
>>>>
>>>> You might want to read Bug 4703738 where this is discussed.
>>>>
>>>> Anurag
>>> Quote from doc:
>>> This issue is fixed in
>>>     * 9.2.0.8 (Server Patch Set)
>>>
>>> Well they didn't kill this bug.  It is back again in 10.2.0.2  :)
>> I'm not quite sure I can agree that something violating Oracle's advice,
>> and generating an error, is a bug. At least not as long as the word
>> TIMESTAMP is present in gv$reserved_words.
>> --
>> Daniel A. Morgan

>
> The bug (or inconsistency as you might want to call it) is that oracle
> should
> not allow a column name and datatype to be of the same name IF the
> column
> name is not enclosed in double quotes.
>
> So create table test (timestamp timestamp); should throw an error
> since all other datatypes do throw an error.

I would agree that throwing an error would be a "nice to have" but I wouldn't call it a bug any more than I would expect Oracle to hold my hand if I am fool enough to write this code.

CREATE SYNONYM dummy FOR dual;

set serveroutput on

DECLARE
  dummy VARCHAR2(1);
BEGIN
   SELECT dummy
   INTO dummy
   FROM dummy;

   dbms_output.put_line(dummy);
END;
/

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

Received on Thu Jan 04 2007 - 10:52:18 CST