- Issue created by @Chi
- Status changed to Needs review
almost 2 years ago 1:16pm 6 May 2023 - last update
almost 2 years ago 29,379 pass - last update
almost 2 years ago 29,379 pass - Status changed to Needs work
almost 2 years ago 9:57pm 6 May 2023 - πΊπΈUnited States smustgrave
Can the issue summary be updated to include the proposed solution and any api changes needed?
Also can a test be written to show the issue?
- Status changed to Needs review
almost 2 years ago 9:05am 8 May 2023 - last update
almost 2 years ago 29,381 pass - last update
almost 2 years ago 29,381 pass - π³π±Netherlands arantxio Dordrecht
I've created two patches one with the change and one without and added one extra test to check the added functionality.
- last update
almost 2 years ago 29,360 pass, 2 fail - last update
almost 2 years ago 29,381 pass - last update
almost 2 years ago 29,381 pass - last update
almost 2 years ago 29,381 pass - Status changed to RTBC
almost 2 years ago 11:03am 8 May 2023 - π³π±Netherlands daffie
All code changes look good to me.
The patch with the added test fails without the fix.
I have updated the IS.
For me it is RTBC. - last update
almost 2 years ago 29,381 pass - last update
almost 2 years ago 29,389 pass - last update
almost 2 years ago 29,388 pass, 1 fail - last update
almost 2 years ago 29,389 pass - last update
almost 2 years ago 29,389 pass - last update
almost 2 years ago 29,389 pass - last update
almost 2 years ago 29,388 pass, 1 fail - last update
almost 2 years ago 29,396 pass - last update
almost 2 years ago 29,400 pass - last update
almost 2 years ago 29,400 pass - last update
almost 2 years ago 29,400 pass - last update
almost 2 years ago 29,401 pass - last update
almost 2 years ago 29,405 pass, 4 fail - last update
almost 2 years ago 29,416 pass - last update
almost 2 years ago 29,419 pass - last update
almost 2 years ago 29,419 pass, 2 fail - last update
almost 2 years ago 29,421 pass 51:43 45:54 Running- last update
over 1 year ago 29,430 pass - last update
over 1 year ago 29,431 pass - last update
over 1 year ago 29,431 pass - last update
over 1 year ago 29,437 pass - last update
over 1 year ago 29,437 pass - last update
over 1 year ago 29,437 pass - last update
over 1 year ago 29,442 pass - last update
over 1 year ago 29,444 pass - last update
over 1 year ago 29,444 pass - last update
over 1 year ago 29,444 pass - last update
over 1 year ago 29,440 pass - last update
over 1 year ago 29,440 pass - last update
over 1 year ago 29,443 pass - last update
over 1 year ago 29,445 pass - last update
over 1 year ago 29,447 pass - last update
over 1 year ago 29,447 pass - last update
over 1 year ago 29,447 pass - Status changed to Needs work
over 1 year ago 7:28am 20 July 2023 - π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
This no longer applies to 11.x
Fine to self RTBC after re-roll
- Status changed to RTBC
over 1 year ago 8:48am 20 July 2023 - last update
over 1 year ago 29,824 pass, 1 fail - last update
over 1 year ago 29,827 pass The last submitted patch, 8: 3358609-8-pass.patch, failed testing. View results β
- last update
over 1 year ago 29,878 pass - Status changed to Needs review
over 1 year ago 6:49am 12 September 2023 - π³π΄Norway steinmb
Mmmm, seems to me like a unrelated random fail. Let's try this one more time.
- last update
over 1 year ago 30,149 pass - last update
over 1 year ago 30,149 pass - Status changed to RTBC
over 1 year ago 8:34am 12 September 2023 - last update
over 1 year ago 30,158 pass - last update
over 1 year ago 30,162 pass - πΈπ°Slovakia poker10
+1 to this fix, looks good to me.
We are already quoting the name of the field when creating it:
protected function createFieldSql($name, $spec) { // The PostgreSQL server converts names into lowercase, unless quoted. $sql = '"' . $name . '" ' . $spec['pgsql_type']; ... }
So we should quote the name in the great than zero check as well.
I have reviewed the patch and it seems like it contains a copy-pasted comment:
+ // First create the table with just a serial column.
I would say we should remove this comment, because it is not relevant here. Not changing the issue status, as I think this is a minor thing and probably could be fixed also on commit. Other that that, the patch looks good and it is working for me. Thanks!
- last update
over 1 year ago 30,164 pass - last update
over 1 year ago 30,169 pass - last update
over 1 year ago 30,169 pass - last update
over 1 year ago 30,206 pass - last update
over 1 year ago 30,364 pass - last update
over 1 year ago 30,366 pass - last update
over 1 year ago 30,359 pass, 2 fail - last update
over 1 year ago 30,363 pass 21:45 20:31 Running- last update
over 1 year ago 30,378 pass - last update
over 1 year ago 30,381 pass, 2 fail - last update
over 1 year ago 30,393 pass - last update
over 1 year ago 30,398 pass - last update
over 1 year ago 30,398 pass - last update
over 1 year ago 30,414 pass 6:44 3:51 Running- last update
over 1 year ago 30,426 pass - last update
over 1 year ago 30,427 pass - last update
over 1 year ago 30,437 pass - last update
over 1 year ago 30,439 pass - last update
over 1 year ago 30,465 pass - last update
over 1 year ago 30,482 pass - last update
over 1 year ago 30,484 pass - last update
over 1 year ago 30,486 pass, 1 fail - last update
over 1 year ago 30,487 pass - last update
over 1 year ago 30,511 pass - last update
over 1 year ago 30,517 pass - Status changed to Needs work
over 1 year ago 12:02am 11 November 2023 The Needs Review Queue Bot β tested this issue.
While you are making the above changes, we recommend that you convert this patch to a merge request β . Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)
- Merge request !5404#3358609 - PostgeSQL escape column name in field constraint β (Open) created by arantxio
- Status changed to Needs review
over 1 year ago 8:00am 15 November 2023 - π³π±Netherlands arantxio Dordrecht
I've created the branch and made a MR.
In the MR I've removed the comment mentioned by @poker10 in #12.
- Status changed to RTBC
over 1 year ago 11:46am 15 November 2023 - last update
over 1 year ago 30,553 pass - last update
over 1 year ago 30,574 pass - πΊπΈUnited States xjm
Please remember to hide patch files when converting them to an MR. Thanks!
- Status changed to Needs work
over 1 year ago 9:30pm 17 November 2023 - πΊπΈUnited States xjm
I posted some small coding standards fix suggestions on the MR. Thanks!
- Status changed to Needs review
over 1 year ago 12:54pm 20 November 2023 - π³π±Netherlands arantxio Dordrecht
@xjm Thanks for the feedback en hiding the patch file, i've forgotten about that.
I've updated the MR with the suggested fixes. - Status changed to RTBC
over 1 year ago 1:02pm 20 November 2023 - π³π±Netherlands daffie
+1 for RTBC
All remarks of @xjm have been addressed.
Back to RTBC. - π³πΏNew Zealand quietone
I'm triaging RTBC issues β . I read the IS and the comments. I didn't find any unanswered questions or other work to do. This is also approved by the Database API maintainer.
Leaving at RTBC.
- Status changed to Needs work
about 1 year ago 3:36am 22 December 2023 - π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
Needs another reroll, please ping me when done, fine to self RTBC - conflicts with π Fix PostgeSQL column name escaping in field constraints RTBC
- First commit to issue fork.
- Status changed to RTBC
about 1 year ago 2:49pm 7 January 2024 - π¬π·Greece dimitriskr
Rebased to latest 11.x
I messed up the commits but all changes are there and postgresql tests pass - πΈπ°Slovakia poker10
The reroll looks good. Compared the MR before and after and changes are the same:
https://git.drupalcode.org/project/drupal/-/merge_requests/5404/diffs?di...
https://git.drupalcode.org/project/drupal/-/merge_requests/5404/diffs?di... - Status changed to Downport
about 1 year ago 9:46pm 7 January 2024 - π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
Committed to 11.x
Needs re-roll for 10.2.x
-
larowlan β
committed 28503b73 on 11.x
Issue #3358609 by Arantxio, daffie, Chi, xjm: Fix PostgeSQL column name...
-
larowlan β
committed 28503b73 on 11.x
- Status changed to RTBC
about 1 year ago 2:37pm 8 January 2024 -
longwave β
committed e891703e on 10.2.x
Issue #3358609 by Arantxio, daffie, Chi, larowlan, xjm: Fix PostgeSQL...
-
longwave β
committed e891703e on 10.2.x
- Status changed to Fixed
about 1 year ago 6:25pm 12 January 2024 Automatically closed - issue fixed for 2 weeks with no activity.