RelationProxy reset query about dpq

[IrenejMarc]

RelationProxy, being an unfinished API is not exactly what I had planned initially.

The current idea is to not change the state in the RelationProxy itself but instead make a copy and modify the state in that. That'll allow you to reuse the same initial instance of multiple times and just build queries on top of that like such:

auto rp = RelationProxy!User;
auto allRows = rp.all;
auto filteredRows = rp.where("row = 1").all;
// and so on

This eliminates all need to reset the state/queries.

The current solution is to use the RelationMixin inside User since each of its methods spawns another instance of RelationProxy.

[Betelgeyser]

That clarifies a bit.

But this approach renders caching unusable since in the case of copying the initial RelationProxy it will always be marked as 'stale'. Or rather difficult to make a RelationProxy to track if the new chain can use cached data from the previous one. Besides, user can easily make his/her own cache like this:

auto rp = RelationProxy!User;
auto cachedUsers = rp.all;

Should the caching be maintained somehow or be just removed from the RelationProxy?