Wed Aug 25 20:05:14 PDT 2010
- Previous message: [Slony1-bugs] [Bug 117] syslog=2, messages go both to syslog and the standard output.
- Next message: [Slony1-bugs] [Bug 151] Let DDL for EXECUTE SCRIPT to be specified inline
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=151 Summary: Let DDL for EXECUTE SCRIPT to be specified inline Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: slonik AssignedTo: slony1-bugs at lists.slony.info ReportedBy: stuart at stuartbishop.net CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 Currently SQL scripts need to be stored separately from a slonik script in individual files. It would be great if there was some mechanism to store these scripts inline in the main slonik script. This would allow generation of complex slonik scripts easier and moving complex slonik scripts around less error prone. One possible approach would be a multi line quoting mechanism and a 'file' meta command that would store the string content in a temporary file and define a token. file foo <<EOM ALTER TABLE Bar ADD COLUMN baz text; EOM EXECUTE SCRIPT(set id=1, filename=@foo, event node=1); multi line quoting mechanism could just as easily be """ or ''' for Python similarity, or $$ & $x$ style for PostgreSQL similarity. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 117] syslog=2, messages go both to syslog and the standard output.
- Next message: [Slony1-bugs] [Bug 151] Let DDL for EXECUTE SCRIPT to be specified inline
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list