Tue Feb 28 14:49:50 PST 2006
- Previous message: [Slony1-commit] By wieck: Forwarded log entries for cascading must go into the currently
- Next message: [Slony1-commit] By cbbrowne: 1.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message: ----------- Fix tagging of <command> Modified Files: -------------- slony1-engine/doc/adminguide: ddlchanges.sgml (r1.21 -> r1.22) -------------- next part -------------- Index: ddlchanges.sgml =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/ddlchanges.sgml,v retrieving revision 1.21 retrieving revision 1.22 diff -Ldoc/adminguide/ddlchanges.sgml -Ldoc/adminguide/ddlchanges.sgml -u -w -r1.21 -r1.22 --- doc/adminguide/ddlchanges.sgml +++ doc/adminguide/ddlchanges.sgml @@ -132,15 +132,15 @@ independent of one another, such as if you add two columns to a table.</para> -<command> alter table t1 add column c1 integer; alter table t1 add -column c2 integer; </command> +<para> <command> alter table t1 add column c1 integer; alter table t1 add +column c2 integer; </command></para> <para> Trouble arises if a subsequent query needs to reference an earlier one. Consider the following DDL statements... </para> -<command> alter table t1 add column c1 integer; create sequence s1; +<para><command> alter table t1 add column c1 integer; create sequence s1; update t1 set c1=nextval('s1'); alter table t1 alter column c1 set not -null; alter table t1 add primary key(c1); </command> +null; alter table t1 add primary key(c1); </command></para> <para> Up until &slony1; version 1.2, this query would <emphasis> fail </emphasis>. It would specifically fail upon reaching the
- Previous message: [Slony1-commit] By wieck: Forwarded log entries for cascading must go into the currently
- Next message: [Slony1-commit] By cbbrowne: 1.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list