Navigation Menu

Skip to content
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

Create doctrine messenger transport table on send #33559

Closed
wants to merge 2 commits into from
Closed

Create doctrine messenger transport table on send #33559

wants to merge 2 commits into from

Conversation

jrjohnson
Copy link
Contributor

Q A
Branch? 4.3
Bug fix? yes
New feature? no
Deprecations? no
License MIT
Doc PR aligns with existing docs

Create doctrine messenger transport table on send just like it is created on get to match the
documentation and expectations for auto_setup.

Existing documentation at https://symfony.com/doc/current/messenger.html#doctrine-transport includes:

auto_setup Whether the table should be created automatically during send / get. true

I think this is correct as I'd expect the table to be autocreated on set before get.

Tests are added here, but they don't actually fail correctly and I'm not sure why. I wonder if sqlite or doctrine is auto creating this table on insert when it isn't present. Maybe it's something else that you will see that I'm missing.

Create this table on send just like it is created on get to match the
documentation and expectations for auto_setup.
Copy link
Member

@Tobion Tobion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you delete the wrong comment in

please?

auto-setup happens on get and send
@jrjohnson
Copy link
Contributor Author

@Tobion, yes. Deleted!

@bendavies
Copy link
Contributor

superseded in #32308 really (which i've not managed to finish off)

@jrjohnson
Copy link
Contributor Author

jrjohnson commented Sep 12, 2019

Oh good @bendavies I was considering that as a next step, I'm glad you're already looking into it. Seems like this should still be merged as a bug fix for release to be enhanced when you finish up that PR?

@nicolas-grekas nicolas-grekas added this to the 4.3 milestone Sep 12, 2019
@fabpot
Copy link
Member

fabpot commented Sep 25, 2019

Closing in favor of #32308

@fabpot fabpot closed this Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants