Hello, Sharing a few thoughts here, I'd love to have your opinion. I have a datawarehouse that is rebuild totally from scratch each night (as opposed to incrementally) - basically drop database, db:migrate, then import. Works pretty well.
For an evolution, I'd like to keep some unimportant state (geocoding cache) into a database so it can be reused each night (and completed if relevant). Loosing the cache would not be a problem if it happened, we would just rebuild it. Are some of you using the etl_execution database for storing that kind of things, as I'm thinking of doing it ? I'm thinking about using an AR record, like: class CachedAddress < ActiveRecord::Base establish_connection :etl_execution end I would probably define an additional migration for that as well (like the ones built-in for :jobs,:records and :batches) by patching ETL::Execution::Migration migrate. what do you think ? thanks, Thibaut Barrère -- LoGeek [blog] http://evolvingworker.com - tools for a better day [blog] http://blog.logeek.fr - about writing software
_______________________________________________ Activewarehouse-discuss mailing list Activewarehouse-discuss@rubyforge.org http://rubyforge.org/mailman/listinfo/activewarehouse-discuss
