# Seeding data for Rails migrations - suggestions

**URL:** <https://www.ruby-forum.com/t/seeding-data-for-rails-migrations-suggestions/134455>\
**Category:** Rails\
**Created:** [April 11, 2008, 12:45am UTC](https://www.ruby-forum.com/t/seeding-data-for-rails-migrations-suggestions/134455 "2008-04-11T00:45:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![JamesKay](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/b3f665/32.png) [@JamesKay](https://www.ruby-forum.com/u/JamesKay)\
**Post date:** [April 11, 2008, 12:45am UTC](https://www.ruby-forum.com/t/seeding-data-for-rails-migrations-suggestions/134455/1 "2008-04-11T00:45:15Z")

</div>

In case it is of use generally, see

> **[Seeding data as part of Rails database migrations](https://workbooks.wordpress.com/2008/04/10/seeding-data-as-part-of-database-migrations/)**
>
> So, we stumbled across a slight problem when trying to seed data as part of our database migration scripts. The de-facto standard seems to be to keep the seed data in yaml files and load them in us…