-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
MySQL Error #8
Comments
This is definitely coming from the Similar plugin SQL? Related: |
Here is the rest of the error, where I'm seeing the Similar plugin referenced. I ended up commenting out the Similar template code for now, and all is running well. I'll check out the link you provided to see what else may be going on.
|
This is related to counting without grouping. |
I am having this issue also.... i am relatively new to craft templating. is there a simple work around for this? |
@khalwat did my code provided in https://github.com/nystudio107/craft-similar/issues/8#issuecomment-411947586 help at all? Do you think this is something that would be addressed in the plugin, or are you thinking it's a fix that happens on the server? |
@AdamChlan That link doesn't seem to work? |
@khalwat hmm, was just referencing my comment with additional error code. Here you go: |
I ran into the same issue. It seems a possible fix, or at least a workaround, is to expand the groupBy statements as @joshuabaker was suggesting in #10, but then also in the sub-query. So in
and
For me this sorted SQL errors for entries with and without relations. Om a side note, if it can be of any use, I also ran into a case where the SQL-query returned a record of a null-values that were passed on to
|
@svale that's fantastic... do you want to PR it? |
Sure. I waited with a PR because I wasn't sure this was the best way to go about it. But as long as it works... :-) I'll get around to it when I'm back at the office over the weekend. |
Fixed in https://github.com/nystudio107/craft-similar/releases/tag/1.0.4 Thanks to @svale |
We are seeing a MySQL error on our production environment, but not elsewhere. Production MySQL is 5.7.22, which is higher than our others. Here is what we are seeing:
The text was updated successfully, but these errors were encountered: