mj-p

Maybe adding an option to apply inactivity_timeout always instead only when close to limit of connections somewhere along those lines: [https://github.com/arvidn/libtorrent/blob/505c63b3bc8bd0c16aa44d224543fcb3962d4b9b/src/peer_connection.cpp#L4975-L5011](https://github.com/arvidn/libtorrent/blob/505c63b3bc8bd0c16aa44d224543fcb3962d4b9b/src/peer_connection.cpp#L4975-L5011)

Despite this being a rather specific case with limited options provided by HATEOAS I guess it feeds into this issue (#1044)? Being able to have annotations on the generated implementation...

After digging a bit more through the issue it makes sense this wont work. Maybe the idea for our own Query annotation seems a bit overkill but should be doable...

I tested a bit more and 6.4.4 doesn't change anything. When using one of the blaze-persistence examples with javax and version 5.6.10 the scenario actually works. There the generated HQL...

The relation looks like this: For Cat ```java @OneToOne(mappedBy = "cat") private Toy favouriteToy; ``` For Toy ```java @Id @GeneratedValue private Long id; @OneToOne private Cat cat; ``` Now from...

I hope this is enough to work with. I replaced the DbmsDialect of H2 with the PostgreSQL one in the Configuration to make sure the buggy query gets created. This...