Skip to content
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.

GET /dashboards throws 500 error #44

Closed
danryan opened this issue Aug 3, 2012 · 4 comments
Closed

GET /dashboards throws 500 error #44

danryan opened this issue Aug 3, 2012 · 4 comments

Comments

@danryan
Copy link

danryan commented Aug 3, 2012

The error in gist form: https://gist.github.com/b83b3b3243f5f6f5757d.

I'll see if I can't figure out what's wrong and hopefully send a pull request.

@obfuscurity
Copy link
Owner

I don't grok this at all. Cannot reproduce.

There is no need to GROUP BY dashboards.uuid, afaict. Very strange. I don't think there's any harm in adding it to the group(), but I'd like to understand why it think this is needed.

Can you paste or gist your bundle output? I'd just like to compare versions. And of course, make sure you're running against HEAD.

@danryan
Copy link
Author

danryan commented Aug 3, 2012

Gist of bundle command is here: https://gist.github.com/3250132. It works locally but fails on Heroku. Confirmed I am running latest master.

@danryan
Copy link
Author

danryan commented Aug 3, 2012

Issue was PEBCAK. While I had run heroku addons:add heroku-postgresql:dev -r $DEPLOY, DATABASE_URL was still set to the default shared Postgres database. There must be an issue with whatever version of Postgres is running on the older databases. The /dashboards view worked flawlessly when I changed DATABASE_URL to the new Postgres dev DB.

@obfuscurity
Copy link
Owner

I wouldn't blame yourself. This is good stuff to know, thanks. ✨

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants