-
Notifications
You must be signed in to change notification settings - Fork 19
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
PostgresError #23
Comments
I fixed it by adding a line ( query.delete :order ) in the page method, agree with that?:
|
That is something to take up with DM core, I would not go explicitly deleting :order, because it works fine with other RDMS |
Ok, anyway removing the option :order will not affect the collection itself, I'm removing the :order only for the aggregate function "count", because the order hasn't any sense for an aggregate function. |
ah, right sorry didnt look closely enough lol its probably fine then |
Cool cool I committed the change :D thanks. Your totally right though I just had read it wrong originally when I scanned over the issue |
good man! now I'm going to remove the monkey patch :) |
hi visionmedia, it's been a long time since my last message and untill now I didn't deployed the app to heroku and now I'm realizing that the gem still throwing the same exception, this is because you removed the :order option to the 'options' instead of to the 'query' as I wrote in my second message. |
My bad! typo, 1.0.1 fixes this |
I'm getting this when running on Heroku because of Postgres database:
PostgresError - ERROR: column "medium.sector" must appear in the GROUP BY clause or be used in an aggregate function
Query: SELECT COUNT(*) FROM "medium" ORDER BY "sector" DESC:
BTW: running it locally with sqlite3 is working like a charm, thanks for the gem!
The text was updated successfully, but these errors were encountered: