| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Thanks for the PR! I think it might be better to solve this issue at a higher level. If tablespaces are disabled, I think that PostgresTableSpaceGenerator.generate() should never be called by the StatementExecutor. Could you check whether this would be possible? |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, thanks for the PR. Also great that you added the test case to ensure we won't have a regression. Will merge after the checks pass.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
When PostgreSQL tablespace testing is disabled, PostgresProvider.mapActions()
now assigns zero executions to CREATE_TABLESPACE. Consequently,
StatementExecutor never selects that action and never calls
PostgresTableSpaceGenerator.generate().
Following the review feedback, this moves the guard up to the scheduling layer,
rather than handling an already-selected action inside the generator.
This removes the previous generator-level IgnoreMeException approach. The
generator is now skipped entirely when tablespace testing is disabled.
Testing