Am Sonntag, 26. August 2018 18:07:25 UTC+2 schrieb Jason: > > why would you want to persist unvalidated data to your db? > >> >> Well, i dont necessarily have to, but i somehow need to be able to perform a query with all updated data taken into account. The easiest solution i came up with is putting everything into the DB while in transaction so i could perform my queries and rollback if the checks dont work out.
Im open to any other ideas. And is there a prepared admin function that is suitable for validation logic after related objects are validated? I might also just write some validation data to the parent while executing the formet validation and so i could verify my parent validation against this extra data even without additional queries against the DB. So far i just see that the changeform_view handles object and formset validation without any way of interfering (other than rewriting that view logic). -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2f46c2d4-a628-4571-8f23-9607125d462b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
