January 2013 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (HHH-465) order by nulls first / last

by Brett Meyer (JIRA)

13 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7872) Improved L2 cache storage of "reference" data

by Steve Ebersole (JIRA)

13 years, 2 months

1
4
0 / 0

[Hibernate-JIRA] (HHH-7963) Continue new bytecode enhancement support

by Steve Ebersole (JIRA)

13 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] (HHH-7912) Define edge-case behavior for Session.evict

by Steve Ebersole (JIRA)

13 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] (BVAL-315) Consider creating a super-interface to MethodDescriptor ConstructorDescriptor or even remove the distinction

by Emmanuel Bernard (JIRA)

13 years, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3869) Improve toString on SessionStatistics

by David Sheldon (JIRA)

Improve toString on SessionStatistics ------------------------------------- Key: HHH-3869 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3869 Project: Hibernate Core Issue Type: Patch Components: core Reporter: David Sheldon Priority: Trivial Attachments: sessionstats.diff toString on SessionStatisticsImpl is missing a comma - patch attached. Before: SessionStatistics[entity count=100collection count=1100] After: SessionStatistics[entity count=100,collection count=1100] -- 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

13 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3862) Wrong link in documentation tutorial chapter 1

by Christian Bauer (JIRA)

Wrong link in documentation tutorial chapter 1 ---------------------------------------------- Key: HHH-3862 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3862 Project: Hibernate Core Issue Type: Bug Components: documentation Reporter: Christian Bauer Priority: Trivial Hi my name is Rafael. Just to let you know that in this page http://www.hibernate.org/hib_docs/v3/reference/en/html/tutorial-firstapp.... in the *Note* item the link maven is break. This link is point to http://maven.org instead of point to http://maven.apache.org. Let it! Regards, -- 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

13 years, 2 months

3
5
0 / 0

[Hibernate-JIRA] (HHH-995) Order.ignoreCase() only works for VARCHAR types, not CHAR types

by Brett Meyer (JIRA)

13 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3458) Register postgres random() function as "rand" in PostgresSQLDialect

by Stephen Cresswell (JIRA)

Register postgres random() function as "rand" in PostgresSQLDialect ------------------------------------------------------------------- Key: HHH-3458 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3458 Project: Hibernate3 Issue Type: Improvement Components: build Affects Versions: 3.2.5 Environment: Postgres 8.3 Reporter: Stephen Cresswell Priority: Trivial I have an HQL query which uses "order by rand()". This works fine in our local integration tests (which are run against hsqldb), but fails against our build integration tests which runs postgres. The reason the query fails is because postgres function for "rand" is called "random". We can workaround this by dynamically detecting the db driver and generating db specific queries, but it strikes me that the cleanest solution for this is to simply re-register postgres' random function as "rand" in the PostgresSQLDialect, i.e. registerFunction( "random", new NoArgSQLFunction("random", Hibernate.DOUBLE) ); registerFunction( "rand", new NoArgSQLFunction("random", Hibernate.DOUBLE) ); -- 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

13 years, 2 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6643) Criteria doesn't support a chaining of 2 not restrictions (sql = not not criterion)

by Lorber Sebastien (JIRA)

Criteria doesn't support a chaining of 2 not restrictions (sql = not not criterion) ----------------------------------------------------------------------------------- Key: HHH-6643 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6643 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.2.7 Environment: Oracle 10g Hibernate 3.2.7 Reporter: Lorber Sebastien Priority: Trivial When we do: "Restrictions.not( Restrictions.not( Restrictions.eq("field",3) ) );" Hibernate generates "where not not field=3" Which generates an SQL exception The correct SQL syntax is: "where not (not field=3)" (At least our Oracle) I think Hibernate should handle such a case. /!\ See org.hibernate.criterion.NotExpression#toSqlString It seems that for MySQLDialect the parenthesis are added, but not for other dialects... I don't know the sql specificities of all dialects but perhaps the parenthesis should be added also for oracle dialect? Note that we use a custom dialect, extending Oracle10gDialect For those interested: i'm doing two not on a criterion instead of using the criterion directly. In real world, my code sample would be a little more complex: sometimes we compose with a lot of criterions, in many different methods. So i do not exactly use Restrictions.not( Restrictions.not( criterion ) ); Trust me, bad luck, it happened that the dynamic composition of my restrictions, in one specific case, resulted on a double not restriction applied to a criterion. Note that an easy workaround of this is to "add the parenthesis manually". A conjunction is a bit like an "empty restriction" thus what i've done is: Restrictions.not( Restrictions.and( Restrictions.not( Restrictions.eq("field",3) ), Restrictions.conjunction() ) ); Adding the "not criterion" into conjunction containing only the criterion. This way, the sql of my inner not restriction become something like: ( not field = 3 AND 1=1 ) -> We can apply a not on that, while we weren't able on "not field = 3" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2013