Skip to content
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

What about unique and non-empty/non-null fields? #9

Closed
bnisevic opened this issue Jan 16, 2020 · 1 comment
Closed

What about unique and non-empty/non-null fields? #9

bnisevic opened this issue Jan 16, 2020 · 1 comment

Comments

@bnisevic
Copy link

What happens with fields which has unique constraint or they can not be empty?

@radiac
Copy link
Contributor

radiac commented Jan 16, 2020

At the moment we don't detect or do anything special for them automatically, but you can create a custom anonymiser: https://django-gdpr-assist.readthedocs.io/en/latest/privacy_meta.html#anonymise-field-name-self-instance

For example:

class MyModel(models.Model):
    slug = models.SlugField(unique=True)

    class PrivacyMeta:
        def anonymise_slug(self, instance):
            instance.slug = f"slug-{instance.pk}"

@radiac radiac closed this as completed Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants