Here's a kludged-together work-around.  After you do your rare pool
requests, drop the sequence and recreate it starting at MAX(ID)+1.  There
is no easier way to reset the sequence number.



                                                                                       
    
                    Marin                                                              
    
                    Dimitrov             To:     Multiple recipients of list ORACLE-L  
    
                    <marin.dimitr        <[EMAIL PROTECTED]>                        
    
                    ov                   cc:                                           
    
                    @sirma.bg>           Subject:     Re: sequence pool                
    
                    Sent by: root                                                      
    
                                                                                       
    
                                                                                       
    
                    10/24/2001                                                         
    
                    12:40 PM                                                           
    
                    Please                                                             
    
                    respond to                                                         
    
                    ORACLE-L                                                           
    
                                                                                       
    
                                                                                       
    




----- Original Message -----
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 24, 2001 18:33


> Why not have the sequence increment by 20 (or something to your liking)
and
> then in the application use the number from the sequence and the 19
numbers
> the sequence will skip.
>

because the pool request will be rather rare, the rest of the time the IDs
will be generated one by one

what I thought of is having two sequences and split the range of possible
IDs between them (i.e. the first half is handled by one-by-one sequence and
the second half is handled by the pool sequence) but this seems quite lame
(the relative order of IDs of the rows will be ruined)


    Marin


----
"...what you brought from your past, is of no use in your present. When
you must choose a new path, do not bring old experiences with you.
Those who strike out afresh, but who attempt to retain a little of the
old life, end up torn apart by their own memories. "


--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Marin Dimitrov
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).


-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to