Hmm, well right now users are complaining it's too easy to view other people's boards because the url is https://www.taskfort.com/view/10
The only way to not view a person's board is if it's private.. There are some services that for their pages will have id's that are 7 or so characters long, and very compact, the uuid you're referencing seems kind of ugly.
I would still keep my incremental ID in the table as a PK, but maybe I could generate a new value per row for a public URL ID. That public url id could be based off of their PK but I don't know what would be the best way to generate a short url id w/ the PK as a key.
Comments
Hmm, well right now users are complaining it's too easy to view other people's boards because the url is https://www.taskfort.com/view/10
The only way to not view a person's board is if it's private.. There are some services that for their pages will have id's that are 7 or so characters long, and very compact, the uuid you're referencing seems kind of ugly.
I would still keep my incremental ID in the table as a PK, but maybe I could generate a new value per row for a public URL ID. That public url id could be based off of their PK but I don't know what would be the best way to generate a short url id w/ the PK as a key.
This looks like a good implementation:
http://kvz.io/blog/2009/06/10/create-short-ids-with-php-like...