[cvsnt] Re: Repository auditing with Oracle

[Paulo Soares]

> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org 
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Anthony Williams
> Sent: Wednesday, January 11, 2006 3:06 PM
> To: cvsnt at cvsnt.org
> Subject: Re: [cvsnt] Re: Repository auditing with Oracle
> 
> "Paulo Soares" <psoares at consiste.pt> writes:
> 
> >> > SELECT ID_SEQUENCE.CURRVAL FROM DUAL
> >> 
> >> and now, it occurs to me that you might also be able to use 
> >> this last SELECT
> >> in conjuction with a trigger that did the actual update.
> >
> > As long as you are the only writer using the sequence. 
> 
> As I understand it, CURRVAL returns the last generated 
> sequence value for this
> connection; consequently you cannot use it until you have 
> used NEXTVAL within
> this session.
>

I know. Just playing safe.
 
> > If you are you
> > may as well generate the number internally in the cvsnt 
> server. A better
> > way is to call
> >
> > SELECT ID_SEQUENCE.NEXTVAL FROM DUAL
> >
> > and use the returned value for all the insertions. It would 
> also work
> > with multiple writers.
> 
> This was one of my suggestions above.

Yes, it was and it gets my vote.

Paulo