-
Notifications
You must be signed in to change notification settings - Fork 129
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
DBAL-based queue constantly raises SQL-level errors #251
Comments
Chose the one you think is best. The reasoning seems solid. |
Ocramius
added a commit
to Ocramius/bernard
that referenced
this issue
Aug 22, 2016
…eady existing repositories
Ocramius
added a commit
to Ocramius/bernard
that referenced
this issue
Aug 22, 2016
… with constraint violation exceptions
Ocramius
added a commit
to Ocramius/bernard
that referenced
this issue
Aug 22, 2016
Ocramius
added a commit
to Ocramius/bernard
that referenced
this issue
Aug 22, 2016
Provided patch in #252. Patch is against |
henrikbjorn
added a commit
that referenced
this issue
Dec 15, 2016
…creation Fix #251: dbal driver - safe queue creation
henrikbjorn
added a commit
that referenced
this issue
Dec 16, 2016
henrikbjorn
added a commit
that referenced
this issue
Dec 29, 2016
…-creation' into doctrine-safe-queue-creation
acrobat
pushed a commit
to acrobat/bernard
that referenced
this issue
Jul 9, 2017
…eady existing repositories
acrobat
pushed a commit
to acrobat/bernard
that referenced
this issue
Jul 9, 2017
… with constraint violation exceptions
acrobat
pushed a commit
to acrobat/bernard
that referenced
this issue
Jul 9, 2017
acrobat
pushed a commit
to acrobat/bernard
that referenced
this issue
Jul 9, 2017
@acrobat I can see you worked on this. Are you planning to rebase and resubmit it? |
Uhm let me see if I can dig this up again 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per
bernard/src/Driver/DoctrineDriver.php
Lines 40 to 45 in 3b78158
INSERT
statements that will fail.While this seems to be acceptable at first, some database engines mark transactions with failed SQL statements as "failed transactions", rendering the entire DB connection unusable.
Few things to be done here
INSERT IGNORE
(not always supported, therefore not going there)SELECT
and then anINSERT
(relatively low-risk, since queues don't get destroyed/recreated often)I'll provide a patch for this today, if this seems reasonable.
The text was updated successfully, but these errors were encountered: