Closed babariviere closed 3 years ago
Hi!
This is a nice fix! I'll be happy to get this merged in.
Do you think you can add an entry in the CHANGELOG.md
file?
Also I'm not exactly sure on how to get this done for a fork but we need to run the tests for this! I'm 99% sure this will break the postgres tests for the query factory (since it's based on string matching). Any ideas?
Thanks! 😇
Hi!
This is a nice fix! I'll be happy to get this merged in. Do you think you can add an entry in the
CHANGELOG.md
file?Also I'm not exactly sure on how to get this done for a fork but we need to run the tests for this! I'm 99% sure this will break the postgres tests for the query factory (since it's based on string matching). Any ideas?
Thanks! 😇
Yes sorry, I should have been more careful about the tests. 😅 I have fixed it with my latest commit.
Awesome. Thank you for your contribution! ✨ The postgres provider could do with some love.
I've verified the tests are working and I'll merge now.
Changes will likely go with the next planned release v1.14.0
, which I'll put together in the next few days.
Fix an issue when using fields that are PostgreSQL keywords.
For example, this query will fail:
This PR patch this issue by escaping SQL fields in
UPDATE
query.