Re: Tricky SQL Problem: Top "n" of queried records

In article <6f8qki$9fu$1_at_nnrp1.dejanews.com>,   bmuller_at_kenan.com wrote:
>
> In article <6f0rfo$5v3$1_at_pebble.ml.org>,
> joelga_at_pebble.ml.org (Joel Garry) wrote:
> >
> > In article <3512F42A.B4591493_at_kenan.com>,
> > Brenda Muller <bmuller_at_kenan.com> wrote:
> > >In Sybase (and Sybase alone), you can "set rowcount 3" at the
> > >beginning of your transaction, which will restrict the server to
> > >returning only 3 rows.
> > >There is nothing analogous to this in Oracle.
> >
> > In sybase, you can wait forever because one of those rows is on the same
> > page as a completely unrelated row that someone has locked up. There
> > is nothing analogous to this in Oracle.
 [ad hominem snipped]
>
> ...it's not possible that you would wait "forever" to access a
> row in Sybase which is on page that is exclusively locked by another
> process...I'll not expound on that...
[ad hominem snipped]

Strike "forever", insert "an indeterminate period, until the other user releases the lock on the page."

Now we're all happy. No?

--
Sherilyn

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/   Now offering spam-free web-based newsreading