ROWID, ROWNUM and views

From: strepxe@xxxxxxxxxxx
Date: Thu, 26 Jun 2008 23:18:50 -0700 (PDT)

Here's some advice for you about the pseudo-columns ROWID, ROWNUM and
their behaviour with views.

* As a general rule avoid using ROWID espcially with complex views
made up of multiple base tables where a DISTINCT clause is used. The
DISTINCT clause will result in the SELECT statement with ROWID not
returning anything.
* As another general rule avoid using ROWNUM. Have found that if the
view has an ORDER BY in the inner query then the SELECT return with
ROWNUM is very very slow ....

.

Follow-Ups:
- Re: ROWID, ROWNUM and views
  - From: Ed Prochak
- Re: ROWID, ROWNUM and views
  - From: Marcin Wróblewski

Prev by Date: Re: DBA_PROCEDURES / DBA_TRIGGERS
Next by Date: Re: Any Oracle 11g for Solaris x86?
Previous by thread: Oracle ODBC scalability with increased user volumes
Next by thread: Re: ROWID, ROWNUM and views
Index(es):
- Date
- Thread

Relevant Pages

Re: ROWID, ROWNUM and views
... made up of multiple base tables where a DISTINCT clause is used. ... DISTINCT clause will result in the SELECT statement with ROWID not ... As another general rule avoid using ROWNUM. ...
(comp.databases.oracle.server)
Re: "Rownum" in Informix
... ROWNUM in Oracle is used to limit resultsets. ... So it's a "relative row number" rather than a rowid. ...
(comp.databases.informix)