-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
PostgreSQL Errors in 3.2.3 vs. 3.1.1 #544
Comments
Having the same problem here on rails 3.2.18. |
Ok, i will try to fix this one too, today. |
This generates a GROUP BY in the statement, which did not happen in the previous version. With the above call as scope doc_scope i have a query like
The except is important, otherwise it would call
instead of
|
Ok, i will give it a try again. Thank you for your reply |
@Skulli , @vanboom can you try 3c9b170 ? I can't remove the group by since it resolve an issue with duplicate tags. In 3.1.1, tables with json,hstore columns were throwing an error when we used DISTINCT. I tried to fix it without breaking any tests. The one side effect with group by is that .count return a hash instead of integer. Let me know if that work for you so i can merge this to master and release v 3.2.4 |
Stupid question maybe, but how do i check that commit out?
did not work for me, commit/ref isnt known. |
@Skulli that correct, i just found a bug in the new code. I will update you once i push the changes. |
@Skulli : you will have to use 'Document.tagged_with("Test", any: 'distinct', wild: true)' . |
branch isnt pushed to origin yet, cant fetch it |
Note that it my fork and not this one. |
Sorry my bad. Seems to work now, not getting errors anymore and results are correct. |
You can use master now. |
And now from rubygems. |
Deprecated Taglist.parse and fix mbleigh#544
Hi,
I am not able to upgrade my Rails 4.0.2 app to acts-as-taggable-on 3.2.3.
Statements like these are causing PostgreSQL errors stating that the field used in ORDER or GROUP BY must appear in the SELECT list.
This is not happening for 3.1.1. Thanks for an amazing gem - please advise.
The text was updated successfully, but these errors were encountered: