I am faced with a unique RoR design Issue and thought of getting some
advice on how go about this requirement.
I need to:
Create a web application to
1. login / Logout/ Manage Users
2. Register queries with boundaries for reporting.
3. Work flow engine to ensure BP
4. Scheduler to execute jobs on Legacy DB
5. Get Transactions from Legacy DB and store in application DB.
5. Once approved, send email reports with Transactions.
6. Store transaction data from Legacy DB to application DB - back up
7. Application users will be able to search queries and have a look
8. Transaction data is not needed to be shown from the Web GUI though.
I am stuck here.
1. Read from Legacy table(s)
2. Store transactions from legacy table into application table for later
What is the best way to read from legacy Oracle Tables which are
partitioned and Massive. What are the issues here as the legacy table
structure is unique and does not cater to RoR standards.
Can i use Ruby gems to fire "SQL select" and use RoR migration technique
to store results in to applicate table? Is that even possible? Or
should i create views in my application DB first and just do plain
reading from them?
I am not sure how to go about rading from legacy first, storing the
search results into application data!
Any inputs will be appreciated.