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

Is there a guideline to migrate from obsoleta django-encrypted-fields? #20

Open
domdinicola opened this issue Jun 21, 2024 · 1 comment

Comments

@domdinicola
Copy link

django-encrypted-fields.

@hendrikschneider
Copy link
Contributor

I think the easiest is to create a new temporary field, read all values from the current encrypted field, save them into the temporary field.

After this is done, rename the original field to a different name and rename the temporary field to the original field name. Afterwards the data should be properly there. Lastly, when everything works you can delete the field with the old data (Be Careful here).

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