-
-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid Entities #778
Comments
Entity generator and surrounding facilities have been deprecated and removed from the next ORM major release, and they will not be improved. |
I was also speaking in terms of ORM, that is, because writing in the |
@chiqui3d at this point in time, the ORM core team is unanimous about the opinion that entities should not be generated, but designed. Even read-only objects need that (typical example: lookup read-only tables). |
I don't understand how doctrine does it automatically for setID and not for the other columns, it's primitive. I just created 50 column and I have to go one by one writing |
@chiqui3d doctrine does never touch the public API of your methods: it uses reflection to set/get data from your objects. |
@Ocramius this behaviour should me mentioned in docs (if it hasn't been there already) this is not obvious and a lot of people are asking for this |
Can you maybe send a patch to the documentation? Would be great to get an
explanation about it in
https://www.doctrine-project.org/projects/doctrine-orm/en/2.6/reference/working-with-objects.html#working-with-objects
…On Fri, 8 Jun 2018, 08:03 Jarek Jakubowski, ***@***.***> wrote:
@Ocramius <https://github.com/Ocramius> this behaviour should me
mentioned in docs (if it hasn't been there already) this is not obvious and
a lot of people are asking for this
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#778 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJakPosWqQVX6lf0q2ltYwKkvuuaXOmks5t6gWrgaJpZM4SGaTt>
.
|
@Ocramius here you go: doctrine/orm#7253 |
Thanks @JarJak! |
Is it not possible to avoid generating or creating getters and setters for columns that do not have to be modified?
It really doesn't make any sense to create getters or setters that are not going to be modified in the final result. I think this option would be very useful.
The text was updated successfully, but these errors were encountered: