Mick Hansen

@xperiandri I have no strong feelings about this :)

Is there any way to produce an error response without having to `raise`?

`ctx.AddError` plus middleware that adds the errors to the response works decently, but you lose `path`. It'd be great to have `path` exposed in `ResolveFieldContext`

When we process associations we attempt to dedupe each row by either matching primary keys or row uniqueness. Any chance the task rows are completely equal? Seems like it's doing...

`id` is the default name for our primary key, so that should just work actually.

@pateketrueke there's no reason to use `plain` unless you're playing with raw queries or custom aggregates. You'd solve your issue most easily by having a primary key on your pivot...

We don't support duplicate entries for through tables currently. You'll have to manually setup associations to and from ownership and manually include it for it to work currently.

@Domiii No work has been done as of yet. That is your best alternative yes, personally i think that's the best solution always but that's just me.

@kopertop There's a difference between indexes and constraints, we support multi column indexes on all tables.

For everyone +1'ing this, are you looking to reference tables with multiple primary keys or what are the usecases here exacttly?