Postgres Error with "SELECT DISTINCT, ORDER BY" #128
Labels
Comments
|
+1 |
tzar
added a commit
to tzar/ancestry
that referenced
this issue
May 7, 2013
Move case statement into part of the select. Fixes stefankroes#128
|
Ignore the above commit, creates issues with some other cases |
tzar
added a commit
to tzar/ancestry
that referenced
this issue
May 7, 2013
Amendment to last fix for stefankroes#128. It doesn't feel clean at all, but it makes it work for my use case at least.
|
This would probably be fixed by #131, right? in that case I would like to close this issue and use that solution |
|
@StefanH ah yeah, it would be fixed by that. Does mysql need the case statement still though? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Problem is the "order by (case.." statement which is used in arrange-method for example.
If i query an ancestry Class like
(i know the statement doest make much sense but just an example).
It will throw following error when using postgres:
It would be correct if the case statement is put into the select and aliased and then accessed in the ORDER BY statement.
The text was updated successfully, but these errors were encountered: