Re: Avoiding generating redo logs

From: DA Morgan <damorgan_at_psoug.org>
Date: Sat, 16 Sep 2006 12:11:37 -0700
Message-ID: <1158433895.999031@bubbleator.drizzle.com>

Frank van Bortel wrote:
> DA Morgan schreef:
>

>> My recommendation would be that you use global temporary tables to cache
>> the data as in the following:
>>
>> CREATE GLOBAL TEMPORARY TABLE test (
>> zip_code     VARCHAR2(5),
>> by_user      VARCHAR2(30),
>> entry_date   DATE)
>> ON COMMIT PRESERVE ROWS;

>
> GTT in combination with mod_plsql is not working.
> Also see:
> http://asktom.oracle.com/pls/ask/f?p=4950:8:18361359189545016282::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:446620083639
>
> http://vanbortel.blogspot.com/2006/07/authentication-in-modplsql.html
>

>>
>> This is likely the most efficient structure for your purposes.
>>
>> But I am left wondering why you think it desirable to let an end user
>> sort and filter anything. Wouldn't it be far easier to just teach them
>> how to use the WHERE and ORDER BY clauses correctly?

>
> It is not uncommon in a web application to have those nice little
> triangles on top of a column, indicating sort order, and the
> possibility to change the sort order

Didn't see that requirement before.

My feeling, as already stated, is that OP is wasting time as filter and sorting should be done by the SELECT statement.

-- 
Daniel Morgan
University of Washington
Puget Sound Oracle Users Group

Received on Sat Sep 16 2006 - 14:11:37 CDT