-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Database error while creating products without name #148
Comments
lruozzi9
added a commit
that referenced
this issue
Sep 7, 2022
lruozzi9
added a commit
that referenced
this issue
Sep 7, 2022
4 tasks
lruozzi9
added a commit
that referenced
this issue
Sep 8, 2022
lruozzi9
added a commit
that referenced
this issue
Sep 8, 2022
Here there are a couple of solutions that we can try: |
mmenozzi
added a commit
that referenced
this issue
Sep 1, 2023
mmenozzi
added a commit
that referenced
this issue
Sep 5, 2023
mmenozzi
added a commit
that referenced
this issue
Sep 5, 2023
mmenozzi
added a commit
that referenced
this issue
Sep 5, 2023
mmenozzi
added a commit
that referenced
this issue
Sep 5, 2023
mmenozzi
added a commit
that referenced
this issue
Sep 5, 2023
mmenozzi
added a commit
that referenced
this issue
Sep 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
It could happen that, while importing products from Akeneo, the attribute used as the name for the product is empty. If this is the case, the importer will not generate any error because the name property on ProductTranslation is nullable. Still, when it tries to persist the product on DB it causes an Integrity constraint violation due to the not nullable constraint on the name column.
Expected behavior
IMHO the plugin should check for the name consistency before trying to persist them on DB. If it is not valid it should throw a PHP exception so that it could be handled by the importer by marking the product as not imported without blocking the entire queue.
The text was updated successfully, but these errors were encountered: