Yes... the initial idea was to pull data from a database(s) that are not in our control and not writable (hence no prod/dev distinction). I do think this is essentially the same as integrating with legacy dbs. It's just that at this point there is not yet any functional need for a local database, and the concept of a "main" database for the app (which is what the single prod/dev organizational model sort of implies) is an ill fit in this case. In the future, maybe, and at that point I'd add the prod/dev dbs for that.
Sounds like going with unused sqlite stubs is the way to go then. Thanks! -glenn On Sun, Feb 13, 2011 at 10:52 AM, Cynthia Kiser <[email protected]> wrote: > > I am not clear why you don't want the current databases to be > development+production. Is it because they are some legacy dbs you are > integrating with? In any case, for what you have currently laid out as > your requirements, I think your idea of leaving the SQLite dbs as > stubs is actually the cleanest. -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
