Bug 1326419

Summary:	Case-sensitive MariaDB issue with filters
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Kris Verlaenen <kverlaen>
Component:	Business Central	Assignee:	Neus Miras <nmirasch>
Status:	CLOSED EOL	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	unspecified	CC:	rrajasek
Target Milestone:	CR1
Target Release:	6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 20:02:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Kris Verlaenen 2016-04-12 15:36:47 UTC

Clone of https://issues.jboss.org/browse/JBPM-5063

Testing against db configured as case sensitive (mariadb on linux), the query that shows the Process Instances domain data, throws this exception
Caused by: org.mariadb.jdbc.internal.util.dao.QueryException: Unknown column 'V.variableId' in 'where clause'

To reproduce:
Execute the product against a bd configured case sensitive.
Access to process instance perspective, and create an instance
Create a new filter that shows domanin data (processId='instance_process_id')
Current result: throws an exception and the list appears waiting
Expected result: show the instances and the domain data as column to select

Comment 1 Neus Miras 2016-04-13 09:42:32 UTC

The issue has been fixed and the pr for the 6.4.x is 

https://github.com/droolsjbpm/jbpm-console-ng/pull/401


At master the PR has been merged
https://github.com/droolsjbpm/jbpm-console-ng/commit/ca3aaa07c04cdc0673a02f61c20917d7b8eae760

Waiting for the merging of the PR to 6.4.x to change the bz to modified

Comment 2 Neus Miras 2016-04-14 12:54:33 UTC

the PR has been merged to 6.4.x
https://github.com/droolsjbpm/jbpm-console-ng/commit/4d1bf2f3982d3f9f166b23ee3476d8340d658134

Comment 3 Jan Hrcek 2016-04-29 10:51:08 UTC

The issue has been fixed. Verified with BPM Suite 6.3.0 CR1