| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODEXPW-224 |
|---|
|
...
In a scope of this spike we need to create a detailed plan for
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODEXPW-218 |
|---|
|
implementation.
...
In a scope of
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODEXPW-198 |
|---|
|
a postgres database was introduces as a replacement for in-memory hsqldb so now another approach for eHoldings job could be used.
...
| Code Block |
|---|
| language | sql |
|---|
| firstline | 0 |
|---|
| title | Package |
|---|
| linenumbers | true |
|---|
|
E_HOLDINGS_PACKAGE (
ID VARCHAR(50) NOT NULL,
JOB_EXECUTION_ID BIGINT NOT NULL,
E_PACKAGE TEXT,
AGREEMENTS TEXT,
NOTES TEXT,
PRIMARY KEY(ID, JOB_EXECUTION_ID, ID)
) |
| Code Block |
|---|
| language | sql |
|---|
| firstline | 0 |
|---|
| title | Package |
|---|
| linenumbers | true |
|---|
|
E_HOLDINGS_RESOURCE (
ID VARCHAR(50) NOT NULL,
JOB_EXECUTION_ID BIGINT NOT NULL,
RESOURCES_DATA TEXT,
AGREEMENTS TEXT,
NOTES TEXT,
PRIMARY KEY(ID, JOB_EXECUTION_ID, ID)
) |
TEXT field type is used because we don't need any operations with this fields, they'll just keep values and data that is going to be queried by id or by "seek" method (using id).
...