PostgreSQL orderBy method adds fields it doesn't need to, leading to fatal errors when the result is used as an insert subquery

The Needs Review Queue Bot → tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

Problem with the bot disregard #75

The last submitted patch, 73: 2057693-73.patch, failed testing. View results →

Back to RTBC.

The last submitted patch, 73: 2057693-73.patch, failed testing. View results →

Back to RTBC

I think #61 addresses #29, removing that from the issue summary

Issue credits

I did some debugging of this, and was able to produce an entity query that errors on postgres with the following interdiff.

Is this something we should be supporting or is postgres stricter on that front? It works with MySQL.

I note this fails in HEAD too, so I assume 'not supported' on postgres (or rather - not valid SQL full stop, MySQL is just more tolerant).

Either way, this no longer applies - NW for that