Skip to content
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 error not reported anymore #9942

Closed
thomasLeclaire opened this issue May 10, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@thomasLeclaire
Copy link

commented May 10, 2019

  • Your databases: (e.x. MySQL, Postgres, MongoDB, …) : PG9.6 and PG11

  • Metabase version: (e.x. 0.19.3) 32.6 and 32.7. (everything ok in 32.5 and before)

  • Metabase hosting environment: (e.x. Mac app, Elastic Beanstalk, Docker, Heroku, Linux/Ubuntu 12) : docker

  • Metabase internal database: (e.x. H2 (default), MySQL, Postgres) : PG9.6

  • Repeatable steps to reproduce the issue
    When i create some custom SQL request with explicit error or syntax error, I don't have anymore the PG error reported.
    I get in place a "No results" answer, like if my request was good but give no result.

It's a huge regression.

@camsaul

This comment has been minimized.

Copy link
Member

commented May 13, 2019

Fixed by #9958. We will be releasing this as part of 0.32.8 later today.

@camsaul camsaul closed this May 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.