Mike,
Yeah. Makes sense. Good thought about the UUIDs! My success
was due partly to the fact that I could afford to move entire
tables,
not just selected rows, and could move all related tables as well.
Trying to move just some of a related set of data f
On 3/01/2017 12:32 PM, Fred Stluka wrote:
Mike,
Maybe you don't need a custom DB manager. Perhaps a simple
DB router would suffice? It's a Django way to specify which DB
to use based on which model is being used, whether it is being
read/written, etc.
That's the approach I took. The essence
Mike,
Maybe you don't need a custom DB manager. Perhaps a simple
DB router would suffice? It's a Django way to specify which DB
to use based on which model is being used, whether it is being
read/written, etc.
See:
-
https://docs.djangoproject.com/en
(this one might be easier to read)
I am planning some utility helper code to push selected records and
their children from our staging database into the production database.
The current database would be 'default' and I could add a second one
called 'production' then read from 'default' and wr
I am planning some utility helper code to push selected records and
their children from our staging database into the production database.
The current database would be 'default' and I could add a second one
called 'production' then read from 'default' and write to 'production'.
(I need to chec
5 matches
Mail list logo
