Bug 1284367 - [QE](6.2.z)Missing semicolons in two statements in SQL Server DB upgrade scripts
Summary: [QE](6.2.z)Missing semicolons in two statements in SQL Server DB upgrade scripts
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Migration Tool
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: CR1
: 6.2.1
Assignee: Edson Tirelli
QA Contact: Tibor Zimanyi
URL:
Whiteboard:
Depends On:
Blocks: 1288023
TreeView+ depends on / blocked
 
Reported: 2015-11-23 07:37 UTC by Tibor Zimanyi
Modified: 2020-03-27 20:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:05:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPM-4843 0 Major Resolved SqlServer upgrade scripts - 2 statements miss semicolon at the end of them 2016-02-25 14:19:52 UTC

Description Tibor Zimanyi 2015-11-23 07:37:41 UTC 
Description of problem:

Two statements from SqlServer upgrade scripts miss semicolon at the end of them. See here [1]. The correct syntax is to end a statement with semicolon or batch of statements with GO. PR for this is here [2]. This is not blocker for 6.2.0 - See comments in PR. 

This applies for both SqlServer dialects that we have scripts for - sqlserver, sqlserver2008.

[1] https://github.com/droolsjbpm/jbpm/blob/974cad8d8a553fffe1dc0d3cfbdf7fafaca71461/jbpm-installer/db/upgrade-scripts/sqlserver2008/bpms-6.0-to-6.1.sql#L49
[2] https://github.com/droolsjbpm/jbpm/pull/344

Version-Release number of selected component (if applicable): 6.2.0.CR1
Comment 2 Maciej Swiderski 2015-12-18 17:07:19 UTC 
merged into 6.3.x branch

jbpm
6.3.x:
https://github.com/droolsjbpm/jbpm/commit/51e21cd7efbe62f3d950bfd7d7c7556362928073
Comment 3 JBoss JIRA Server 2015-12-21 14:20:16 UTC 
Maciej Swiderski <swiderski.maciej> updated the status of jira JBPM-4843 to Resolved
Comment 4 Radovan Synek 2016-01-21 14:09:27 UTC 
Verified with BPMS-6.2.1.CR1
Note You need to log in before you can comment on or make changes to this bug.