IBX-8562: Fixed flooding content attributes table with duplicates

[Nattfarinn]

+ IBX-8492: Fixed replacing only field of Content Type with virtual field

Question	Answer
JIRA issue	IBX-8562, IBX-8492
Type	bug
Target Ibexa version	v3.3
BC breaks	no

Checklist:

• Provided PR description.
• Tested the solution manually.
• Checked that target branch is set correctly (master for features, the oldest supported for bugs).
• Ran PHP CS Fixer for new PHP code (use $ composer fix-cs).
• Asked for a review (ping @ezsystems/engineering-team).

[Steveb-p]

Given how the issue comes up when multiple layers interact with each other, this almost requires tests - either adjustment of already present ones, or new ones.

I'd accept this only with an explanation why this works, ideally with a promise of tests being added at least to 4.6 to show the issue in the new testing framework.

[mnocon]

The JIRA ticket mentions a SQL script to remove the duplicated entries - if we decide to create one please let us (the Knowledge Team) know, we will have to document it in the update doc

[micszo]

Current status of retests.

https://issues.ibexa.co/browse/IBX-8562
OK

https://issues.ibexa.co/browse/IBX-8492
Content view works but editing item causes error:
(under verification by @Nattfarinn)

[eWert-Online]

Hello 👋

since the creation of this PR, our clients database grew an additional 5 million rows and 2 GB in disk size.
Please provide a fix for this issue as fast as possible.

Thank you!

[micszo]

Retest status: on v3.3 404 persists when editing item with only field replaced.

[alongosz]

I'm still missing some coverage on integration level, with database.
You should be able to query database via tests by getting \Doctrine\DBAL\Connection service from the test container (it's already exposed).
// for 4.6

[micszo]

OK from my side now.

[eWert-Online]

Hi 🙂

we now have ~10 million duplicates in our table and the database grew around 3GB in disk size.

Since a few days, the production database is throwing error messages (SQLSTATE[HY000]: General error: 1114 The table 'ezcontentobject_attribute' is full).
Some SQL queries fail with Fatal Error: Allowed memory size exhausted.

...but sure... take your time discussing what kind of null check you want to do. Nothing to worry about!

[adamwojs]

Hi @eWert-Online!

First of all my apologies for the situation. I understand your frustration but I would like to ensure you that we are aware of importance of this patch and we are actively working on providing the solution.

Unfortunately, Github does not give a full visibility of our intense activities behind the scenes. Currently proposed changes are going through Quality Assurance process. As soon as we will be ready we will do the 3.3.40 and 4.6.10 release.

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud