Mon May 22 12:51:48 PDT 2006
- Previous message: [Slony1-general] Change the slave's table name
- Next message: [Slony1-general] Change the slave's table name
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, May 22, 2006 at 03:33:56PM -0400, Andrew Sullivan wrote: > On Mon, May 22, 2006 at 10:48:46AM -0500, Jim C. Nasby wrote: > > > It's tricky, but you can often do it without application changes, as > > > long as you never do something dumb like SELECT *. > > > > Maybe I missed something, but wasn't the OP trying to replicate data > > from slaves back up to the master? > > I didn't have that impression: I had the impression of many remote > machines, and one central one that shared their data. If this is to > be two-way, then it does indeed become more tricky (although the same > general strategy might be made to work). Yeah, what I've told people before is that they can have one table for each site that is replicated to all sites, and then build a view on top of that that makes it appear as one table. -- Jim C. Nasby, Sr. Engineering Consultant jnasby at pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
- Previous message: [Slony1-general] Change the slave's table name
- Next message: [Slony1-general] Change the slave's table name
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list