Re: using UID in DB

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 30, 2010 at 7:37 PM, Paul M Foster <paulf@xxxxxxxxxxxxxxxxx> wrote:
>
> Unless you have some compelling need to store a number like this, I
> don't see the need to. What I store is what is called in PostgreSQL a
> "serial" value. MySQL calls it "auto_increment". You store all the other
> values as a row, and the DBMS adds in the "auto_increment"/"serial"
> value for you. It's an integer, *usually* one larger than the last value
> entered.
>
> Paul
>

The (personal) project I'm about to start will run in several threads
(thinking how can I make this happen in PHP) where the inserts could
be multiple inserts at once.  Identity (type) insert doesn't behave
nicely (locking up the DB) when there are multiple inserts at once.
Using UUID is one of the possible solution to resolving this problem
for me.

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux