Chris Travers wrote:
There are problems with that too. One can't just apply a fix where replication is at work in a database because that can screw up the replication. Because we want to offer a replication-friendly environment, automatic application of fixes is a bit problematic.
Hmm, ok. Still... when you upgrade versions, it's reasonable to expect that there might be a schema change (for other reasons, not just fixes) and that you should take that into account. I really believe that making it a policy that "Upgrades might require schema changes; take appropriate action" is the way to go. Regards, David.