-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
changing over to db:setup which closes #191
- Loading branch information
Showing
1 changed file
with
7 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bc4bb1d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, @btbonval - was there a reason you kept
rake db:migrate
as a fallback? Now that I'm trying to deprecate spatial_adapter and get sqlite-compatible (for new developers), I'm more interested in just never running migrate, because there are ENGINE directives and spatial things I'd like to never have to deal with, but don't want to rewrite the schema/migration history. For example, I'd prefer to add a new migration than to change early migrations in #429 and #433.I did see an error with
rake:db setup
recently, but migrate didn't solve the issue.