document how to work with generated columns #11834
Conversation
dbu
force-pushed
the
document-generated-columns
branch
from
ae6a9e1 to
a0780a8
Compare
i was wondering. happy to do that. would that be the 2.21.x branch? i do not see a 2.x branch. |
dbu
force-pushed
the
document-generated-columns
branch
from
2381482 to
b0d794a
Compare
|
does the CI provide a preview somewhere so i can check if anything is rendered incorrectly? |
|
2.20.x, and there is no preview, but you can generate the html locally by doing what the ci does |
| expressed with Doctrine mapping. ``columnDefinition`` specifies the full SQL | ||
| to create the column. To allow to use database specific features, this | ||
| attribute does not use DQL. Note that we use the database column names with | ||
| snake_case to reference the fields, and not the entity fields with camelCase. |
There was a problem hiding this comment.
This makes a lot of assumptions on configuration and is also not very clear in some parts. Can you re-read this a few times and simplify?
Snake Case vs Camel Case depends on how the naming strategy is configured. Default behavior is not the Symfony behavior.
There was a problem hiding this comment.
uh, i was not aware that snake_case is not the default strategy. i changed the example and adjusted the text to explain things without assumptions. better?
dbu
force-pushed
the
document-generated-columns
branch
from
b0d794a to
712e912
Compare
dbu
force-pushed
the
document-generated-columns
branch
from
712e912 to
285c6cc
Compare
dbu
force-pushed
the
document-generated-columns
branch
from
285c6cc to
8ce7b31
Compare
i changed the branch and target of this merge request. |
while all relevant attributes are in the reference, it is not obvious how to work with generated columns.
this is an attempt to explain how to work with them with some examples.
this would answer #10706