Aaron Barthel

@solnic you were saying that you regret adding `result: :many` or `result: :one` but maybe a custom command set with `result: :void` could trigger this behavior?

@solnic how would you envision configuring if results are returned or not? I imagine, you'd want to be able to do something like: `relation.command(:create, option_name: :value)` but what would you...

I literally ran into this exact same problem a few moments ago. An additional gist showing this bug in action with **rom v4.2.1** & **rom-sql v2.4.0**: [Combine overrides default dataset](https://gist.github.com/abrthel/9d65828e1a3871fd73f773d2d5c6e450)

After a bit of sleuthing, I believe the issue lies with rom schemas, If you change the selections of the relation at the dataset level then the relations schema doesn't...

In my case explicit schema definitions didn't work and as far as I know, there isn't a way to explicitly define attributes on a schema that targets another table. The...

Thanks to @mrship I've stumbled upon a solution to this issue. **TL;DR;** I've updated my reproduction script to show the fix [Combine overrides default dataset FIXED](https://gist.github.com/abrthel/9d65828e1a3871fd73f773d2d5c6e450/revisions) ### The Problem During...

Technically it says something to that effect on the first rom-sql page in the first paragraph but that's probably something that should get a bit more attention. [http://rom-rb.org/4.0/learn/sql/](http://rom-rb.org/4.0/learn/sql/)