# Schema.rb SVN or not?

**URL:** <https://www.ruby-forum.com/t/schema-rb-svn-or-not/135887>\
**Category:** Rails\
**Created:** [April 25, 2008, 9:57pm UTC](https://www.ruby-forum.com/t/schema-rb-svn-or-not/135887 "2008-04-25T21:57:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisdwan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/7feea3/32.png) [@chrisdwan](https://www.ruby-forum.com/u/chrisdwan)\
**Post date:** [April 25, 2008, 9:57pm UTC](https://www.ruby-forum.com/t/schema-rb-svn-or-not/135887/1 "2008-04-25T21:57:37Z")

</div>

Fairly simple one today:

Does Schema.rb belong in your SVN repository which all the developers  
commit to? If Schema.rb is autogenerated which it claims to be, then  
will running the Migrations on every (new) machine bring the Schema.rb  
in the correct state?

Getting some conflicts now in Schema.rb when 2 devs create migrations  
and commit / update with the SVN

---

<div class="post-metadata">

**Author:** ![chrisdwan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/7feea3/32.png) [@chrisdwan](https://www.ruby-forum.com/u/chrisdwan)\
**Post date:** [April 25, 2008, 11:33pm UTC](https://www.ruby-forum.com/t/schema-rb-svn-or-not/135887/2 "2008-04-25T23:33:17Z")

</div>

I include it in the repo for two reasons: (1) the comment at the top of  
schema.rb urges me to include it in the repo; (2) I’ve never had a  
conflict  
on it, and I work on projects stored in both Subversion and Git repos.

Regards,  
Craig

---

<div class="post-metadata">

**Author:** ![chrisdwan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/7feea3/32.png) [@chrisdwan](https://www.ruby-forum.com/u/chrisdwan)\
**Post date:** [April 26, 2008, 10:58am UTC](https://www.ruby-forum.com/t/schema-rb-svn-or-not/135887/3 "2008-04-26T10:58:05Z")

</div>

On Sat, Apr 26, 2008 at 5:57 AM, Chris D.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Does Schema.rb belong in your SVN repository which all the developers  
> commit to? If Schema.rb is autogenerated which it claims to be, then  
> will running the Migrations on every (new) machine bring the Schema.rb  
> in the correct state?
> 
> Getting some conflicts now in Schema.rb when 2 devs create migrations  
> and commit / update with the SVN

That would be the #1 reason why you WOULD put your schema.rb into the  
repo as if you are getting conflicts on this file that aren’t  
automerging, then you know that your developers are crossing paths on  
the database and that might be something you want to catch early…

My 2c worth.

Mikel  
[http://www.lindsaar.net/ruby-on-rails-tips](http://www.lindsaar.net/ruby-on-rails-tips)