Design question: support CUD-operations with/without `RETURNING`

[kolemannix]

I love that the full row is returned by default. This is really useful and generally ideal. However, sometimes we just do not need it, and the JDBC -> case class decoding, as well as extra bandwidth used, is unnecessary.

It would be great to have an insert that does not return the row. The question is, should this insert support returning generated columns at all? I would say 'no' for simplicity; if you need returned generated values, call the regular insert.

As a workaround, we would just use insertUnsavedStreaming with a stream of 1 element, but we are not on Postgres 16 yet.