Friday, November 14, 2014
Hi Colin,
On Thursday, November 13, 2014 4:29:31 PM UTC-5, Colin Law wrote:
-- Thanks for your response. I totally agree with you. Do you or anyone else have experience with these kind of data content migrations going bad? Basically, the only argument I can provide the team is that it "smells" bad, the intent of migrations seem to be for data structure, not content (other than reference data or an initial admin user), and all migration documentation/examples only show DDL type statements.
Thanks.
On Thursday, November 13, 2014 4:29:31 PM UTC-5, Colin Law wrote:
On 13 November 2014 18:44, <bob.n...@gmail.com> wrote:
> @rails Hi,
>
> I'm new to rails, and my dev team wants to load all user content data (not
> reference data or admin users) via migrations. Is this going to be
> problematic?
>
> If so, how can I convince them that is a likely mistake? What would be the
> alternatives?
Use rake db:seed, which runs db/seeds.rb. That is what it is for.
Colin
>
> Thanks,
>
> Bob
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-ta...@googlegroups.com .
> To post to this group, send email to rubyonra...@googlegroups.com .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-talk/ .5a065c67-52ca-4852-9c72- c77023f6009c%40googlegroups. com
> For more options, visit https://groups.google.com/d/optout .
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/b4a4af78-bf79-40f2-87e6-0e400fa74fff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment