On Sat, 16 Sep 2006, jeremy0505@gmail.com wrote:
> Environment as in sig.
>
> I am a little puzzled about the logging_clause when creating a
> table. We are designing a web application which will have use , at
> times, a table to hold a "cache" for a user. For example, a query is
> executed which takes a few seconds. We store the results in the
> "cache" and then the user can sort and filter on that "cache". This
> cache I envisage as a table structure with its PK being the user_id of
> the user logged in. The data in this table is of no lasting value as
> it is just a redult of a query.
>
> I wanted to design this, if possible, so that there is no redo
> generated for DML performed on this table.

Why do you need to worry about redo?

--
Galen Boyer