one option: - build rake task to import data - and use schedular or background job to run it regularly
On Feb 24, 2012 8:18 AM, "Frank Guerino" <[email protected]> wrote:a > > Hi, > > I have a question about how best to handle "ongoing" and "incremental" > seeding of a database, after the application is built. > > Summary of Application: I need to build a multiple choice testing > application where, in short, each Question has four Answer Choices. A > "User Specific Test" will consist of 200 randomly selected Questions > from a Catalog that contains thousands of Questions. There are other > constructs that handle things like Test Results, etc. Rails seems to > handle the model pretty well. > > Summary of the Issue: The requirement is that as new Questions and > their correlating Answer Options get created, about 100 per month, they > need to be loaded in bulk into the database, through an automated means. > The key is not to disrupt anything that already exists in the database > and automatically make the new Questions discoverable via the Catalog. > > Is there a clean way to handle this with Rails? I've been skimming > through things like Fixtures but don't know enough about them to > understand whether they'd help. > > Thanks, in advance, for any help you can offer. > > Frank > > -- > 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. > -- 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.
