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

AuditLog error when cloning objects #664

Open
raayu83 opened this issue Aug 9, 2024 · 2 comments
Open

AuditLog error when cloning objects #664

raayu83 opened this issue Aug 9, 2024 · 2 comments

Comments

@raayu83
Copy link

raayu83 commented Aug 9, 2024

I'm trying to clone objects including their m2m fields using a solution I found on StackOverflow.

Unfortunately I get the following error:
null value in column "object_pk" of relation "auditlog_logentry" violates not-null constraint

I assume this is because the cloned objects pk field has to be set to None in order for it to be assigned with a new ID automatically.

Is there any way to work around this?

@jcgiuffrida
Copy link

You can get around this by manually assigning an id to the copied object but be very careful it's not an ID already in use, or you'll overwrite something else. You could also probably temporarily unregister the model with AuditLog, which disables the signals.

@raayu83
Copy link
Author

raayu83 commented Aug 26, 2024

Since these seemed more like hacks than an actual solution I switched to django-simple-history which suits my usecase better

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