-
Notifications
You must be signed in to change notification settings - Fork 2
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
backticks don't work in postgres for database health check #15
Comments
I'm new to github actions, but if you're able to, can you add postgres, sqlite and mysql/mariadb to the action? I don't think it's working for postgres, and now that postgres is the default database when running
it's even more important than this bundle work with it. Thanks. |
I agree that it is good to fix it. The question is what a proper fix would be, it's not completely straightforward as you say. Suggestions are welcome. |
If all we're doing is testing that the database is connected and running, I think
is the fastest. It also saves the time of looking for the tables, etc. |
Alternatively, we could allow the user to define their own query, defaulting to "Select 1". That way, they could check a particular table, for example, or even a certain number of rows, or that all migrations have been executed, etc. But I'm looking at using this for something that's going to be checking uptime status every few seconds, so would like it to be as fast as possible and with as little overhead as possible. |
With If we can configure the query needed then the bundle can satisfy both our needs I think. |
Can you tweak the bundle so that postgres users can use it? I like the idea of a configurable query, but all my bundle experience is Symfony 6.1+, which extends AbstractBundle. Much easier to configure. |
I think this works in MySQL, but not postgres:
when I remove the backticks, it works as expected for me, running postgres 16.
I thought doctrine had some sort of escape method that was database-specific, but I can't find it now.
FWIW, the table is doctrine_migrations_table
The text was updated successfully, but these errors were encountered: