Topic: Does Rails need to know everything about a database?
(using rails 3.1)
I ask this because I am developing a timecard interface (in Rails) to an existing accounting system which manages employee hours, grants and projects-billed-to.
Since I am making some small changes to the existing system to work with rails, I thought I would do the following:
- start building the new database with Rails migrations of the data structures Rails needs to know about.
- after the data structures needed by the Rails app have been created, use postgreSQL to add the remaining fields (ex. employee health care benefits, dependents, gender etc.) and tables used by accounting but not used by the Rails interface.
Is this going to work for Rails, or is Rails going to throw a fit because of the stuff in the database it doesn't know about?
Thanks for any help you can offer. --Fred