On Thu, Oct 06, 2005 at 04:57:56PM +0000, Andreas Pflug wrote:
> Tim Goodaire wrote:
> >On Thu, Oct 06, 2005 at 11:24:52AM +0000, Andreas Pflug wrote:
> >
> >>Christopher Browne wrote:
> >>
> >>
> >>>It's just that "completeness sake" dictates mentioning that this isn't
> >>>the only scenario where a set can have no tables.  I can't call the
> >>>problem "solved" unless all of the scenarios are addressed.
> >>
> >>A reasonable use-case of empty sets is replication of ddl scripts. One 
> >>might like a set dedicated to ddl scripts only.
> >
> >
> >You don't replicate ddl scripts. You replicate tables and sequences
> >only. A ddl script is applied to a set, but if that set doesn't contain
> >anything, I don't know how useful it'd be.
> 
> So you don't call it "replication of ddl scripts", but "applying ddl 
> scripts to a set". The result is the same, the ddl is replicated...
> 
> You might need to target such ddl changes to all nodes in a replication 
> topology (your enterprise wide schema), but like your data replicated 
> individually between nodes. That's the case I'm talking about.

Ok. It's becoming a little more clear for me. I think. 

You would like to be able to apply ddl changes to all sets in a cluster.

> 
> Regards,
> Andreas

-- 
Tim Goodaire    416-673-4126    tgoodair at ca.afilias.info
Database Administrator, Afilias Canada Corp.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20051006/10be6d4d/attachment.bin