Differences between generated scheme and actual DB

[RetGal]

There are some differences between the generated scheme and the actual (Oracle) DB.
The following fields are present in the DB but not in the generated scheme:

Table RESOURCE and RESOURCE_AUD:

• VERSION_ID
• PREVIOUSVERSION_ID

Table RESOURCEGROUP_AUD:

• V

Table RELEASE_AUD:

• V

Table TAMW_PROPERTYDESCRIPTOR_AUD (need to be booleans Number(1,0) not Number(*,1)):

• ENCRYPT
• NULLABLE
• TESTING

Table TAMW_TEMPLATEDESCRIPTOR_AUD (need to be booleans Number(1,0) not Number(*,1)):

• TESTING

Define indexes in Entities

• we need to set the names of index on the jpa entities

[phil-pona]

@yvespp can the two fields:

• VERSION_ID
• PREVIOUSVERSION_ID

be deleted?

[yvespp]

Both VERSION_ID and PREVIOUSVERSION_ID are empty in TAMW_RESOURCE in on our production Database.
In TAMW_RESOURCE_AUD there are a few rows.
I don't know what they are used for, are they referenced in code?

[RetGal]

These are used by Envers. The TAMW_X_AUD tables should have almost the same columns as the TAMW_X table. Differences: TAMW_X_AUD tables have the following additional columns:

• REV
• REVTYPE

but they should not have a V column (which is only used for optimistic locking).