Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | SYN-377: Make sure that the StreamIdGenerator.get_next.__exit__ is called ↵ | Mark Haines | 2015-05-12 | 1 | -4/+8 |
| | | | | from the main thread after the transaction completes, not from database thread before the transaction completes. | ||||
* | Typo | Erik Johnston | 2015-04-29 | 1 | -1/+1 |
| | |||||
* | Also remove yield from within lock in the other generator | Erik Johnston | 2015-04-29 | 1 | -8/+6 |
| | |||||
* | Fix deadlock in id_generators. No idea why this was an actual deadlock. | Erik Johnston | 2015-04-29 | 1 | -14/+16 |
| | |||||
* | Make get_max_token into inlineCallbacks so that the lock works. | Erik Johnston | 2015-04-27 | 1 | -3/+4 |
| | |||||
* | Use try..finally in contextlib.contextmanager | Erik Johnston | 2015-04-15 | 1 | -3/+5 |
| | |||||
* | Correctly increment the _next_id initially | Erik Johnston | 2015-04-14 | 1 | -2/+4 |
| | |||||
* | Stream ordering and out of order insertions. | Erik Johnston | 2015-04-09 | 2 | -0/+140 |
Handle the fact that events can be persisted out of order, and so to get the "current max" stream token becomes non trivial - as we need to make sure that *all* stream tokens less than the current max have also successfully been persisted. |