model.set doesn't fire its callback after a certain situation #185

Closed
ile opened this Issue Dec 10, 2012 · 2 comments

Comments

Projects
None yet
3 participants

ile commented Dec 10, 2012

Source code to reproduce the bug and instructions: https://github.com/ile/derbytest4

To reproduce:

  • insert a "row" that fails - the transaction must fail somehow (duplicate key).
  • after that, when inserting a row that should succeed, the callback won't be fired.
  • the row is inserted anyway, but the problem is that the callback wasn't fired.

I have the latest Derby & Racer.

kennu commented Feb 6, 2013

I just noticed this problem, too. I didn't verify the situation in which the callback doesn't get called, but sometimes it doesn't. This severely breaks an app that tries to call model.set() multiple times in a row, using callbacks to wait for the previous completion.

Contributor

nateps commented Apr 10, 2014

Master of Derby is now the rewritten 0.6 and I am removing previous issues pretty aggressively so that I can be more responsive to new issues.

Please re-open if this issue is still relevant in Derby 0.6.

@nateps nateps closed this Apr 10, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment