Re: question about sequences.

In article <uel5mjpy9.fsf_at_hotpop.com>, Galen says...
>
>On Sun, 16 Feb 2003, kennedy-downwithspammersfamily_at_attbi.com wrote:
>
>> It is the type of thing that would happen in real life (some bozo did
>> an insert into dual and now it has 2 rows, and is creating all sorts
>> of havoc.)
>
>I didn't know this could happen so I tried it.
>

snip
>
>How can I get two rows back? (Not that I would do this in actual code,
>but I'd like to know how to make it happen)
>
>I would have answered that question, "Can't happen".
>--
>Galen deForest Boyer
>Sweet dreams and flying machines in pieces on the ground.

Galen

It's something that you used to be able to do in earlier releases (before 8.1.something IIRC). I know, I had this exact problem when we let a manager (yes, I know, I know) do maintenance one night - ended up with 2 rows in DUAL and every form for every application errored out the next morning because they all included a date-time field on them (single row query returns more than one row type error).

In later editions, we put the smarts into the kernel to ensure you CAN'T screw up like this, so it must have happened fairly frequently. :) Now I think you can do inserts, deletes and all sorts of things, get no errors, but still only end up with one row in DUAL, becaue it's no longer really a table (IMSMC it's a synonym on X$DUAL?)

HTH. Additions and corrections welcome.

Pete

SELECT standard_disclaimer, witty_remark FROM company_requirements; Received on Tue Mar 04 2003 - 23:21:26 CST