Re: Avoiding generating redo logs

In article <9sqng2lqh30vumre927tafg5bs2fkfh0p2_at_4ax.com>, Sybrand Bakker says...
> On 16 Sep 2006 05:09:21 -0700, "Martin T."
> <bilbothebagginsbab5_at_freenet.de> wrote:
>
> >Jeremy wrote:
> >> Environment as in sig.
> >>
> >> (...) (as ours is a web app over http a new session is
> >> started for every new screen displayed).
> >>
> >Really. Really. Really bad idea. All kind of complications will arrise.
> >Is it really not possible with your environment to have a HTTP user
> >session and an associated DB session?
> >
> >I'd recommend you take a few hours and try to find out how you could
> >change the design so that you have a session per user session.
> >
> >cheers,
> >Martin
>
> Good recommendation.

You think so?

> The OP sounds like someone who just starts
> 'somewhere' and continues to hack code until it 'works'.

Based on what - I merely asked a question about whether it was possible/desirable to suppress generation of redo under certain circumstances.

> After some time disaster is apparent, but then he has already left the
> company, or the application has been outsourced, and people like
> myself can clean out the mess.
>

What a lot of old rubbish.

-- 

jeremy