Databases
StackOverflow2013
Postsdbo
POGenerating a non-sequential ID/PK for a Django Model
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGenerating a non-sequential ID/PK for a Django Model
    primarykey
    data
    text
    <p>I'm on the cusp of starting work on a new webapp. Part of this will give users pages that they can customise in a one to many relationship. These pages naturally need to have unique URLs.</p> <p>Left to its own devices, Django would normally assign a standard <code>AUTOINCREMENT</code> ID to a model. While this works fantastically, it doesn't look great and it also makes pages very predictable (something that isn't desired in this case).</p> <p>Rather than 1, 2, 3, 4 I would like set-length, randomly generated alphanumeric strings (eg h2esj4). 6 spots of a possible set of 36 characters should give me over two billion combinations which should be more than enough at this stage. Of course if I could expand this at a later time, that would be good too.</p> <p>But there are two issues:</p> <ol> <li><p>Random strings occasionally spell out bad words or other offensive phrases. Is there a decent way to sidestep that? To be fair I could probably settle for a numeric string but it does have a hefty hit on the likelihood of clashes.</p></li> <li><p>How do I get Django (or the database) to do the heavy lifting on insert? I'd rather not insert and <em>then</em> work out the key (as that wouldn't be much of a key). I assume there are concurrency issues to be aware of too though if two new pages were generated at the same time and the second (against all odds) magically got the same key as the first before the first was committed.</p></li> </ol> <p>I don't see this being a million miles different from how URL shorteners generate their IDs. If there's a decent Django implementation of one, I could piggyback off that.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USOli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGenerating a non-sequential ID/PK for a Django Model
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGenerating a non-sequential ID/PK for a Django Model
      1. USOli
      1. VTBountyStart
    3. VO
      singulars
      1. POGenerating a non-sequential ID/PK for a Django Model
      1. USDominik Szopa
      1. VTFavorite
    1. COAs a note: the 'URL shorteners' usually generate sequential URLs :).
      singulars
      1. POGenerating a non-sequential ID/PK for a Django Model
      1. USMichał Górny
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload