Well, what happens if production crashes and you need to copy the mirror datafile over to production? Is it OK that those records owned by production haven't been updated in a long time from the mirror?
There's no technical reason you can't exclude that table... and like you wrote, if you do, you can modify records on either side. Personally, I think it's easier conceptually if the mirror is an exact copy of production (maybe except for truly temporary tables), and you know the mirror database will never be modified except by integration. -- Jeffrey Kain [email protected] > On Jan 8, 2018, at 4:13 PM, Chuck Miller via 4D_Tech <[email protected]> > wrote: > > Is this even possible in a mirror situation. I know one should not really be > changing any records in the mirror except through the journal, but would this > approach work? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
