Re: Tools for moving normalized data around

2023-01-18 Thread Rob Sargent
On 1/18/23 13:15, Gavan Schneider wrote: On 19 Jan 2023, at 6:47, Peter wrote: Now I want to grab some part of the data, on a certain condition (let's say all records belonging to user 'Bob', if there is a "user" table somewhere at the tree-bottom), and move it to another database with the very

Re: Tools for moving normalized data around

2023-01-18 Thread Gavan Schneider
On 19 Jan 2023, at 6:47, Peter wrote: > Now I want to grab some part of the data, on a certain condition > (let's say all records belonging to user 'Bob', if there is a "user" > table somewhere at the tree-bottom), and move it to another database > with the very same layout - which is already popu

Re: Tools for moving normalized data around

2023-01-18 Thread Dominique Devienne
On Wed, Jan 18, 2023 at 9:03 PM Jeremy Smith wrote: >> How to do this with two tables connected via one foreign key, that is >> explained a dozen times in Stackoverflow. But what if the tree is 50 >> tables and 120 foreign key columns? >> It can be done. But probably not manually. >> >> So, as thi

Re: Tools for moving normalized data around

2023-01-18 Thread Jeremy Smith
> > > How to do this with two tables connected via one foreign key, that is > explained a dozen times in Stackoverflow. But what if the tree is 50 > tables and 120 foreign key columns? > It can be done. But probably not manually. > > So, as this seems a very usual use-case for normalized data, is t