-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent cache #130
Comments
You could implement this with by adding a |
a php-based cache file, which dumps the output of similar as done here: |
But it's extremely insecure, it's okay with phpstan because it's a development tool, gdpr-dump can be executed on production environments. |
Is your feature request related to a problem? Please describe.
Scenario 1:
We have two databases that contain partially the same data because the corresponding systems communicate with each other via APIs and exchange this data (e.g. names and addresses).
Example goal: Person X with first name "Richard Roe" will become "John Doe" in both dumps.
Scenario 2:
A dump is automatically created every night for the development. Different anonymized values should not be generated every night for the same original values.
Example goal: Person X with the first name "Richard Roe" becomes "John Doe" today and "John Doe" tomorrow and not "Foo Bar".
In both cases, the resulting data for the same input is different.
Describe the solution you'd like
A possibility to persist the cache entries in a cache file. Then a next execution would already find the cached value and return the same result for the same input.
The text was updated successfully, but these errors were encountered: