Different schema for select and mutations

[ijsnow]

I see that you can make fields optional by setting a default value in the schema, but it would be great to be able to pass different schemas for select, insert and update.

You can see a use case in the react projects example in this repository. The "select" schema's include all the fields which is awkward because the example goes through the effort to generate a random number for an id, even though it is omitted in the trpc layer anyway.

Additionally, there are benefits to having different schemas for insert and update. For example, databases being the source of truth for defaults for creation, and setting a default value for an update transaction could overwrite data when you are providing partial data.

[KyleAMathews]

An id is required for selects because the UI and routing requires one. The insert there is the optimistic insert which gets discarded when it loads the backend state.