bump for doctrine orm 2 -> 3, dbal 3 -> 4 through roave psr container

[cPintiuta]

No description provided.

[github-actions]

Qodana for PHP

82 new problems were found

Inspection name	Severity	Problems
Undefined method	🔶 Warning	62
Undefined class	🔶 Warning	12
Undefined namespace	🔶 Warning	8

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[alexmerlin]

Any idea why the uuid column has moved towards the end of the table, before the created column?
I guess Doctrine3 treats differently an entity when it extends another entity.

[cPintiuta]

Any idea why the uuid column has moved towards the end of the table, before the created column? I guess Doctrine3 treats differently an entity when it extends another entity.

Yes, because those columns comes from AbstractEntity, we need to declare this class with MappedSuperclass attribute, and if we want the uuid to appear first and timestamps last, we need to split them.

[cPintiuta]

@alexmerlin The problem from github actions is dot-data-fixtures who request doctrine/data-fixtures ^1.5. support for orm 3 and dbal 4 was added from 1.7.
We need to disquss how we aproach this to be sure that it works for api v4 and v5.

[alexmerlin]

the good: updated should get updated when the entity gets updated.
the bad: updated should stay null at entity creation.
@arhimede correct me if I'm wrong.

[arhimede]

is not a tragedy if at the creation time, created and updated fields have the samr value
if this simplify the code, we should keep it that way

[arhimede]

Second tought (or so)

We should not use ilogical stuff in database.
So at creation time, should be null the updated field