Comments (3)
Hi Martin,
I will do some investigation. Can you confirm that this in fact a problem with graphene-django-cud
and not with django-simple-history
? E.g. if you perform the same tasks manually (create object, add to m2m-relation), do you get the behaviour you epxect?
If you are attaching existing objects to the m2m-relation, the post_save
-signal will not be fired; the m2m_changed
will be fired (https://docs.djangoproject.com/en/2.2/ref/signals/#m2m-changed). I don't know if that is a limitation with django-simple-history
.
All saving of instances done in graphene_django_cud
is performed using the regular .save()
method. Hence post_save
should be fired in all relevant scenarios.
from graphene-django-cud.
Actually, reading your comment a bit more carefully, it should probably fire the post_save
signal there. I'll get back to you.
from graphene-django-cud.
Sorry, Tormod, I was mistaken. This is an issue with django-simple-history
which fails to create a historical record even when using the shell, so it's not an issue in this library.
from graphene-django-cud.
Related Issues (20)
- How to query errors from the mutation result? HOT 1
- This package ROCKS!!! HOT 1
- many_to_one_extras not correctly saving reverse relations
- Cryptic error message on `unique_together` error when using DjangoPatchMutation
- Mutations and DateField issue in graphene-django-cud code
- Improve documentation
- Incompatibility with latest graphene-django v3.1.2, due to import of `compat.JSONField`
- Release after graphene-django's compat.JSONField removal HOT 1
- Missing documentation in "Nested fields" about excluding fields
- many_to_many_extras with through table referencing the same model HOT 2
- Respect Django's own validation mechanism HOT 7
- Some proposals for improvement HOT 1
- Make it possible to configure calling `obj.full_clean` on all mutations as a part of natural object validation HOT 3
- [Batch mutations]: Create a hook for altering a single object's input data
- Add support for optional foreign keys with foreign_key_extras
- Add get_or_create support for foreign_key_extras
- Is there a way to use nested "many extras" to create/update/remove at once, without separate fields?
- Getting error 'super' object has no attribute 'items' when performing a create mutation on model with a ForeignKey on itself
- Nested one-to-one fields
- End of life HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from graphene-django-cud.