>----- Original Message ----
>From: Andrew Sullivan <[EMAIL PROTECTED]>
>To: [email protected]
>Sent: Wednesday, May 30, 2007 8:30:32 PM
>Subject: Re: [SQL] slow query execution
>
>On Wed, May 30, 2007 at 11:08:02AM -0700, Trigve Siver wrote:
>
>> I want to do it only for some queries. So when I need query like
>> that "SELECT * from t1" I need to add row_numbers there. So I will
>> have "query with row_numbers" (where row_numbers are row numbers of
>> my virtual list view). Then when I perform search I also get
>> row_numbers for IDs of search result and I can highlight items in
>> my list view. I haven't found other solution that met my
>> requirements.
>
>You really need to ensure you keep that ORDER BY in there, then. The
>order that SQL returns in is not determined until the data has come
>back. Are you doing this all in one serialisable transaction,
>though? If not, what guarantee will you have that new data won't
>mess up your row numbering from query to query?
I seee...when new data will be added to table, then row numbers wouldn''t be
valid anymore.
Hmmm...looked like I need to find other solution.
thanks
Trigve
____________________________________________________________________________________Get
the free Yahoo! toolbar and rest assured with the added security of spyware
protection.
http://new.toolbar.yahoo.com/toolbar/features/norton/index.php
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
