-
Notifications
You must be signed in to change notification settings - Fork 686
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
PG16 - Add rules option to CREATE COLLATION #7185
Conversation
Codecov Report
@@ Coverage Diff @@
## main #7185 +/- ##
==========================================
- Coverage 93.19% 93.18% -0.02%
==========================================
Files 274 274
Lines 59322 59327 +5
==========================================
- Hits 55288 55285 -3
- Misses 4034 4042 +8 |
{ | ||
collicurules = TextDatumGetCString(datum); | ||
appendStringInfo(&collationNameDef, ", rules = %s", | ||
quote_literal_cstr(collicurules)); |
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.
the only thing that I'm not very sure is quote_literal_cstr. Is our test dealing with a rule that have escape chars?
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.
I couldn't quite understand your question - do we need another quote function here?
collicurules
should be quoted as part of the sql syntax.
a32f744
to
74971ad
Compare
Relevant PG commit: postgres/postgres@30a53b7 30a53b7
74971ad
to
d55f583
Compare
Relevant PG commit: postgres/postgres@30a53b7 30a53b7
Relevant PG commit:
postgres/postgres@30a53b7
30a53b7
#7138