-
Notifications
You must be signed in to change notification settings - Fork 157
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
issue #3676 remove Db2 support #3803
Conversation
punktilious
commented
Jul 25, 2022
•
edited by lmsurpre
Loading
edited by lmsurpre
- removal of all things db2
- removal of the multitenant db schema flavor (which was only supported on db2)
- removal of the legacy approach to storing parameters (which was only used in db2)
- renamed CommonTokenValues classes (Cache and DAO) to CommonValues to reflect that they cover both token values and reference values now
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
…sistence API Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
|
||
1. Print the DDL and manually tweak it for your desired database; or | ||
2. Add configuration to control which IDatabaseAdapter and IDatabaseTranslator are used. | ||
|
||
Note, the Db2 implementation uses stored procedures, the Postgres implementation uses Functions, and the Derby implementation is JDBC. | ||
Note, the Postgres implementation uses Functions, and the Derby implementation is JDBC. |
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.
super minor
Note, the Postgres implementation uses Functions, and the Derby implementation is JDBC. | |
Note, the Postgres implementation uses Functions and the Derby implementation is JDBC. |
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.
fixed
...stence-jdbc/src/main/java/com/ibm/fhir/persistence/jdbc/citus/CitusResourceReferenceDAO.java
Show resolved
Hide resolved
@@ -82,21 +77,9 @@ public MigrateV0021AbstractTypeRemoval(IDatabaseAdapter adapter, String adminSch | |||
|
|||
@Override | |||
public void run(IDatabaseTranslator translator, Connection c) { |
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.
Not for this PR, but I wonder if our 5.0 is a chance to remove some of these historical migration objects.
Or, if not, maybe we deprecate them and remove in 6.0 (so we could support 4.x -> 5.x but we'd require 5.x to get to 6.x)
fhir-persistence-schema/src/main/java/com/ibm/fhir/schema/patch/Main.java
Outdated
Show resolved
Hide resolved
// Pretend that our target is a DB2 database | ||
Db2Adapter adapter = new Db2Adapter(tgt); | ||
// Pretend that our target is a Derby database | ||
DerbyAdapter adapter = new DerbyAdapter(tgt) { |
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.
in other cases we replaced with Postgres...any reason to target derby from this one?
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.
Yeah, because Postgres requires a whole bunch of doesXXExist
methods to be overridden in the adapter which are currently private.
fhir-persistence-schema/src/test/java/com/ibm/fhir/schema/derby/OldFhirResourceTableGroup.java
Show resolved
Hide resolved
fhir-persistence-schema/src/test/java/com/ibm/fhir/schema/derby/OldFhirSchemaGenerator.java
Show resolved
Hide resolved
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.
Left some comments (mostly thoughts for the future), but this is some great cleanup.
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>
Signed-off-by: Robin Arnold <robin.arnold@ibm.com>