Colin Law wrote:
All this hassle makes one wonder whether it might be possible to
combine the two databases into one. That would make life a lot
simpler, if it were possible.
Colin
Amen. But since mine is a table containing 700K 18-column records of
unchanging data, I'm not giving up
On 14 August 2010 21:04, Fearless Fool li...@ruby-forum.com wrote:
Colin Law wrote:
All this hassle makes one wonder whether it might be possible to
combine the two databases into one. That would make life a lot
simpler, if it were possible.
Colin
Amen. But since mine is a table
Colin Law wrote:
Am I misunderstanding your question, or is it just a matter of doing
rake db_migrate RAILS_ENV=external
to migrate that db?
Colin
Colin: your answer was *perfect* for the question I asked.
Unfortunately, I'd over-simplified the question.
I have *two* databases: the
Fearless Fool wrote:
[...]
I've thought about how rake db:migrate works -- it modifies a database,
then asks the database to reveal its new structure to build a new
schema.rb. Given that, it doesn't have enough information to know which
tables belong in the regular database and which
On 13 August 2010 18:05, Fearless Fool li...@ruby-forum.com wrote:
[...]
I have *two* databases: the 'external' one holds static data -- it never
changes as a result of my application. The 'regular' database
(dbtest_development, dbtest_test, or dbtest_production) holds data that
does change
5 matches
Mail list logo
