Feature: Add DB comments for PG producer #137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…oducer::PG * also verifies that `comments` become an array
* let's fix them tests!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Many databases support storing comments as part of the actual schema.
Postgres is one of them, just the syntax is slightly different than other RDBMS, b/c you
can't define it inline with the table definition.
This PR adds the ability to write out comments using the
COMMENTcommand documentedhere.
It follows the example of the MySQL producer and puts all comments into the schema,
including ones that were parsed as DDL only comments (line comments starting with
--).