Re: A problem in SQL (a real challenge)
From: Joe Celko <71062.1056_at_compuserve.com>
Date: 2000/05/05
Message-ID: <8evc8e$otb$1_at_nnrp1.deja.com>#1/1
Date: 2000/05/05
Message-ID: <8evc8e$otb$1_at_nnrp1.deja.com>#1/1
>> Karl Hewlett suggested a smart solution for this a while ago. This
solution utilizes the unique rowid of each row in a table: <<
ROWID is both not standard, and not relational. You can use a CURSOR and stay within standards, but that also stinks. You will have do this because the table is so screwed up by not having a PRIMARY KEY declared that all bets are off. Beat up the programmer to prevent this from happening again.
--CELKO--
Joe Celko, SQL and Database Consultant
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Fri May 05 2000 - 00:00:00 CEST