Mon Jun 4 07:49:53 PDT 2007
- Previous message: [Slony1-general] Error after EXECUTE SCRIPT
- Next message: [Slony1-general] Do we need to stop the write activity during a slave initialization?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michal Taborsky - Internet Mall <michal.taborsky at mall.cz> writes: > Andrew Sullivan napsal(a): >> happened. One thing that certainly happened, however, is that your >> script contained some commands that weren't supported. In the docs, >> it says, "The script must not contain transaction BEGIN or END >> statements, as the script is already executed inside a transaction." > > I'm fairly sure it was the begin-commit that broke it. The script > itself was like this: > > BEGIN; > ... some DDLs ... > COMMIT; > > > Wouldn't it be possible to check the script for these commands > beforehand, then? I mean, it would be real nice, if slonik produced an > error message, instead of breaking things. I'll put that on my TODO list, as it ought to be possible to detect this. -- output = reverse("ofni.sailifa.ac" "@" "enworbbc") <http://dba2.int.libertyrms.com/> Christopher Browne (416) 673-4124 (land)
- Previous message: [Slony1-general] Error after EXECUTE SCRIPT
- Next message: [Slony1-general] Do we need to stop the write activity during a slave initialization?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list