Feature Request
| Q |
A |
| New Feature |
yes |
| RFC |
yes |
| BC Break |
yes |
Summary
Hi, I want to ask, is there some ongoing discussion about ORM 3.0 and possible BC breaks and features? Because I have an ideas and I don't know if it has been already discussed.
Nullable columns
Will be a default value for nullable column the PHP ? or |null instead of false? It would be a huge time saver, since I barely add something in #[Column] attribute and I think that all my properties match the PHP value, and it's like 60+ complex entities. I know you didn't want this BC break in 2.x, so is it for sure it will be in 3.0?
Rearranging columns
Another great feature would be column rearranging, so ORM would keep 1:1 column order with database, because as projects gets older and there is a lot of columns in tables, if someone wants to add something like $externalId right after the $id property, and in the database it's always at the end, or we need to manually edit and add queries, what is also time consuming. Another thing is that if schema is generated again for some reason in new app instance, the column order matches those in entities, but older database has that column at the end.
Feature Request
Summary
Hi, I want to ask, is there some ongoing discussion about ORM 3.0 and possible BC breaks and features? Because I have an ideas and I don't know if it has been already discussed.
Nullable columns
Will be a default value for nullable column the PHP
?or|nullinstead of false? It would be a huge time saver, since I barely add something in#[Column]attribute and I think that all my properties match the PHP value, and it's like 60+ complex entities. I know you didn't want this BC break in 2.x, so is it for sure it will be in 3.0?Rearranging columns
Another great feature would be column rearranging, so ORM would keep 1:1 column order with database, because as projects gets older and there is a lot of columns in tables, if someone wants to add something like
$externalIdright after the$idproperty, and in the database it's always at the end, or we need to manually edit and add queries, what is also time consuming. Another thing is that if schema is generated again for some reason in new app instance, the column order matches those in entities, but older database has that column at the end.