Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

GH-3035: Include INT_ prefix into PK constraints

Browse Source 
Fixes https://github.com/spring-projects/spring-integration/issues/3035

To avoid names collision for primary key indexes on the target schemas
include an `INT_` prefix to names for the PKs in Spring Integration SQL
scripts.
Also fix the Docs for mentioned PKs
This commit is contained in:
Artem Bilan
2019-08-19 11:32:58 -04:00
committed by Gary Russell
parent a756e6334d
commit 4db71d751a
10 changed files with 47 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/reference/asciidoc/jdbc.adoc
View File

@@ -1072,7 +1072,7 @@ CREATE TABLE INT_LOCK (
REGION VARCHAR(100),
CLIENT_ID CHAR(36),
CREATED_DATE TIMESTAMP NOT NULL,
constraint LOCK_PK primary key (LOCK_KEY, REGION)
constraint INT_LOCK_PK primary key (LOCK_KEY, REGION)
);
----
====
@@ -1125,7 +1125,7 @@ CREATE TABLE INT_METADATA_STORE (
METADATA_KEY VARCHAR(255) NOT NULL,
METADATA_VALUE VARCHAR(4000),
REGION VARCHAR(100) NOT NULL,
constraint METADATA_STORE primary key (METADATA_KEY, REGION)
constraint INT_METADATA_STORE_PK primary key (METADATA_KEY, REGION)
);
----
====