Skip to content

Conversation

jawad-arb123
Copy link
Member

Old test (Postgres assumption):

Expected user2 to still be visible inside the parent transaction after its rollback.
This matches Postgres behavior: rolled-back rows can sometimes still be visible in the same transaction until the outer transaction ends.

New test (Oracle semantics):

Now expects user2 to disappear immediately after rolling back to the savepoint.
Oracle uses undo segments and ROLLBACK TO SAVEPOINT, which permanently discards changes from the inner transaction, so that even the parent can’t see them anymore.

@jawad-arb123 jawad-arb123 self-assigned this Aug 26, 2025
@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Aug 26, 2025
@jawad-arb123 jawad-arb123 requested review from ting-lan-wang and removed request for ting-lan-wang August 26, 2025 13:35
ting-lan-wang
ting-lan-wang previously approved these changes Aug 29, 2025
@jawad-arb123 jawad-arb123 deleted the fix_transaction_tests branch September 3, 2025 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants