Update grantPermissions.js to use double quotes#711
Update grantPermissions.js to use double quotes#711CodeWithCJ merged 3 commits intoCodeWithCJ:mainfrom
Conversation
Summary of ChangesHello @toddejohnson, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refines the database permission granting mechanism by ensuring that the application user's role name is always properly quoted in SQL Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
The pull request adds double quotes to role names in SQL queries, which is a good step for correctness with case-sensitive names. However, it leaves a potential SQL injection vulnerability if the role name contains double quotes. My review includes a suggestion to properly escape the role name identifier, which also refactors the repetitive query calls into a more maintainable loop. This improves both security and code quality.
|
@toddejohnson Thanks a lot for your PR |
|
@toddejohnson this prevents to start the server. Using a fresh clone with commit 30c01a4 leads to errors:
|
|
oh no.. fixing it now. And I also saw OAuth is triggering before even DB migration and RLS are completed. So causing issue to first time deployment users. both will be fixed in next PR |
|
Perhaps I should switch back and let parameterized query handle the quoting and escaping? |
#710 (comment)