Marnen, Rob: I agree with Rob that it makes good sense to partition constant data into a separate db and use that consistently for development, test and production.
Marnen, maybe I misunderstand you, but even if I knew a priori which TimeDimension records my tests were going to use, it's a PITA to generate TimeDimension records piecemeal (what day did Easter fall on in 2005?) Furthermore, I have other large constant tables such as the location of FAA certified airports in North America, cobbled from multiple sources. Again, it would be a pain to figure out exactly which ones my test code will reference and then ETL their records on demand. ANYWAY, I'm in the process of setting up a "constant" database (separate from development, test or production) and I have questions about that. But I'll start a new post for that one. Watch for it... :) Thanks, y'all. - ff -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
