Mark Story

> The Tree Behavior should contain a warning that it is not thread safe / safe for concurrent requests. Sure we can update the documentation, I don't think there is...

> Could we solve this with transactions somehow? Not in most database deployments. Solving this with transactions requires `serializable` transaction isolation. Repeatable read, and read committed would still allow concurrent...

This is likely due to differences in how the SQL is generated. Containing an association does behave differently because of how the semantics of the ORM have worked for a...

Bumping to 5.1 as we haven't implemented enum support into routes yet, so it isn't a defect. I do agree that it is a useful addition :smile:

I can see two ways the signature linking could be implemeted: 1. As a separate tool that we run periodically to 'sync' signature from the code into RST docs. 2....

I took some time to look at this tonight and I'm not sure there is a feasible solution for this other than to throw errors when `skip` is used multiple...

@nishimura-d That does look incorrect. I can get that condition and the related one for connectionsToDrop but those changes don't seem to change the behavior in a way that will...

> I don't think this message is appropriate. What would make more sense to you? > Since my misunderstanding has been resolved, I am fine with closing this issue as...

That works for me too. Did you want to put a pull request together for that? If not I'll get to this eventually.

@mcube27 No it won't. If you don't want to see deprecations you can turn them off. But you'll need to address the deprecations before you can upgrade. Upgrading migrations may...