-
Notifications
You must be signed in to change notification settings - Fork 7
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
Feature: conditional transform #34
Comments
I wonder, does that condition apply to the whole record or a specific transformer? So here is the definition of the transformation now:
In my point of view, there might be a condition for the whole record and for specific transformer. The prototype might be:
If we are talking about tuple filtering then it is connected with other features (database scale down). As for now, it is better to use the |
This applies to the whole record. It is very useful to also selectively not anonymize certain column values. We have been able to achieve that with an if statement in template logic. However it would be useful to have a declarative way of doing it as you show. |
Just want to inform you that this feature is going to be published right after the next major |
A conditional transform states a SQL condition used to decide whether or not to transform a row. In datanymizer a where clause is given as a string. This API seems to work. Below
groups
is a table.Datanymizer implemented this by adding
NOT
to the given query. I fixed an issue that addingNOT
also needs proper NULL-checking behavior: datanymizer/datanymizer@24e2521The text was updated successfully, but these errors were encountered: