Neil Clayton

I'm setting up a scenario where each customer has some shared data (currently residing in the 'public' schema) and their own data in their own named schema (e.g: site_wft_1). This is on postgres. The tables are generated via Django, and contain FK links from the per-'User' models to the 'Shared' models. e.g: site_wft_1.System4000_User_job references public.System4000_Shared_customer When I try to do a load, the creation of the 'users' tables fails because the schema naming is incorrect. In the logs...

OK. Here is some DB SQL: https://www.dropbox.com/s/1o84qpi3bpinf2c/symmetricDSArchive.zip?dl=0 This includes various SQL files you might find useful. I dumped the entire DB after setting it up (including sample data and triggers/routers). See "Entire Master.sql". I can replicate the problem by executing the DeleteTheLogin script on master, and seeing the fault on a slave (well, seeing it not work because the router can't make the link to the login any more). I've included properties files for both...

Will do. It'll take me a while to par it down to something simple. I'll see if I can get a simple self contained project available to demonstrate the prob.

Will do. It'll take me a while to par it down to something simple. I'll see if I can get a simple self contained project available to demonstrate the prob.

I've been testing SDS as a solution for the master-corp/separate stores situation, where each store has a subset of data. I'll use the term "master" to refer to the master-db. The 'corp'. I'll use the term "client" to mean any node with filtered data. I'm running into two problems: 1) If I delete both a m2m row and dependent row, the dependent row isn't deleted on the client. 2) If I update the owner of the row, the old dependent row isn't deleted on the old client (the previous owner) Triggers use...

I've been testing SDS as a solution for the master-corp/separate stores situation, where each store has a subset of data. I'll use the term "master" to refer to the master-db. The 'corp'. I'll use the term "client" to mean any node with filtered data. I'm running into two problems: 1) If I delete both a m2m row and dependent row, the dependent row isn't deleted on the client. 2) If I update the owner of the row, the old dependent row isn't deleted on the old client (the previous owner) Triggers use...

I've been testing SDS as a solution for the master-corp/separate stores situation, where each store has a subset of data. I'll use the term "master" to refer to the master-db. The 'corp'. I'll use the term "client" to mean any node with filtered data. I'm running into two problems: 1) If I delete both a m2m row and dependent row, the dependent row isn't deleted on the client. 2) If I update the owner of the row, the old dependent row isn't deleted on the old client (the previous owner) Triggers use...

I've been testing SDS as a solution for the master-corp/separate stores situation, where each store has a subset of data. I'll use the term "master" to refer to the master-db. The 'corp'. I'll use the term "client" to mean any node with filtered data. I'm running into two problems: 1) If I delete both a m2m row and dependent row, the dependent row isn't deleted on the client. 2) If I update the owner of the row, it isn't deleted on the client Triggers use an EXTERNAL_SELECT to fill in EXTERNAL_DATA....