-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: maxdb issue with upper(NULL)
PostPosted: Wed Apr 23, 2008 2:02 pm 
Newbie

Joined: Tue Apr 15, 2008 4:12 am
Posts: 1
I am using hibernate 3.2.6. with mssqlserver 2005 and maxdb 7.6. Using Criteria api.

Some queries using left outer joins return different data in both, after investigating, it turns out upper(column1)='hello' is true in maxdb when column1 is NULL (due to the outer join). The problem also happens with lower() and probably other functions.

I dont know if you guys are aware of this and decided the hibernate user has to take it into account. If that is the case, then dismiss this post.

In case hibernate would want to take care of it on its own, it would need to add a condition column1<>NULL. I have done this with the criteria api and it solves the issue.

thanks
javi


Top
 Profile  
 
 Post subject: Re: maxdb issue with upper(NULL)
PostPosted: Thu Mar 04, 2010 7:15 am 
Newbie

Joined: Thu Mar 04, 2010 7:12 am
Posts: 2
Where you able to find a solution?


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.