cli for schema generator should use orm config more #2912
Closed
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.
There are a number of issues with postgres and session_replication_role
I think I found another one here, I could not use the recommended fixes (add disableForeignKeys to orm config) with success.
In my case, I needed the following code fix, then I could run cli command like
schema:create
without the--fk-checks
cli flag and it would use the config specified in orm configuration like:We can see why we might want this to be 'tri state' at the place I made the change by looking what happens down in the schema generator