version tracking schema.rb - causes timestamp conflicts about plots2 HOT 4 CLOSED

I've seen points for and against keeping schema.rb under source control, but I'd vote for not tracking it.

The schema.rb file will be updated in both production and development environments when migrations are run, which will ensure a "healthy" way to evolve the schema as time passes and models are added or removed. Plus it'll help avoid committing outdated schema files due to not checking the current version and such.

from plots2.

how shall we safely do this? it's OK for me to untrack schema.rb and just check it out, but future coders may run into trouble if they don't take precautions. I'm tempted to version track a copy as schema.rb.example for a little while...

from plots2.

I don't have this problem with any of my two rails projects, but I do have
problems with Gemfile.lock on the other project.

So I'm just popping in my head to say I have no idea.

An example file is good if schema.rb cannot be compiled/built from the
models and migrations.

On Fri, May 2, 2014 at 12:33 PM, Jeffrey Warren [email protected]:

how shall we safely do this? it's OK for me to untrack schema.rb and just
check it out, but future coders may run into trouble if they don't take
precautions. I'm tempted to version track a copy as schema.rb.example for a
little while...

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

from plots2.

schema.rb should be easy to build from migrations. Thats how ive always
started rails apps... With rake db:migrate. But I'm starting to think that
I missed a memo about that and that lots of people skip the migrations and
build directly from the schema and seeds files.
On May 2, 2014 12:39 PM, "Bryan Bonvallet" [email protected] wrote:

I don't have this problem with any of my two rails projects, but I do have
problems with Gemfile.lock on the other project.

So I'm just popping in my head to say I have no idea.

An example file is good if schema.rb cannot be compiled/built from the
models and migrations. If you're using South with migration files for all
models, then there's probably no need to maintain schema.rb.

On Fri, May 2, 2014 at 12:33 PM, Jeffrey Warren [email protected]:

how shall we safely do this? it's OK for me to untrack schema.rb and
just
check it out, but future coders may run into trouble if they don't take
precautions. I'm tempted to version track a copy as schema.rb.example
for a
little while...

—
Reply to this email directly or view it on GitHub<
https://github.com/publiclab/plots2/issues/48#issuecomment-42050995>
.

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

from plots2.