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.
@HuxleyKendell and I were working on the updated script at the same time (great job, Hux). I'm submitting this as an update to consider because of how Postgres names objects. All objects are coalesced to lowercase unless they're quoted, but then all objects need to be quoted from that point forward if they are anything other than lowercase. Therefore, the Postgres convention is to use snake_case, which is used for all other internal functions and naming.
This becomes evident in the baseline script, where all of the creation statements are all lowercase (rather than the CamelCase of the creation script), and then automatically generated objects like sequences are snake_case.
I also made updates to the identity columns so that they would function like SQL Server identity columns (cannot insert values manually), and created some procedures rather than functions. Essentially, any function that does not return a result (void) can technically be a procedure. These changes are debatable, but I thought having the opportunity to show that both are maintained by Flyway was potentially helpful.