On 10/5/2011 3:43 PM, Pete Blumenthal wrote: > I run a web app which allows users to cause dynamic schema changes-adding > columns to tables specifically. This operation doesn't happen often, but it > happens often enough that we don't want to have to manually SLONIK EXECUTE > SCRIPT every time we want to do a schema change. There is also a possibility > of write operations happening on the tables with dynamic schema changes at > the same times as the schema changes occur. > > Which is preferred solution for dynamic schema changes in production with > Slony-I 2.0, Why?
Applications changing the DB schema during normal production operation have always been problematic. Not only with Slony, but with databases, that do not cover DDL under transactional semantics, too. Changes that might happen to Slony 2.2 would make it possible to support this in a safe and secure manner, but those changes will most certainly not be backported into any earlier version. Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
