Colin Law wrote: > > I do not know enough about the application to say much more. I was > suggesting updating the actual data rather than a temp table, but it > was only a suggestion. I generally would suggest to do things the > easiest way initially and only complicate it it if becomes necessary, > though which is the easy way in your case I do not know. Certainly > don't worry about the db traffic unless it becomes an issue. > > Whichever route you go down make sure you have tests in place so you > can refactor later and know it still works. > > Colin
Alright, thanks a lot to all of you! I'll keep both solutions in mind and see what's easier to use. -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
