On 4 June 2015 at 21:21, kenatsun <kenat...@gmail.com> wrote: > ... > However: This process has only a limited ability to update the Rails > objects to handle the database change while preserving manually entered > changes to them. Specifically: For each Rails file where the new > (generated) version differs from the existing (possibly manually modified) > version, you get to choose between keeping the old version (so it doesn't > match the database changes) or replacing it with the new version (so any > manual updates to the old version are lost). In other words, I haven't > found a way to generate a new file that is a combination of the old and the > new - that is, it is identical to the old file in all respects except that > it implements the database schema changes. > > So... > > Next question: Are there any Rails tools that can generate a "combined" > file in the sense just defined? Is there any way to generate a "combined" > file in the sense just defined? - either with other Rails tools or with > options to the tools used in the above scenarios?
The reason no work has been done on this is that the scaffold is intended merely as a quick and dirty method of getting some basic functionality up and running. By the time you have a real application going it is most unlikely that much of the original scaffolding code will remain. Colin -- 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+unsubscr...@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/CAL%3D0gLutQQ-%3DCXgu-hKc74axkhcwK5pbRAQ-2KHikP1Z2GrQeQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
