RE: [Phpwebsite-developers] Sequence Tables

[Darrel <da...@ii...>]

You may want to take a look at this paper by Scott Ambler[1].  It
compares the various approaches to getting an object identifier and then
suggests an alternative called the high/low approach that might work
well in your situation.  The big differences are that he uses a single
sequence for all objects and he allocates a set of id's to a session so
that a database access is not required on each object allocation, only
when the set of assigned ID's is used up.

Darrel

[1] http://www.ambysoft.com/mappingObjects.pdf


> -----Original Message-----
> From: php...@li... 
> [mailto:php...@li...] On 
> Behalf Of Don Seiler
> Sent: October 22, 2002 10:43 AM
> To: Steven Levin
> Cc: php...@li...
> Subject: Re: [Phpwebsite-developers] Sequence Tables
> 
> 
> So we're going with the pear sequences and the additional 
> *_seq tables?
> 
> I'll go +1 on that.
> 
> I'm just paranoid of dead-locks and bottlenecks by having one 
> table store 
> all sequences.
> 
> Don.
> 
> On Tue, 22 Oct 2002, Steven Levin wrote:
> 
> > Hello All,
> > 
> > In response to the very long thread we have had concerning 
> the PEAR DB 
> > and auto_increment,  the development team just held a meeting to 
> > discuss our options.  The decision was made to stick with the PEAR 
> > standards.
> > 
> > So here is my +1
> > 
> > Please vote :)
> > 
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future 
> of Java(TM) technology. Join the Java Community 
> Process(SM) (JCP(SM)) program now. 
> http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun
.com/javavote
_______________________________________________
Phpwebsite-developers mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers