-
Notifications
You must be signed in to change notification settings - Fork 73
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
Error while activating plugin wp-statistics #115
Comments
i already found a fix for me, i made the bigint detection not upper/lower case dependent |
the plugin still gets some errors:
|
I tried to format it a bit more readable to find out what is going wrong. the conversion makes absolutely no sense to me: original mysql:
now the postgres converted sql:
first of all, why does it select "domain" twice? the original sql query only had 2 colums then why is the FROM after ORDER BY? then why does the GROUP BY not use "domain" but copy&paste the whole expression again? and then lastly, where did the DESC go in ORDER BY and where did the LIMIT go? |
That's a heck of a query, but looks like an issue with the group by rewriting in the select rewriter. We'll need to add this to the test suite |
There's a good explanation of why this is happening here.
This method probably needs to be updated as it doesn't detect this case properly. Additionally where Went is a mystery for the moment |
another failed query from the same plugin:
I try to translate my german error message: ERROR: there is no unique constraint or exclusion constraint, which matches the ON CONFLICT definition I will check if the table creation was missing a unique or so.... |
While yes it would be expected that "visit" needs to be a key which supports conflicts, in your example the plugin incorrectly rewrote the duplicate value. It's missing the + 1 |
This plugin is tricky, I started capturing example failing tests here: #136 |
WP Version: 6.5
PG4WP Version: latest master
The text was updated successfully, but these errors were encountered: