The tradeoff will be between a user not being able to play around with the querystring (i.e change id=1 to id=2) and performance. How much performance I can't say. A million a day I would think you would start to see it. I personally haven't hit the performance issue with uuid but I also haven't created nearly 1 million a day.
-- Ryan LeTulle On Thu, Jun 11, 2009 at 7:03 AM, Fawzi Amadu <[email protected]> wrote: > > I am wondering the best way to create an ID for an online advertising site > that I anticipate could have about a million products uploaded a day. > > I had considered using create UUID I read the following from Christian > Cantrell > > "If you want the convenience of generating your own primary key without the > performance degradation of selecting from a table with a 35 character > primary key, you can let your database create a normal auto-incrementing ID > field as you normally would to use as your primary key, and insert a UUID at > the same time. Then, just select the ID of the row that has the UUID that > you just generated, and you are guaranteed (statistically) to have selected > the right ID without having to use vendor specific SQL" > > Now I am wondering if I should add the auto-incrementing ID or just use and > auto- generated number concatenated with the a string representing the day, > month and year of the transaction. > > I'll appreciate any insight on this. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:323388 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
