Quote randomNumber
column in PostgreSQL schema
#9509
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've opened this PR because it is a point of frustration when implementing tests for new frameworks, but I've marked it as draft because the change may be too breaking.
The test specs say that the
World
table has anid
column andrandomNumber
column (note the camelCasing). Indeed, the PostgreSQL schema usesrandomNumber
in itsCREATE TABLE
statement. However, theCREATE TABLE
statement does not quote the column name, so PostgreSQL treats the name as if it were lowercase.Also note that the PostgreSQL schema has
CREATE TABLE World
andCREATE TABLE "World"
statements. Presumably, this is because the former actually creates aworld
table because it too is not quoted. (Whereas the latter actually creates aWorld
table.)This commit modifies the
CREATE TABLE "World"
statement to quote therandomNumber
column so that its camel case is preserved.