-
Notifications
You must be signed in to change notification settings - Fork 264
Syntax error when using non-standard DB names #5
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
Comments
Agreed. Would you perhaps like to send a pull request :)? |
I'm sorry, but after further investigation I suggest that we don't do this - it forces everyone to use quotes throughout, see e.g. https://stackoverflow.com/a/6331658/258772. This is not a good thing. What do you think? |
A quick test didn't show the problem described in the SO answer.
I think the problem is that postgresql converts names without quotes to lowercase, so using quotes might be unexpected for the user. I don't really know enough about postgres to say if this has further implications. |
Adding quotes around the names in docker-compose actually works for me, looks like they are passed to the script.
|
Perfect, now you hit the mark 👍 - it's a documentation issue after all. I'll amend the readme accordingly. |
And many thanks for the thorough tests, much appreciated! |
Please review #7, do you agree this is sufficient? |
Fixed with #7 |
When using a non standard DB name, e.g.
test-db
, a syntax error is thrown.This could be avoided by using double quotes around the variables in the SQL statements.
The text was updated successfully, but these errors were encountered: