Enabled capitzalized table names for sequence reset

[jaads]

Closes #19817

When looking up the auto increment sequence name for a table which is capitalized, PostgreSQL throwed an error saying relation xy does not exist. The table name needed explicit quotes, otherwise PostgreSQL used a lowercase variant of the table name automatically and couldn't resolve some (internal) relationship (I guess).

So the table name for the pg_get_serial_sequence function call, which need to be passed as string, needed to be escaped.

In addition of just escaping the value to the pg_get_serial_sequence, now all the values get passed as parameters to the database (using Knex's ?) and all identifiers now get escaped via Knex using ??.

This is an example of how the statement now looks:

WITH sequence_infos AS (SELECT pg_get_serial_sequence($1, $2) AS seq_name, MAX("id") as max_val FROM "articles") SELECT SETVAL(seq_name, max_val) FROM sequence_infos; ["articles", id]

I also tested with a capitalized column name, but this worked fine without the explicit double quotes like it was needed for the table name.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0c5b7a4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@directus/api	Minor
directus	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[jaads]

shout out to @paescuj for the support 🎉

[paescuj]

LGTM! ❤️

[azrikahar]

LGTM! Out of curiosity, tried to looked up more info from the official docs regarding this and they do seem to support the actual fix and reasoning behind the quotes around table name, but not needed for column name.

pg_get_serial_sequence ( table text, column text ) → text
Because the first parameter potentially contains both schema and table names, it is parsed per usual SQL rules, meaning it is lower-cased by default. The second parameter, being just a column name, is treated literally and so has its case preserved.
Link to above reference

Quoting an identifier also makes it case-sensitive, whereas unquoted names are always folded to lower case. For example, the identifiers FOO, foo, and "foo" are considered the same by PostgreSQL, but "Foo" and "FOO" are different from these three and each other. (The folding of unquoted names to lower case in PostgreSQL is incompatible with the SQL standard, which says that unquoted names should be folded to upper case. Thus, foo should be equivalent to "FOO" not "foo" according to the standard. If you want to write portable applications you are advised to always quote a particular name or never quote it.)
Link to above reference