Re: SEQ#, DUAL and Oracle literacy

Don't see any problems :-)

CREATE TABLE SYS.SUPER_DUAL (specific_seq_num NUMBER(10));

DROP PUBLIC SYNONYM DUAL; CREATE PUBLIC SYNONYM DUAL FOR SYS.SUPER_DUAL; INSERT INTO SYS.SUPER_DUAL VALUES(666); Vua-la!!! ;)

-- 
Alexandre



> Want to have a good laugh?... read on... I don't  think its OT :) 

> 

> A few minutes ago, my co-worker DBA was 'ordered' by one of the Oracle

> Duhvelopers from our 'preferred vendor' to fix the DUAL table so that the

> application will get a *specific* Sequence Number for something. 

> 

> DBA: Why do you think DUAL is the problem?  

> Duhveloper:  ...'cause I see the PL/SQL code that says 'from dual'. 

> 

> Boy! Are we in trouble or what??   ;) 

> 

> - Kirti 


-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Alexandre Gorbatchev
  INET: alexandre.gorbatchev_at_avermann.de

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).