Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current implementation does not allow filtering complex relationships, this PR add capabilities for the klepto users to proper filter table with relationships. Let's take this scenario:
I want to dump only the active
users
with theirorders
and it'sorder_items
And need to anonymise the email and firstName fields respectively
Given the klepto config
Tables.Relationships
fields are necessary to generate joins between tables behind the scenes e.ggenerated query for dumping users:
generated query for dumping orders from the users:
generated query for dumping order_items from the user orders:
FYI dumping large databases specially with the mysql-drive is pretty painful, a lot of bad conn errors are raised after some time dumping, this is where the filter comes in