When $magentoAttribute and $akeneoAttribute parameters have the same value with different CamelCase the first line just deletes everything and you have no data for $options
The possible solution is making the query sensitive for CamelCase
for example:
$connection->delete($tmpTable, ['BINARY attribute = ?' => $magentoAttribute]);
and after getting options delete it from the $tmpTable table in the database to prevent duplicates
Environment and configuration
Steps to reproduce
Expected result
Actual result
There is a bug with MySQL query in the file:
vendor/akeneo/module-magento2-connector-community/Job/Option.php
method mapOptionsThere are 2 lines 1 .
$connection->delete($tmpTable, ['attribute = ?' => $magentoAttribute]);
$options = $connection->select()->from($tmpTable)->where('attribute = ?', $akeneoAttribute);
When $magentoAttribute and $akeneoAttribute parameters have the same value with different CamelCase the first line just deletes everything and you have no data for $options
The possible solution is making the query sensitive for CamelCase for example:
$connection->delete($tmpTable, ['BINARY attribute = ?' => $magentoAttribute]);
and after getting options delete it from the $tmpTable table in the database to prevent duplicates