Bug 1299842

Summary: [TEST] (6.4.x) Skip tests for HHH-10161 on Sybase
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jan Martiska <jmartisk>
Component: HibernateAssignee: Gail Badner <gbadner>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Simka <msimka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.6CC: bbaranow, bmaxwell, gbadner, jbilek, jmartisk, msimka, smarlow
Target Milestone: CR1   
Target Release: EAP 6.4.8   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 12:36:48 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1279553, 1315479    

Description Jan Martiska 2016-01-19 11:39:08 UTC
Tests for null value specified using javax.persistence.Parameter#getParameterType() (introduced via HHH-10161) fail on Sybase, because Sybase treats null as equal to null

That means,
insert into test values(null);
select * from test where id = null;

The SELECT will return the value added by the INSERT. This behavior is different from all other databases that we support. On other databases, you have to query whether "is null", not "= null". 

I believe this is just a database-specific behavior that Hibernate can't really do anything about, so I suggest to skip these failing tests.

Comment 1 Jan Martiska 2016-01-19 11:49:24 UTC
pull request to Hibernate: https://github.com/hibernate/hibernate-orm/pull/1227

Comment 2 Mike McCune 2016-03-28 22:38:41 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 3 Gail Badner 2016-04-13 04:16:29 UTC
Should this block the component upgrade BZ: 
https://bugzilla.redhat.com/show_bug.cgi?id=1315479 ?

Comment 5 Jiří Bílek 2016-05-06 07:26:53 UTC
Verified with EAP 6.4.8.CP.CR2.

Comment 6 Petr Penicka 2017-01-17 12:36:48 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.