Develop new queries API based on collections (#51)
Api should:
1) Be based on collection concept
2) Be suspend/use flow/use channel
3) Support entity views (#77)
Api shouldn't:
1) support lazy loading
2) support entity cycles in first version
At first the api may return all entities of collection, that can be manipulated by standard kotlin's collections operations, but it should provide way to backward compatibly introduce a way to filter collection internally.
Develop new queries API based on collections (#51)
Api should: 1) Be based on collection concept 2) Be suspend/use flow/use channel 3) Support entity views (#77)
Api shouldn't: 1) support lazy loading 2) support entity cycles in first version
At first the api may return all entities of collection, that can be manipulated by standard kotlin's collections operations, but it should provide way to backward compatibly introduce a way to filter collection internally.
Cases to consider:
Study JPA's EntityGraph feture