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

Fix reversed logic for native UUID detection #297

Merged
merged 2 commits into from Dec 20, 2017
Merged

Fix reversed logic for native UUID detection #297

merged 2 commits into from Dec 20, 2017

Conversation

msheakoski
Copy link
Contributor

I know that you are working on #280 but for current users of Enqueue, it is very inconvenient to manually edit the package to fix this bug and it also makes deploying/CI difficult. Can you release this as 0.8.12?

@@ -170,7 +170,7 @@ public function createDataBaseTable()
return;
}

if ($this->getDbalConnection()->getDatabasePlatform()->hasNativeGuidType()) {
if (!$this->getDbalConnection()->getDatabasePlatform()->hasNativeGuidType()) {
Copy link
Member

Choose a reason for hiding this comment

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

I guess this change would break MySql. Could you remove it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have removed the check. That check should not be necessary in the first place because Doctrine will use the UUID column type if available, otherwise fall back to VARCHAR. One thing to take note of is that it may be necessary to add some code to #280 to detect and migrate the column type if you decide to merge that PR.

@makasim makasim merged commit f8ac4eb into php-enqueue:master Dec 20, 2017
ASKozienko pushed a commit that referenced this pull request Nov 2, 2018
Fix reversed logic for native UUID detection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants