Hi,
Is there any reason why it would be a bad idea to include the database
name, ie:
set_table_name ''database.tablename''
in my models?
We have legacy tables spread across several databases in MySQL and we
use separate base classes for each which have their own
establish_connection''s to ensure they connect to the correct database.
The problem with this is that the :include option on find will not work
because it assumes the tables are all in the same database, but adding
the database name to the set_table_name seems to solve this.
Assuming all the databases are on the same server does anything think
this would cause a problem?
TIA
Kind regards,
Rob
--
Posted via http://www.ruby-forum.com/.
