Unable to detect changes not default schema

Open
#176 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
databases

Research direction

Start with the Changes constructor and the changes.changesList path shown in the report, then trace how the Oracle connection determines the schema used for change detection. Define how a non-default schema would be selected and verify that changes made there populate changesList between setStartPointNow() and setEndPointNow().

Written by the indexing model from the issue text.

Description

enhancement

I am using Oracle DB for testing.
Also, the application user and the schema management user are different.

Watching at changes.changesList in the code below, it's null.

OracleDataSource ods = new OracleDataSource();
ods.setURL(...);
ods.setUser(...);
ods.setPassword(...);

Changes changes = new Changes(ods);
changes.setStartPointNow();

makeChangesInTheData();

changes.setEndPointNow();

Changes targets the default schema for change detection, can it target another schema?

Dominant language
Java
Stars
130
Forks
21
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from assertj/assertj-db

All issues in assertj/assertj-db

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.