Instead of returning a new Tuple, dialects can update/put values to the tuple passed into insertOrUpdateTuple() etc. That's used for store-generated ids already now. So this issue is basically out-of-date.

I'm leaving it open in order to re-visit the retrieval of generated values from within the engine. Instead of re-loading the tuple, we may check the tuple passed in for alterations and update the entity based on those.