Closed HKayani closed 1 year ago
I had this same problem. It's because ONLY_FULL_GROUP_BY is enabled by default in MySQL 5.7.5 and later. See https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_only_full_group_by
So you should disable this if you can.
Another possibility that I haven't tried is setting useNonStandardSql
to false.
As bobcat said, while this has long been a bug the useNonStandardSql
option was added as a work around. Prism v4 will not have this flaw and is in dev now.
Describe the bug When using
/pr near
no results are returned and upon inspection of the console, I see a SQL syntax error.To Reproduce Steps to reproduce the behavior: Using Prism 3.6.0 (all) in a 1.19.3 Purpur server instance, I broke some stone blocks I placed under my feet using World Edit and attempted to check that it's being registered with Prism using
/pr near
. It wasn't returning any results, not even showing an error had occurred.Expected behavior I expected the command to return some log of the recently broken stone blocks. I was in creative and also OP so I didn't pay much attention at first, then realized after checking the server log.
Screenshots No screenshots but here's the log of the error from the console.
Server (please complete the following information):
Additional context I have 9 other plugins installed: