Re: How to disable '@' in SQL*Plus?

Anthony wrote:

> Thanks Daniel for the reply.
>
> Do you mean that it is impossible to disable this behaviour?
>
> Daniel Morgan <damorgan_at_x.washington.edu> wrote in message news:<1075354681.632738_at_yasure>...
>
>

>>SELECT keyword
>>FROM v$reserved_words
>>WHERE LENGTH(keyword) = 1;
>>
>>Don't try to kludge your way around a bad design ... fix your design.

Impossible. You can kludge your way around it on a case by case basis and probably get anything to work ... at least until Oracle releases a patch that breaks the kludge. But the question I am asking is why, given all of the characters on the keyboard, anyone would intentionally design anything using a restricted keyword? Just change to something else and the entire problem disappears.

And consider the implications of using any tools that can't use the kludge's available to a programmer. I would think every production DBA looking at your code would get a sick feeling in the pit of their stomach that can best be expressed by saying: "He's going to write this garbage and go on to something else and I'm the one that's going to have to maintain it for the next five years. Well there go my evenings and weekends."

I'm encouraging you to never use keywords for anything other than their intended usage.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)