39 ms·
we're actually working on this right, can see the PR here -> https://github.com/nucleuscloud/neosync/pull/1832/files https://github.com/nucleuscloud/neosync/pul
by edrenova 2y ago
we're actually working on this right, can see the PR here -> https://github.com/nucleuscloud/neosync/pull/1832/files https://github.com/nucleuscloud/neosync/pull/1832/files
it's a combination of creating a random number of records for foreign keys i.e 1 customer - create between 2 and 5 transctions. Working on giving you control over that, and handling referential integrity with table constraints (foreign keys, unique constraints, etc.)
ML based approaches typically are not very good at this and struggle with handling things like referential integrity. So a more "procedural" or imperative way is slightly better. The ideal is a combination of both.