mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
DDC-3832: readOnly should be renamed to immutable in the mapping #4693
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Jul 16, 2015).
Originally assigned to: @Ocramius on GitHub.
Jira issue originally created by user stof:
readOnlyin the mapping is currently very confusing. Some people are using it to map entities to views, and then complain about SchemaTool-based projects (migrations for instance) because it handles things as table.But this is not the actual meaning of this mapping flag. Read-only entities can be inserted and deleted. The only forbidden action on them are updates. This makes the naming totally unsuited.
For reference, Hibernate uses "mutable=false" for the feature corresponding to our "readOnly=true".
@Ma27 commented on GitHub (Jul 14, 2016):
@Ocramius is it still relevant for 3.0? If so, I'd give it a try in the next days :)
@Ocramius commented on GitHub (Jul 14, 2016):
Unlikely: the benefit of a rename is next to 0, and it is just one more BC break