-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Postgres: Safely escape strings in nested objects #5855
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5855 +/- ##
==========================================
- Coverage 93.69% 93.67% -0.03%
==========================================
Files 150 150
Lines 10616 10613 -3
==========================================
- Hits 9947 9942 -5
- Misses 669 671 +2
Continue to review full report at Codecov.
|
Hypothetically, the first half of the PostgreSQL adapter could be replaced with much nicer code, because you ignore that |
I’ve been meaning to do a rewrite at some point. The PG Adapter is ~2500 lines. I didn’t know it supported nested natively and custom types If you could do an initial PR, I can help out. |
I'm afraid I'm not the right person to rewrite it, I know almost nothing about the code actual purpose, as I do not even use parse-server myself. But if you have any questions, I will answer ;) And besides, you'd want to rewrite the whole thing, not a small part of it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me. LGTM!
* Postgres: Safely handle string in nested objects * fix failing tests
Superced: #5336
Removed existing error message and prevent query from breaking using pg-promise built in formatting engine