An error occurred fetching the project authors.
- 22 Nov, 2018 1 commit
-
-
Jan Provaznik authored
DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
-
- 24 Feb, 2017 2 commits
-
-
Timothy Andrew authored
The default (false) is not strictly required, and this lets us avoid a potentially expensive migration
-
Timothy Andrew authored
Rather than using a separate `ghost` state. This lets us have the benefits of both ghost and blocked users (ghost: true, state: blocked) without having to rewrite a number of queries to include cases for `state: ghost`.
-