-
Notifications
You must be signed in to change notification settings - Fork 93
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
Test changes for 'Fix error when trying to drop columns from temp tables.' #2753
Test changes for 'Fix error when trying to drop columns from temp tables.' #2753
Conversation
Signed-off-by: Jason Teng <[email protected]>
Signed-off-by: Jason Teng <[email protected]>
Signed-off-by: Jason Teng <[email protected]>
Signed-off-by: Jason Teng <[email protected]>
CREATE TABLE #t1 (a INT, b INT) | ||
GO | ||
|
||
ALTER TABLE #t1 DROP COLUMN b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add more tests, such as
- dropping then recreating the same column multiple times
- make sure that dependencies aren't broken (so if the column depends on another object, or an object depends on the column that the proper behavior happens)
- more complicated dependencies such as with toast/index/identity etc
- ensure that the table also works (i can select, update, drop from it normally)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added more test cases. Note that foreign key constraints are not allowed for temp tables, so I can't test that.
Pull Request Test Coverage Report for Build 10047842090Warning: 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 |
Signed-off-by: Jason Teng <[email protected]>
~~ERROR (Code: 3726)~~ | ||
|
||
~~ERROR (Message: cannot drop column b of table "#temp_table_rollback_t1" because other objects depend on it)~~ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for handling this.
Do we have tests for scenarios where it's supposed to fail with this error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just added an extra test case, that while not reproducing this exact error, produces a similar error due to a dependency.
Signed-off-by: Jason Teng <[email protected]>
6b45d49
into
babelfish-for-postgresql:BABEL_4_X_DEV
…les.' (babelfish-for-postgresql#2753) Tests for babelfish-for-postgresql/postgresql_modified_for_babelfish#410 Task: BABEL-4912 Signed-off-by: Jason Teng <[email protected]>
…les.' (#2753) (#2779) Tests for babelfish-for-postgresql/postgresql_modified_for_babelfish#410 Task: BABEL-4912 Signed-off-by: Jason Teng <[email protected]>
…les.' (babelfish-for-postgresql#2753) Tests for babelfish-for-postgresql/postgresql_modified_for_babelfish#410 Task: BABEL-4912 Signed-off-by: Jason Teng <[email protected]>
…les.' (babelfish-for-postgresql#2753) (babelfish-for-postgresql#2779) Tests for babelfish-for-postgresql/postgresql_modified_for_babelfish#410 Task: BABEL-4912 Signed-off-by: Jason Teng <[email protected]>
Description
Tests for babelfish-for-postgresql/postgresql_modified_for_babelfish#410
Issues Resolved
BABEL-4912
Test Scenarios Covered
Use case based -
Boundary conditions -
Arbitrary inputs -
Negative test cases -
Minor version upgrade tests -
Major version upgrade tests -
Performance tests -
Tooling impact -
Client tests -
Check List
By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.