-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.0.0 can register more than once with a single email address #5
Comments
This is really a question about the portal. Leaving it open here for now until we're ready to test Mitya's new portal. |
Yeah it would make testing the portal very hard indeed if you couldn't I thought casjobs did in fact enforce unique emails but clearly it must not Ani Aniruddha R. Thakar, Principal Research Scientist http://www.sdss.jhu.edu/%7EthakarWe are all atheists about most of the gods that societies have ever On Tue, Jun 30, 2015 at 12:38 PM, raddick notifications@github.com wrote:
|
The current production CasJobs does indeed enforce unique emails. I just tried creating a new account with my current email, and got an error saying "Cannot create account; this email already exists." Forget about testing - what about our end users? Do we want to allow multiple registrations on the same email address? I don't think that allowing multiple registrations on an email hurts the user, but it does mean that we can't use email as the primary key in the users table. Thoughts? |
We don't use email as PK anyway AFAIK, probably webservicesid or userid. Ani Aniruddha R. Thakar, Principal Research Scientist http://www.sdss.jhu.edu/%7EthakarWhoever heard of a hundred thousand animals rushing together to On Wed, Jul 1, 2015 at 9:13 AM, raddick notifications@github.com wrote:
|
I haven't seen a case using email address as PK. Agreed with Ani on enforcing email uniqueness . |
OK, sounds like we've decided that we do want to enforce email uniqueness. Should we close this issue, then? |
Oh, but the issue said that the user can register with more than one email address. That's not the behavior we want. So this is no longer a question, but a bug. Changing labels accordingly. |
I think that this issue should be moved to single sign-on login portal. @mikear69 |
Should this be allowed?
The text was updated successfully, but these errors were encountered: