[Hibernate-JIRA] Created: (HHH-4580) Possible Sybase bug causes AssertionFailure in QueryByExampleTest
3:28 a.m.
Possible Sybase bug causes AssertionFailure in QueryByExampleTest
-----------------------------------------------------------------
Key: HHH-4580
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.2.4.sp1
Environment: sybase 15
Reporter: Strong Liu
Test QueryByExampleTest.testJunctionNotExpressionQBE fails due to a possible bug in Sybase
15. The same test passes for Sybase 12.5. The test expects two records as a result for a
query, but it gets 3. After some debugging with the query that Hibernate generated, I end
up with these two simpler ones:
select id from Componentizable where not (name like ? and subName1 like ?)
select id from Componentizable where not (name like 'hibernate' and subName1 like
'ope%')
The first one returns three records, while the second returns two. The interesting part is
that if I replace the first parameter in the first query by a hardcoded value
("hibernate"), it still returns 3 records. That means that the problem is
probably with the binding of JDBC parameters containing a wildcard % .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:28 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4580) Possible Sybase bug causes AssertionFailure in QueryByExampleTest
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580?page=c...
]
Strong Liu commented on HHH-4580:
---------------------------------
https://jira.jboss.org/jira/browse/JBPAPP-3069
Possible Sybase bug causes AssertionFailure in QueryByExampleTest
-----------------------------------------------------------------
Key: HHH-4580
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.4.sp1, 3.3.2, 3.5.0.Beta-1, 3.5.0-Beta-2
Environment: sybase 15
Reporter: Strong Liu
Test QueryByExampleTest.testJunctionNotExpressionQBE fails due to a possible bug in
Sybase 15. The same test passes for Sybase 12.5. The test expects two records as a result
for a query, but it gets 3. After some debugging with the query that Hibernate generated,
I end up with these two simpler ones:
select id from Componentizable where not (name like ? and subName1 like ?)
select id from Componentizable where not (name like 'hibernate' and subName1 like
'ope%')
The first one returns three records, while the second returns two. The interesting part
is that if I replace the first parameter in the first query by a hardcoded value
("hibernate"), it still returns 3 records. That means that the problem is
probably with the binding of JDBC parameters containing a wildcard % .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4580) Possible Sybase bug causes AssertionFailure in QueryByExampleTest
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580?page=c...
]
Steve Ebersole commented on HHH-4580:
-------------------------------------
Actually I am wondering if the test case itself might have to do with null comparisons.
The test basically builds a disjunction predicate like:
( OR^ (ex) (NOT ex) )
So... give me everything that matches either (1) ex or (2) NOT ex. In theory that should
be everything. However ANSI SQL says that any comparision involving NULLs should always
evaluate to UNKNOWN. So even though there are a total of 3 records in the db only 2
should match because of that null-comparison rule. Both Sybase and SQL Server treat null
comparisons in a manner other than what is described by ANSI SQL. Specifically I think
they say here that "NULL LIKE 'something%'" evaluates to FALSE and
therefore the negation (NOT) of that evaluates to TRUE.
You say that this is a different server (15 versus 12.5). Was this 15 server set up with
the option "set ansinull on"? I'll follow up with Red Hat QE who own these
boxes to verify.
As for your experienced discrepency between a literal match-string and a parameterized
match-string, dunno. That sure sounds like I bug in the driver or database. I'll
look after I follow up with QE
Possible Sybase bug causes AssertionFailure in QueryByExampleTest
-----------------------------------------------------------------
Key: HHH-4580
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.4.sp1, 3.3.2, 3.5.0.Beta-1, 3.5.0-Beta-2
Environment: sybase 15
Reporter: Strong Liu
Test QueryByExampleTest.testJunctionNotExpressionQBE fails due to a possible bug in
Sybase 15. The same test passes for Sybase 12.5. The test expects two records as a result
for a query, but it gets 3. After some debugging with the query that Hibernate generated,
I end up with these two simpler ones:
select id from Componentizable where not (name like ? and subName1 like ?)
select id from Componentizable where not (name like 'hibernate' and subName1 like
'ope%')
The first one returns three records, while the second returns two. The interesting part
is that if I replace the first parameter in the first query by a hardcoded value
("hibernate"), it still returns 3 records. That means that the problem is
probably with the binding of JDBC parameters containing a wildcard % .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:35 a.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-4580) Possible Sybase bug causes AssertionFailure in QueryByExampleTest
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580?page=c...
]
Steve Ebersole reassigned HHH-4580:
-----------------------------------
Assignee: Steve Ebersole
Possible Sybase bug causes AssertionFailure in QueryByExampleTest
-----------------------------------------------------------------
Key: HHH-4580
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.4.sp1, 3.3.2, 3.5.0.Beta-1, 3.5.0-Beta-2
Environment: sybase 15
Reporter: Strong Liu
Assignee: Steve Ebersole
Test QueryByExampleTest.testJunctionNotExpressionQBE fails due to a possible bug in
Sybase 15. The same test passes for Sybase 12.5. The test expects two records as a result
for a query, but it gets 3. After some debugging with the query that Hibernate generated,
I end up with these two simpler ones:
select id from Componentizable where not (name like ? and subName1 like ?)
select id from Componentizable where not (name like 'hibernate' and subName1 like
'ope%')
The first one returns three records, while the second returns two. The interesting part
is that if I replace the first parameter in the first query by a hardcoded value
("hibernate"), it still returns 3 records. That means that the problem is
probably with the binding of JDBC parameters containing a wildcard % .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:03 a.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-4580) Possible Sybase bug causes AssertionFailure in QueryByExampleTest
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580?page=c...
]
Strong Liu resolved HHH-4580.
-----------------------------
Resolution: Won't Fix
from juca(JBPAPP-3069):
I have "sa" rights in the database, so, I can change it. I tried to find the
command to set it for all connections for a given database, but I couldn't yet.
Anyway, I added the below line to the test (locally) and it passes, confirming that the
"ansinull" option is indeed the "guilty" in this case:
s.connection().createStatement().execute("set ansinull on");
This line shouldn't go into the test case, I added it only locally to verify if this
option affects the test.
Possible Sybase bug causes AssertionFailure in QueryByExampleTest
-----------------------------------------------------------------
Key: HHH-4580
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.4.sp1, 3.3.2, 3.5.0.Beta-1, 3.5.0-Beta-2
Environment: sybase 15
Reporter: Strong Liu
Assignee: Steve Ebersole
Test QueryByExampleTest.testJunctionNotExpressionQBE fails due to a possible bug in
Sybase 15. The same test passes for Sybase 12.5. The test expects two records as a result
for a query, but it gets 3. After some debugging with the query that Hibernate generated,
I end up with these two simpler ones:
select id from Componentizable where not (name like ? and subName1 like ?)
select id from Componentizable where not (name like 'hibernate' and subName1 like
'ope%')
The first one returns three records, while the second returns two. The interesting part
is that if I replace the first parameter in the first query by a hardcoded value
("hibernate"), it still returns 3 records. That means that the problem is
probably with the binding of JDBC parameters containing a wildcard % .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:59 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4580) Possible Sybase bug causes AssertionFailure in QueryByExampleTest
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580?page=c...
]
Strong Liu commented on HHH-4580:
---------------------------------
add "set ansinull on" in hibernate-parent/pom.xml
ANSI NULL mode – “val = NULL” is unknown when “val” is NULL
The ANSI rule for the where and on clauses return rows that are true, and rejects rows
that are both false and unknown.
Possible Sybase bug causes AssertionFailure in QueryByExampleTest
-----------------------------------------------------------------
Key: HHH-4580
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.4.sp1, 3.3.2, 3.5.0.Beta-1, 3.5.0-Beta-2
Environment: sybase 15
Reporter: Strong Liu
Assignee: Steve Ebersole
Test QueryByExampleTest.testJunctionNotExpressionQBE fails due to a possible bug in
Sybase 15. The same test passes for Sybase 12.5. The test expects two records as a result
for a query, but it gets 3. After some debugging with the query that Hibernate generated,
I end up with these two simpler ones:
select id from Componentizable where not (name like ? and subName1 like ?)
select id from Componentizable where not (name like 'hibernate' and subName1 like
'ope%')
The first one returns three records, while the second returns two. The interesting part
is that if I replace the first parameter in the first query by a hardcoded value
("hibernate"), it still returns 3 records. That means that the problem is
probably with the binding of JDBC parameters containing a wildcard % .
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4867
days inactive
5517
days old
hibernate-issues@lists.jboss.org
5 comments
2 participants
participants (2)
-
Steve Ebersole (JIRA) -
Strong Liu (JIRA)