DDC-3603: Readonly columns

[doctrinebot]

Jira issue originally created by user sparrowek:

Sometimes I have a column that is calculated (or have a default value) at the database side. When inserting a new record doctrine issues NULL into such a column that causes problems on some DBMS. I would like to annotate such columns as readonly so that doctrine would skip them in INSERT and UPDATE clauses but still fetch them in SELECT clauses.

[Hikariii]

Issued a PR for exactly this: #5728

[Hikariii]

@beberlei This becomes more urgent as more people start using mysql 5.7 and generated columns.
See #5728 for more details on why this is important.

[Ocramius]

Described my thoughts about this feature in #5728

[dbu]

as #5728 has been closed, should this be closed too?

if you write your query in dbal, you can completely hide columns from ORM with a schema listener. the column won't be mapped on the entity however, and is not available for DQL / ORM query builder.

[0xPaul]

This should not be closed because, as far as I can tell, there still isn't support for read-only generated columns within the ORM.

[garak]

Readonly on primary keys is not working for me. As soon as I try to hydrate the object, the UnitOfWork tries to call setValue method on the property, resulting in an exception ("Attempting to change readonly property My\Entity\Foo::$id.")

[derrabus]

@garak The ticket you are commenting on has nothing to with the PHP language feature readonly. Please file a bug for your issue.

[beberlei]

This was implemented in 2.11 as virtual and generated columns