I have recently just done a similar thing for a games site... The email
address and the display name of the user was to be unique... The way I
did it was via a stored procedure... So on registration I call a stored
procedure and pass all the details through, then the proc works out if
it can be
This is probably your best solution. I would _still_ put the constraint on
the table because imho it's better to have a user see an error than to have
no indication when something is wrong. This way, in the event that the
stored procedure isn't working properly -- for any reason -- you'll know
2 matches
Mail list logo
