Is this a bug?

DA Morgan wrote:
>
> When you buy an car ... do you expect the dealer to teach you how to
> drive it?

Actually, BMW, Land Rover and some more obscure makes do make it an
option (potentially free for BMW).

http://www.bmwusa.com/bmwexperience/...ancecenter/faq
http://www.landrover.de/us/en/Owners...s_Overview.htm
http://www.saleen.com/events_store_grand_opening.htm

jg
--
@home.com is bogus.
"Without getting into all of your high-falootin' scientific
mumbo-jumbo, can you give me a good rule of thumb?" - Pete Wrigley

On Thu, 04 Jan 2007, damorgan-at-psoug.org wrote:
> Serge Rielau wrote:
>
>>> 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.
>> I wish my customers were as tolerant as you are....
>
> When a company goes to the effort to put a reference of keywords into
> their product then it becomes the obligation of the developers and
> DBAs to use it.
>
> When you buy an car ... do you expect the dealer to teach you how to
> drive it?

If there are differences between the platform independent way of driving
cars, I would expect them to tell me about it.

--
Galen Boyer

On Thu, 04 Jan 2007, damorgan-at-psoug.org wrote:
> Serge Rielau wrote:
>
>>> 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.
>> I wish my customers were as tolerant as you are....
>
> When a company goes to the effort to put a reference of keywords into
> their product then it becomes the obligation of the developers and
> DBAs to use it.
>
> When you buy an car ... do you expect the dealer to teach you how to
> drive it?

If there are differences between the platform independent way of driving
cars, I would expect them to tell me about it.

--
Galen Boyer

On Thu, 04 Jan 2007, damorgan-at-psoug.org wrote:
> 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;
> /

You don't think that out of the thousands of people using the product,
there aren't quite a few people who would make this simple mistake?

--
Galen Boyer

On Thu, 04 Jan 2007, damorgan-at-psoug.org wrote:
> 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;
> /

You don't think that out of the thousands of people using the product,
there aren't quite a few people who would make this simple mistake?

--
Galen Boyer

What's in a namespace wrote:
> "DA Morgan" schreef in bericht
> news:1167929230.952378-at-bubbleator.drizzle.com...
>> Serge Rielau wrote:
>>
>>>> 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.
>>> I wish my customers were as tolerant as you are....
>> When a company goes to the effort to put a reference of keywords into
>> their product then it becomes the obligation of the developers and DBAs
>> to use it.
>>
>> When you buy an car ... do you expect the dealer to teach you how to
>> drive it?
>> --
>> 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
>
> No, but I do not expect some hidden pocket somewhere with a small booklet in
> it titled: 'Which buttons not to push...'
> Well anyway, we have seen some 'reserved word' problems before, so I guess
> you're right after all ;-) and thank heavens your not a car dealer!
>
> Shakespeare
> (What's on a button?)

Why is it everyone keeps being so thankful I don't sell cars? Far worse
if I were a politician. Far far worse. ;-)

But you are correct in one respect. While they've done a decent job
with SQL keywords ... there are some rather ugly gaps when you get
to PL/SQL. This just didn't happen to be one of them.
--
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

What's in a namespace wrote:
> "DA Morgan" schreef in bericht
> news:1167929230.952378-at-bubbleator.drizzle.com...
>> Serge Rielau wrote:
>>
>>>> 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.
>>> I wish my customers were as tolerant as you are....
>> When a company goes to the effort to put a reference of keywords into
>> their product then it becomes the obligation of the developers and DBAs
>> to use it.
>>
>> When you buy an car ... do you expect the dealer to teach you how to
>> drive it?
>> --
>> 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
>
> No, but I do not expect some hidden pocket somewhere with a small booklet in
> it titled: 'Which buttons not to push...'
> Well anyway, we have seen some 'reserved word' problems before, so I guess
> you're right after all ;-) and thank heavens your not a car dealer!
>
> Shakespeare
> (What's on a button?)

Why is it everyone keeps being so thankful I don't sell cars? Far worse
if I were a politician. Far far worse. ;-)

But you are correct in one respect. While they've done a decent job
with SQL keywords ... there are some rather ugly gaps when you get
to PL/SQL. This just didn't happen to be one of them.
--
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

hpuxrac wrote:
> Jim Smith wrote:
>> In message <1167866459.800948@bubbleator.drizzle.com>, DA Morgan
>> writes
>>> EscVector wrote:
>>>> Anurag Varma wrote:
>>>>> EscVector wrote:
>>>>>> As demonstrated below, a table can be created with data type
>>>>>> "timestamp" as a column name.
>>>>>>
>>>>>> This causes a subsequent issue when creating triggers.
>>>>>>
>>>>>> Shouldn't the table create throw a "ORA-00904: : invalid identifier"
>>>>>> error?
>>>>>>
>>> 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.
>> The "bug" is that it *isn't* generating an error.
>
> Ahh but now you are trying to imply that the person responding is
> actually trying to read the post and trying to understand it instead of
> just blasting out spam.

I confess. My post was pure spam. I wanted everyone to purchase a copy
of gv$reserved_words from me. I have three copies on the lot that were
previously owned by a little old lady who only queried them on Sundays
after church. And they all come with a full warranty. ROFLOL!
--
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

hpuxrac wrote:
> Jim Smith wrote:
>> In message <1167866459.800948@bubbleator.drizzle.com>, DA Morgan
>> writes
>>> EscVector wrote:
>>>> Anurag Varma wrote:
>>>>> EscVector wrote:
>>>>>> As demonstrated below, a table can be created with data type
>>>>>> "timestamp" as a column name.
>>>>>>
>>>>>> This causes a subsequent issue when creating triggers.
>>>>>>
>>>>>> Shouldn't the table create throw a "ORA-00904: : invalid identifier"
>>>>>> error?
>>>>>>
>>> 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.
>> The "bug" is that it *isn't* generating an error.
>
> Ahh but now you are trying to imply that the person responding is
> actually trying to read the post and trying to understand it instead of
> just blasting out spam.

I confess. My post was pure spam. I wanted everyone to purchase a copy
of gv$reserved_words from me. I have three copies on the lot that were
previously owned by a little old lady who only queried them on Sundays
after church. And they all come with a full warranty. ROFLOL!
--
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

Niall Litchfield wrote:
> DA Morgan wrote:
>> Serge Rielau wrote:
>>
>>>> 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.
>>> I wish my customers were as tolerant as you are....
>> When a company goes to the effort to put a reference of keywords into
>> their product then it becomes the obligation of the developers and DBAs
>> to use it.
>
> It would be nice though if reserved words were always reserved though,
> that is the column couldn't have been created in the first place - not
> that that worked fine but the trigger fails.

I agree with nice: In fact I said exactly the same thing a few posts
back. But truly Oracle can not protect people who don't read from
themselves.

Developers and DBAs need to learn about the tools they use just as an
engineer needs to have certain knowledge to design a bridge. The
difference here is that you need to prove your competence before they
will let you design a bridge. All you need to be a developer is to put
the word "developer" on your resume.
--
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