Not working with PostgreSQL #4
Milestone
Comments
|
This indeed is a statement which needs to be adjusted to fit all supported databases. To be fixed |
|
I implemented postgres queries and added a readme.md which I guessed from the code: |
dregad
added a commit
that referenced
this issue
Sep 8, 2019
The query is a lot more complex than it needs to be. All of the ratings data aggregated with outer joins is not used anywhere in the plugin's code, so we might as well remove it. This removes the MySQL-specific IFNULL() function that was causing compatibility issues with PostgreSQL. Fixes #4
dregad
added a commit
that referenced
this issue
Sep 8, 2019
Until now, saving a user's vote was relying on MySQL's non-standard "UPSERT" statement (INSERT INTO ... ON DUPLICATE KEY UPDATE ...). This prevents using the plugin with other RDBMS. To avoid this, we always delete the old vote, and insert a new record with the user's new stance. Fixes #4
dregad
added a commit
to dregad/GaugeSupport
that referenced
this issue
Sep 9, 2019
The query is a lot more complex than it needs to be. All of the ratings data aggregated with outer joins is not used anywhere in the plugin's code, so we might as well remove it. This removes the MySQL-specific IFNULL() function that was causing compatibility issues with PostgreSQL. Fixes mantisbt-plugins#4
dregad
added a commit
to dregad/GaugeSupport
that referenced
this issue
Sep 9, 2019
Until now, saving a user's vote was relying on MySQL's non-standard "UPSERT" statement (INSERT INTO ... ON DUPLICATE KEY UPDATE ...). This prevents using the plugin with other RDBMS. To avoid this, we always delete the old vote, and insert a new record with the user's new stance. Fixes mantisbt-plugins#4
dregad
added a commit
that referenced
this issue
Sep 9, 2019
Until now, saving a user's vote was relying on MySQL's non-standard "UPSERT" statement (INSERT INTO ... ON DUPLICATE KEY UPDATE ...). This prevents using the plugin with other RDBMS. To avoid this, we always delete the old vote first, and then insert a new record with the user's new stance. Fixes #4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Clicking on the "Issue Support Ranking" Button just gives an error page:
#-2: ERROR: syntax error at or near "sql_mode"
LINE 1: SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,'ONLY_FULL_GR...
^ für die Abfrage: SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,'ONLY_FULL_GROUP_BY','')).
The text was updated successfully, but these errors were encountered: