AndrewSisley

I do see this as by design, any the results of any action returning an error should not be trusted and should instead be ignored. The example test cases above...

> A user will have acp on a collection and they want to be able to write without reading? Keep in mind when we talk about write we are only...

> I am not sure I understand this fully, so I tested this on one of the new tests and the tests still pass if the last action has a...

> I could have sworn that before applying delete there was a check for primary key existing DocIDs are public I think, so when I talk about delete I assume...

> > Yes, but in that case you are expecting both a result and an error from a single action, which makes no sense IMO. If you want to test...

Ah nice - would be safer than silently ignoring it :)

I'm not sure this is specific to Views, and I'm not sure we want to do anything about this. Constraints such as `Size` can vary across nodes, and across definition...

> the help menu in defraud client p2p collection is faulty. "getall" doesn't seem to be supported and "describe" seems to be filling this role now Hi Alex, `getall` seems...

There are multiple tasks in this ticket. - Add support for variables (confirmed with quick test, we dont support them) - Add support for alias targetting (independently of whether it...

Is a discussion on this in the discord thread dev-db/"Alias targeting syntax" https://discord.com/channels/427944769851752448/1036675536971374694 Alternative syntax suggestion: ``` query { User(groupBy: [Verified]) { Verified _sum(_group: {alias: "pointsAvg"}) _group(groupBy: [Name]) { Verified...