On Sat, Jun 02, 2007 at 12:05:20AM +0200, Alexander Staubo wrote: > All you would require is a simple boolean flag to enable or disable > automatic DDL propagation, surely. You know, it is just possible that some of the responses you are getting in this thread have to do with the glib way you say "just a simple flag", waving away all the corner cases and difficult parts. What do you do, for instance, when your automatic DDL wedges the replication system after data-replicating events have come in? What do you do when there happens to be a schema mismatch that you didn't know about? (How do you even detect such a thing?) That isn't a SMOP: it requires design that is not trivial, and you don't seem to be spending any time thinking about those issues before brushing off the current design as some sort of nasty thoughtless attempt to make your life more difficult on the part of those who have worked on the system. DDL changes require that every node have the new schema before any of the node-affecting data gets there. We have _enough_ problems with DDL failing on target systems without increasing this problem tenfold by doing it automatically. A -- Andrew Sullivan | ajs@xxxxxxxxxxxxxxx The whole tendency of modern prose is away from concreteness. --George Orwell