Hi,
I believe that I encountered a bug or at least a serious limitation with
transaction.on_commit in Django 1.9.x. Essentially, the on_commit hooks
seem to be tied to the database connection instead of the transaction. This
means that unrelated transactions may trigger on_commit hooks, which
The callbacks are indeed run when autocommit is restored, but they are not
executed one after the other, i.e., they are not **all** executed when
autocommit is restored. The relevant code in Django:
# Called by set_autocommit(...)
def run_and_clear_commit_hooks(self):
self.valida
Hi Carl, thanks for your input.
I opened a ticket (https://code.djangoproject.com/ticket/26627) and
submitted a pull request based on your
suggestion: https://github.com/django/django/pull/6617
Bart
On Tuesday, May 17, 2016 at 1:52:58 AM UTC-4, Carl Meyer wrote:
>
> Hi Bart,
>
> On 05/16/2016
I believe I found a limitation in the Django jsonb support, but I'm really
not sure how the framework could fix it beside adding a limitation section
in the documentation.
Basically, it is possible to fetch models with json 'null' values but it is
not possible to save them back (Django converts
4 matches
Mail list logo
