Ruby on Rails
Friday, November 14, 2014
as long as you develop - one file per migration
once you 'wrap' it up - a single file is ok
but why change it in the first place?
Den 14/11/2014 kl. 09.27 skrev M,Gopi M.gopinath <gopi170987@gmail.com>:Hi All,I have question with rails migration file.Seems In rails for each and every table migration file will be generate with timestamp followed by table name.But I have moved all the migration file to a single file, and deleted all the migrations.what is the best way of practice,Having single migration for each table or else a single migration file for the whole application.Thanks in advance...Best Regards,Gopinath MRuby on Rails Developer--
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/CAPDEixJMJsZNEjCuCFw%3DRkkq2kGvJnmCGEnucCF3H-XNMBs5uw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment