Process to create development setup data
Reported by theirishpenguin | December 14th, 2008 @ 10:07 PM | in 0.1
Add a migration that contains development setup data. This saves laborious seeding of the development database by each developer. Will probably remove this migration and come up with a better solution (rake task?) once near the end of the first development phase.
Comments and changes to this ticket
-
theirishpenguin December 14th, 2008 @ 11:20 PM
I have added some seed data in a migration. I have put it up at http://github.com/theirishpengui...
I need to work out how to get this onto the master tree.
-
Gavin Joyce December 14th, 2008 @ 11:58 PM
Thanks for doing this.
I agree with your comment, a rake task would be a cleaner solution. Perhaps we should aim for this?
-
-
theirishpenguin December 16th, 2008 @ 09:18 PM
Rake task done as rake db:seed (also added a db:clean task). Should probably change this functionality to use a Factory, just like the specs?
-
Gavin Joyce December 17th, 2008 @ 06:11 PM
I think that we should be OK using the Models directly for this. The factory used in the specs will change soon anyway, it has issues with complex model relationships.
-
Gavin Joyce December 17th, 2008 @ 07:15 PM
- State changed from “new” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A simple job listing app from Ruby Ireland
Gavin Joyce