Slide wrote: > I liked the idea someone mentioned about having a sort of source > control mentality about it all. You can grab a working copy and put it > on your laptop for meetings and then when you are done, you can > "commit" the changes back into the main repository or database. This > could be achieved in a variety of ways.
That's a fine idea, but an important risk is the difficulty of merging conflicting updates. Conflict resolution in source code works because it's all text and you can use the same tool (a text editor) to resolve conflicts as you use to write code. Conflict resolution in a database can be much trickier. The problems can be solved, but in practice, the need to avoid and resolve conflicts tends to influence the design of the whole application. Shane _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
