You don't build the db with db:migrate about selfstarter HOT 4 OPEN

While it's true that rake db:schema:load is the proper method to build a db, the migrations would still be required if any rake db:rollback operations are to be performed. Rollbacks affect the schema and the db it corresonds to.

from selfstarter.

I'm assuming you're referring to my comment about deleting migrations...

I was referring to deleting migrations that are old, not recent. And
moreover I was saying that to make the point that they should be not
considered definitive.

I'll also add that migrations that work fine today will sometimes even fail
months in the future, especially if things get renamed. Further proof that
migrations should not be used to build up a db.

Anyway, are you agreeing that the instructions should be changed, or do you
feel it should stay as is?

Khurram Virani

On Sat, Nov 23, 2013 at 9:04 PM, Mohammed Ameen [email protected]:

While it's true that rake db:schema:load is the proper method to build a
db, the migrations would still be required if any rake db:rollbackoperations are to be performed. Rollbacks affect the schema and the db it
corresonds to.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/69#issuecomment-29149083
.

from selfstarter.

rake db:schema:load or rake db:setup which essentially is a shortcut for rake db:create && rake db:schema:load && rake db:seed is usually how we create db's on new projects/machines.

I'd agree with changing the instructions as recreating a db overtime solely through migrations would not be feasible (essentially if later migrations affect older ones or any irreversible migrations are performed)

Also if you strongly feel that the instructions are to be changed edit the readme and send in a pull request with the updated instructions for recreating the db.

from selfstarter.

Great, will do. Thanks

Khurram Virani

On Sat, Nov 23, 2013 at 10:10 PM, Mohammed Ameen
[email protected]:

rake db:schema:load or rake db:setup which essentially is a shortcut for rake
db:create && rake db:schema:load && rake db:seed is usually how we create
db's on new projects/machines.

I'd agree with changing the instructions as recreating a db overtime
solely through migrations would not be feasible (essentially if later
migrations affect older ones or any irreversible migrations are performed)

Also if you strongly feel that the instructions are to be changed edit the
readme and send in a pull request with the updated instructions for
recreating the db.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/69#issuecomment-29149719
.

from selfstarter.