Skip to content

Better data integrity #206

Closed
croaky opened this Issue Jul 20, 2012 · 2 comments

2 participants

@croaky
thoughtbot, inc. member
croaky commented Jul 20, 2012

I propose the default migration should make email, encrypted_password, and remember_token :null => false.

@jferris
thoughtbot, inc. member
@croaky
thoughtbot, inc. member
croaky commented Jul 21, 2012

Thinking we can't really have null: false in the "upgrade existing users table" migration: can't add null remember_token, email, and encrypted_password columns to existing user rows.

Will only apply this to the "new users table" migration.

@croaky croaky added a commit that referenced this issue Jul 22, 2012
@croaky croaky [#206] Improve data integrity
By default, we want email, encrypted_password, and remember_token to
enforce a NOT NULL constraint.
fd6fbc0
@croaky croaky closed this Jul 22, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.