Re: Trigger error (implicit vs explicit cursors)

From: mcstock <mcstockx_at_xenquery.com>
Date: Mon, 3 Nov 2003 06:51:52 -0500
Message-ID: <DuOdncpF7oge3DuiRVn-jg@comcast.com>

rownum is the pre-sort order of the rows -- rownum = 1 is not always the first row returned:

SQL> select dname, deptno
2 from dept
3 order by dname desc;
...

DNAME DEPTNO
-------------- ----------

SALES                  30
RESEARCH               20
OPERATIONS             44
ACCOUNTING             10

SQL> select dname, deptno
  2 from dept
  3 where rownum =1
  4 order by dname desc;
...

DNAME DEPTNO
-------------- ----------
ACCOUNTING 10 however, isn't there another technique or function added in 8i for stuff like first_rows() for top_rows?

"Connor McDonald" <connor_mcdonald_at_yahoo.com> wrote in message news:3FA6342C.7E0D_at_yahoo.com...
>
> The too_many_rows is a dead issue.
>
> If you have a cursor that may return more than 1 row and you code
> open/fetch/close, then you are basically seeing that you are interested
> in just the first. In which case, the implicit cursor can be
>
> select .. into ...
> where rownum = 1
>
> and you'll never ever get the too_many_rows.
Received on Mon Nov 03 2003 - 05:51:52 CST