K
K
kamchatkin2013-07-02 20:13:48
Ruby on Rails
kamchatkin, 2013-07-02 20:13:48

Working with arbitrary tables/data

When designing a new rails application, I ran into a problem that, due to my little experience, I don’t know how to solve.

The application consists of 2 parts.
1. Aggregator.
Collects data, cleans it and puts it in the database.
How to make this application clear, such experience already exists.

2. Client application.
Should be able to work with the database collected by the first application and make beautiful reports.
The application was decided to be made using RoR due to its simplicity and in order to pump the skill.

As far as is known, when creating a model by standard means

rails generate scaffold some_model

active record creates a table with its service fields: id, created_at, updated_at and also creates a model and controller file that describes the basic functionality.

The question is the following.
If the aggregator puts data into a database that was originally created using standard rails tools, will the rails application work correctly with this data and are there any problems that are not visible at first glance?

Or who can offer the best solution in this situation?
Thank you.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
O
OnYourLips, 2013-07-02
@OnYourLips

There shouldn't be any problems.
However, it would make more sense for the application to work with a ror REST service.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question