You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is caused by optimized bulk saving in DD.
Pimcore's default saving mechanism only saves one object at a time and if anything goes wrong, the transaction gets rolled back. However, when not using compatibility mode in DD, an optimized saving approach gets used. This executes only one INSERT ... ON DUPLICATE KEY UPDATE statement per table for a batch of 100 items. This is much faster. The disadvantage of this approach is that for new objects we first have to execute the INSERT statement to objects table because all the other tables need the object id. So while the INSERT INTO objects may have succeeded there may be a unique key violation in the object_store_Product or any other error. But this is not wrapped in a transaction because then we had deadlocks with this in the past. For this reason we have introduced some cleanup at the end of the import which deletes all orphaned entried from objects table at the end. But somehow this contained a condition for o_parentId IS NULL - but this is not true in your case, so I removed this condition in 3.5.50 so that the cleanup should now work in your case.
Hi
Sometimes during import data DD create records in Objects table with empty type column.
Why ?
The text was updated successfully, but these errors were encountered: