The data is quite volatile. The schema typically has some changes during each release cycle. We currently point at shared DBs, which I'm thinking is the direction we'll stick with. But we are talking about all of the suggestions mentioned here. I can see the benefit in having local DB as well--in fact this is how I've developed in the past, and understand how easily this scenario can break the app for other developers (who may not be in a position to update their local code-base for whatever reason).
> On Tuesday 17 Jul 2007, [EMAIL PROTECTED] wrote: > > As for running local DBs, not sure that is an option as our DB is > > large. That would mean regular downloads/restores on every dev > > station? This does beg the question of how we'll manage keeping our > > dev data in tune. It's time consuming with 1 or 2 DBs, but start > > talking 9 or 10, we're looking at a lot of time. > > Depends how often the data / schema changes - if this is infrequent you could > point all the dev's at a shared DB. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:283971 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
