You are correct. I must do some editing to incoming data before it's "imported" into the "projects" table.
I'm having more problems importing data from one table to another. When editing is complete, I click a button to "save" to projects table. My button is very up front and easy. <%= button_to "Add Records to Projects", :action => "addIrbProjects", :id => import.id %> It's just setting up the projects Controller that has me confused. I'm in the projects controller reading a "imports" table. John Ar Chron wrote: > Marnen Laibow-Koser wrote: >> >> You could -- it's just poor design in most cases. >> > > Most cases yes, but in some cases a parallel import table is not a bad > thing. > > If you put all your data into one table, then all the records going into > that table have to pass all the model constraints immediately. > > From John's initial post, I read "after doing some preliminary editing" > to imply that the records, as imported from CSV, may not satisfy all the > constraints of the application. > > It may be in his interest to keep these "dirty" records separate from > the "clean" records so he does not have to relax any constraints on the > mainstream application data, or complicate his existing model > constraints by mixing a flag check into the middle of things. > > Ultimately, it'll be whatever works best for John. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
