Build result summary

Details

Completed
Queue duration
1 day
Duration
3 seconds
Labels
None
Revision
70f09d3f4341561541459c5f31f796df699ab39f 70f09d3f4341561541459c5f31f796df699ab39f
Fixed in
#145 (Manual run by Daniel Kayiwa)
No failed test found. A possible compilation error occurred.

Responsible

Code commits

Author Commit Message Commit date
Daniel Kayiwa Daniel Kayiwa 70f09d3f4341561541459c5f31f796df699ab39f 70f09d3f4341561541459c5f31f796df699ab39f Merge pull request #19 from suniala/MAP-5-varchar-length
MAP-5: Take length limit into account in class name index change set
Mikko Suniala <mikko.suniala@iki.fi> Mikko Suniala <mikko.suniala@iki.fi> a1638876dbf32a50de48a6b71db335f5834df64e a1638876dbf32a50de48a6b71db335f5834df64e MAP-5: Take length limit into account in class name index change set
MySQL has a 255 (usually) char length limit on indexes. Prior to 5.5,
index key length is automatically limited to this length (a 'prefix'
index) but on 5.6 it is an error to try to create an index for a
longer column. Modify the existing change set into a mysql specific
one that limits the index key length and create another change set
for all other dbms.

Note that this commit modifies an existing 1.1.0-SNAPSHOT liquibase
change set. If you have deployed a 1.1.0-SNAPSHOT version from a
prior commit, you may have to drop the index
metadatamapping_idx_mdtm_mdclass manually before deploying this
commit.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeMAP-5Could not obtain issue details from Jira