🚀 go-pugleaf

Hello all.

Question 1:
In an N-way replication scheme via dial-up, we will want to add new users to
the system over time, and I am looking for the simplest way to do this.  I
tried to use Synchronization for this purpose.  However, when I ran the
synchronization it didn't work because the RI constraints are violated.

Is there a way you can define the order in which tables are synchronized?
If I update my child tables before the parent tables, I won't need to drop
the constraints.  Or will I need to remove the constraints before
synchronizing?  Or is there another alternative?

Question 2:
As a replacement for synchronization, I'm thinking of just taking a
different source database (after replication has been done with the server
target), copying the database to a new laptop as a new source DB, create a
new config DB for this new laptop, remove and re-creating the system objects
for both source and target.  Would this work as an alternative or is there
something else to watch out for?  I'm not sure of the impact on the schema
numbers in this solution.

Thanks.
-Mike