-
Notifications
You must be signed in to change notification settings - Fork 356
feat: experimental db pull as declarative schemas #4722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or 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
Pull Request Test Coverage Report for Build 21473922934Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
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.
What kind of change does this PR introduce?
feature
What is the new behavior?
Cluster-Wide Objects (
cluster/)roles.sqlCREATE ROLE,ALTER ROLE,GRANT role TO roleextensions.sqlCREATE EXTENSIONforeign_data_wrappers.sqlCREATE FOREIGN DATA WRAPPER,CREATE SERVER,CREATE USER MAPPINGpublications.sqlCREATE PUBLICATION,ALTER PUBLICATIONsubscriptions.sqlCREATE SUBSCRIPTION,ALTER SUBSCRIPTIONevent_triggers.sqlCREATE EVENT TRIGGER,ALTER EVENT TRIGGERtablespaces.sqlCREATE TABLESPACE,ALTER TABLESPACEvariables.sqlSET check_function_bodies = false;,ALTER SYSTEM,CREATE DATABASESchema-Scoped Objects (inside
schemas/{schema}/)schemas/{schema}/schema.sqlCREATE SCHEMA,CREATE COLLATION,CREATE OPERATOR FAMILY,CREATE TEXT SEARCH, schema-levelGRANT, schema-levelALTER DEFAULT PRIVILEGEschemas/{schema}/types.sqlCREATE TYPE(enum, composite, range)schemas/{schema}/sequences.sqlCREATE SEQUENCE,ALTER SEQUENCE(excluding owned by)schemas/{schema}/tables/{table}.sqlCREATE TABLE,ALTER TABLE(excluding foreign key constraints),CREATE INDEX,CREATE POLICY, BEFORE/AFTERCREATE TRIGGER, trigger functions, tableGRANT,COMMENTschemas/{schema}/views/{view}.sqlCREATE VIEW, INSTEAD OFCREATE TRIGGER, viewGRANT,COMMENTschemas/{schema}/materialized_views/{mview}.sqlCREATE MATERIALIZED VIEW, indexes,GRANT,COMMENTschemas/{schema}/functions/{function}.sqlCREATE FUNCTION(including all overloads and trigger functions),GRANT,COMMENTschemas/{schema}/procedures/{procedure}.sqlCREATE PROCEDURE,GRANT,COMMENTschemas/{schema}/foreign_tables/{ftable}.sqlCREATE FOREIGN TABLE,GRANTschemas/{schema}/domains/{domain}.sqlCREATE DOMAIN,ALTER DOMAINschemas/{schema}/operators/{operator}.sqlCREATE OPERATOR,ALTER OPERATOR,CREATE OPERATOR CLASS,CREATE AGGREGATE,CREATE TRANSFORMschemas/{schema}/policies/{policy}.sqlCREATE POLICY,CREATE RULE, foreign key constraintsschemas/unqualified.sqlSELECT lo_create(),CREATE CASTAdditional context
Known caveats