5 ms·
Previously: http://news.ycombinator.com/item?id=670218 http://news.ycombinator.com/item?id=670218, http://news.ycombinator.com/item?id=1818166 http://news.ycomb
by jjwiseman 16y ago
Previously: http://news.ycombinator.com/item?id=670218 http://news.ycombinator.com/item?id=670218, http://news.ycombinator.com/item?id=1818166 http://news.ycombinator.com/item?id=1818166, joshu: http://joshua.schachter.org/2007/01/autoincrement.html http://joshua.schachter.org/2007/01/autoincrement.html (http://news.ycombinator.com/item?id=52429 http://news.ycombinator.com/item?id=52429 )
Foursquare growth in 2009 inferred from autoincrement IDs: http://www.flickr.com/photos/wallofhair/4232092914/ http://www.flickr.com/photos/wallofhair/4232092914/
- joshu 16y agoI have a bunch of similar data on craigslist I should write up someday.
- gokhan 16y agoOne from 2006: http://www.guardian.co.uk/world/2006/jul/20/secondworldwar.tvandradio http://www.guardian.co.uk/world/2006/jul/20/secondworldwar.t... "The statisticians believed that the Germans, being Germans, had logically numbered their tanks in the order in which they were produced."
- gojomo 16y agoFor some services, your growth may not be proprietary info — you may want to show incrementing IDs off, or make all your artifacts trivially discoverable. But, if you have an internal autoincrement ID that you want to obfuscate, what's the best simple practice, minimizing token expansion?
- smanek 16y agoJust use UUIDs and be done with it. I'll give you a $1 if you ever see a collision ;-)
- gojomo 16y agoThat's a reasonable baseline suggestion, but I'd prefer any technique to generate more compact public IDs.
- buddydvd 16y agohttp://www.quora.com/How-do-you-symmetrically-encrypt-32-bit-auto-increment-IDs-to-avoid-using-64-bit-UUIDs-to-conceal-the-size-and-order-of-a-database-table/answers/23925 http://www.quora.com/How-do-you-symmetrically-encrypt-32-bit...