add slonik path generation for slony replca set nodes with fallback configuration data
slonyReplicaSet and slonyReplicaSetNode database connection overrides are optional
generate a create set statement as part of the slonik subscription file
need semicolon at end of CLUSTER NAME declaration
only put slony nodes who are used in the replica set in the preamble
refactor build_slonik_subscribe_set() as build_slonik_create_set() because thats what its really doing - generate the slonik to create the set to the subscribe replica nodes to
generate slony replica set subscription files for each node in the replica set
store paths that make sense
tweak slonyId reporting to actually report segments with one number missing in a run
return after non-slony diff_doc_work() when generate slonik mode is not in effect
remove abandoned database sub elements as of API 1.3 ; do not create slony configuration elements in pgsql8 extraction XML -- this is a configuration process for the user to do once the schema has been reviewed
sql tags can and should have slonySetId attributes
filter REFERENCES .. ON UPDATE|DELETE dialecting for pgsql8 with a partical pgsql8_constraint implementation
warn code maintainers about the partial implementation of pgsql8_constraint
remove XML database section elements removed as of DBSteward API 1.3
Fixed DuplicateSlonyIdsTest to account for new replica set determinations
when generating index dimensions, always give them a name, require indexDimension names as of DBSteward API 1.3
require autoloader to fix some tests
Merge branch 'master' of https://github.com/nkiraly/DBSteward
Updated a number of tests, added a commented-out section in sql99_table that may be a potential fix for an issue