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
From the terminal, run ./bin/console messenger:consume
The text was updated successfully, but these errors were encountered:
dlegatt
changed the title
Messenger Doctrine Transport not compatible with SQL Server
[Messenger] Doctrine Transport not compatible with SQL Server
Jul 17, 2019
… placeholders for sqlsrv compatibility (David Legatt)
This PR was squashed before being merged into the 4.3 branch (closes#32836).
Discussion
----------
[Messenger] Removed named parameters and replaced with `?` placeholders for sqlsrv compatibility
| Q | A
| ------------- | ---
| Branch? | 4.3
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #32585
| License | MIT
| Doc PR |
I edited the Doctrine Transport Connection class to use `?` placeholders in the query builder instead of named repositories as this resulted in a compatibility issue with SQL Server.
Commits
-------
fc0e4ba [Messenger] Removed named parameters and replaced with `?` placeholders for sqlsrv compatibility
Symfony version(s) affected: 4.3.2
Description
Doctrine DBAL throws the following exception when using messenger with the Doctrine transport and a SQL Server database.
How to reproduce
Create a new symfony project and install messenger:
Configure
.env
for the database DSN and messenger transport DSNConfigure
messenger.yaml
Configure
doctrine.yaml
From the terminal, run
./bin/console messenger:consume
The text was updated successfully, but these errors were encountered: