PostgreSQL script updates (UTF-8, SERIAL PKs and case-insensitive identifiers) #3
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 updated the original PostgreSQL script in three-steps.
The case-insensitive version of the script is useful if the DB is used with a language like Java where strings are by default use double-quotes. If identifiers are double-quoted in PostgreSQL it's burdensome to write queries, because one would need to wrap identifiers in double-quotes leading to stuff like
String sql = "SELECT * FROM \"Customer\"";
which soon becomes error-prone.