Rumpi
True for the SQL, but specifically avoided for the procedural solution (don't put the call into the collection until after it's been checked against prior calls; don't check against itself).
:-)
----- Original Message ----
From: Rumpi Gravenstein <rgravens_at_gmail.com>
One issue that Nigel hasn't addressed is that you will want to account for a call overlapping with itself. That might be done with something along the lines of:
a.ROWID != b.ROWID
On 9/20/07, Nigel Thomas <nigel_cl_thomas_at_yahoo.com> wrote:
Gene
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Sep 20 2007 - 13:13:30 CDT
