On 5/22/06, Jim C. Nasby <jnasby at pervasive.com> wrote:
> 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.
>

Instead of doing a view, you could also do partitioning with table
inheritance.  Each client gets its own inherited table to replicate
into.  It would be partitioned on the host.  Selecting from the parent
table will show all the rows

 - Ian