From: sharmp@hhcs.gov.au
Newsgroups: comp.databases.oracle
Subject: RE: RE: PL/SQL, V$ problem
Date: 4 Sep 92 08:26:02 +1000
Organization: Aust. Dept. Health, Housing and Community Services

Kathy asked me to post this.  Thanks for the info Kathy.  We've just got
6.0.36 which I think includes PL/SQL 1.0.34!

From:	UUCP%"kjou@us.oracle.com"  3-SEP-1992 08:43:55.15
To:	hhcs.gov.au!sharmp
CC:	
Subj:	Re: Re: PL/SQL, V$ problem

From us.oracle.com!kjou  Wed Sep  2 08:04:59 1992 remote from sserve
Received: from sserve by hhcs.gov.au (DECUS UUCP ///1.3-1/2.5/);
          Thu,  3 Sep 92 08:43:53 +1000
Received: from gatekeeper.oracle.com by sserve.cc.adfa.oz.au (5.65c/1.34)
          id AA03282; Thu, 3 Sep 1992 08:17:06 +1000
Received: from hqpyr1.us.oracle.com by gatekeeper.oracle.com (Oracle 1.12/37.7)
          id AA27569; Wed, 2 Sep 92 15:16:58 PDT
Received: by hqpyr1.us.oracle.com (Oracle 1.12/37.7)
          id AA20471; Wed, 2 Sep 92 15:04:59 PDT
Message-Id: <9209022204.AA20471@hqpyr1.us.oracle.com>
Date: Wed, 2 Sep 92 15:04:59 PDT
From: "Kathy Jou" <sserve!us.oracle.com!kjou>
To: hhcs.gov.au!sharmp
Subject: Re: Re: PL/SQL, V$ problem
Original-To: hqpyr1:sharmp@hhcs.gov.au


I tried to post a correction, but our news reader died.  Here's a follow-up.
It's a bug, not a restriction, in your case.  Feel free to post this if your
news reader is more robust than ours.

Cheers,

	_Kathy_

-------------------------------------------------------------------------------
Kathy Jou					(415) 506-2523 -*- 400 OP, #519
Application Porting, DG/88open Systems		 Minicomputer Products Division
-------------------------------------------------------------------------------

Newsgroups: comp.databases.oracle
Subject: Re: PL/SQL, V$ problem
Summary: 
Expires: 
Followup-To: 
Distribution: 
Organization: Oracle Corporation, Redwood Shores CA 94065
Keywords: bug

Oops, this is a case where a reserved word is not used in the wrong context as
documented (as an identifier, for example).  PL/SQL v1.0.34 and higher fixes 
this problem.  Sorry about that!


-- Kathy Jou
-- Disclaimer: Oracle's glad that I don't speak on their behalf...

In article <1992Sep2.170535.25347@oracle.us.oracle.com> kjou@us.oracle.com (Kathy Jou) writes:
>In article <1992Sep1.155256.336@hhcs.gov.au> sharmp@hhcs.gov.au writes:
>[stuff deleted...]
>>	INSERT INTO dbu.drs_snapshot_v$lock
>>	     SELECT d.db_started,
>>		    d.db_closed,
>>		    v.addr,
>>		    v.pid,
>>		    v.type,
>>		    v.id1,
>>		    v.id2,
>>		    v.lmode,
>>		    v.request
>>	       FROM v$lock v, dbu.drs_driver d
>>fails because TYPE is a PL/SQL reserved word.  Sure, we could create the insert
>>statement as select * from, or rename the column, but is there a way to get
>>PL/SQL to accept a reserved word as a column name (how come ORACLE uses
>>reserved words anyway?! :^)).
>
>Upper case the reserved words and put double quotes around them, i.e. use
>v."TYPE".  This is a rough workaround since the restriction is clearly 
>documented.  All *programming* languages have reserved words (can't declare a
>variable called if in C).  I guess we just have to live with it.
>
>
>-- Kathy Jou
>-- Oracle Corporation
>-- Disclaimer: not an official Oracle spokesperson...
>