Nothing has been decided. If we do add support for this, it will need to go behind a configuration flag so that we don't break existing applications.

I would love to see this implemented. Sometimes it's also easier to pass the full entity around instead of having to create another for the occasion of executing a DB query, even if the query doesn't use all fields of the entity.

This can make creating queries for seeding the database a lot easier, otherwise, you'll end up with twoCreate queries with duplicated insert fields. This is not a problem if you have few columns but when you have 50 columns in a table, you need to keep track of both queries and update both when you add a new column to the table.

I'd like to know if there is any way right now to do this nicely.