From: Adam M. <ad...@tu...> - 2002-10-22 14:49:26
|
OK after meeting with everyone here I've decided to change my vote to sticking with the PEAR standard. This will require more tables but will also reduce the "bottleneck" effect. So...+1 on PEAR standard Adam > I'm with the single table idea for all sequence numbers. > > This way we can have one select on init that loads all sequence numbers > into a session array. Then on inserts we only have to update the > core_sequencer table instead of select AND update it (thinking of > reducing database accesses). > > Also, with all the sequence numbers in the core table, we can get rid of > the current _seq tables getting our table total back down to around 23 > :) (organizational +). > > Another plus? A quick re-write of the sqlmaxid function can simply > return the id in the sessioned sequence array (less database > action=good...there may be more functions that can take advantage). > > We can continue to rely on the pear package, we just need to try and get > the best of all worlds. > > Adam > > --------------------------------- > Adam Morton > Developer - Web Technology Group > Appalachian State University > http://phpwebsite.appstate.edu > > > > > ------------------------------------------------------- > 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;7576298;k?http://www.sun.com/javavote > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers --------------------------------- Adam Morton Developer - Web Technology Group Appalachian State University http://phpwebsite.appstate.edu |