the real question is - if you want the email to be unique, why use
"surrogate" primary key as UUID.
I wonder what UUID gives you at all?
If you want to have non email primary key, why not use md5(email) ?
On Wed, May 7, 2014 at 2:19 AM, Tyler Hobbs wrote:
>
> On Mon, May 5, 2014 at 10:27 AM
If you are worried about the over head of malicious bulk registration, you
could develop some rate limiting to restrict the sign ups to X signups per
hour from the same IP. Also you could use a CAPTCHA system to make lots of
requests hard to create.
The other thing that works well is automating th
On Mon, May 5, 2014 at 10:27 AM, Ignacio Martin wrote:
>
> When a user registers, the server generates a UUID and performs an INSERT
> ... IF NOT EXISTS into the email_to_UUID table. Immediately after, perform
> a SELECT from the same table and see if the read UUID is the same that the
> one we j
Hi,
I know this is a pretty common topic, but I haven't found any solution that
really satisfy me. The problem is well known: you have a table with user
information with a UUID as primary key, but you want to avoid email
duplicates when new users register.
The closest solution I've found is this:
