Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Is anyone using random strings as their primary key? Uuids, guids, etc. I
have random 27 character strings that I'm creating. They are very similar
to uuids, but a little more aesthetically pleasing.
I'd like to start using them as my primary keys, so when it comes time to
scale out my database onto multiple machines things will be easier.
The docs, luckily, :) do explain how to to this. So that's good.
But I'd like some reassurance anyway. Last thing I need is to come up
against some obscure bug because I'm the only one using this feature. I
mean obscure but immediate would be okay. But database corruption or
inconsistencys gives me the willies. Is anyone else doing this?
By the way, here is the relevant part of the docs:
Non-Integer Keys <http://www.sqlobject.org/SQLObject.html#id56>
While not strictly a legacy database issue, this fits into the category of
"irregularities". If you use non-integer keys, all primary key management is
up to you. You must create the table yourself (SQLObject can create tables
with int or str IDs), and when you create instances you must pass a
idkeyword argument into constructor (like