January 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2176) DB2 setMaxResults problem in Hibernate 3.1.3

by Winter Lau (JIRA)

DB2 setMaxResults problem in Hibernate 3.1.3 -------------------------------------------- Key: HHH-2176 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2176 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: DB2 any version Hibernate 3.1.3 JDK 1.5 Reporter: Winter Lau Priority: Blocker public static List listHotTags(int count){ Session ssn = getSession(); String sql = "SELECT tag_name,COUNT(*) FROM dlog_tag GROUP BY tag_name ORDER BY 2 DESC"; SQLQuery query = ssn.createSQLQuery(sql); query.setMaxResults(count); List tags = new ArrayList(); List results = query.list(); for(int i=0;results!=null && i tags.add(((Object[])results.get(i))[0]); } return tags; } tags.add(((Object[])results.get(i))[0]); this code work fine in other database, but in DB2 , it return the rownumber, i must change to get the second element of array then it return the correct data. -- 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

14 years, 10 months

4
12
0 / 0

[Hibernate-JIRA] Créée: (HHH-2389) Improving DB2 dialect

by Nicolas Billard (JIRA)

Improving DB2 dialect --------------------- Key: HHH-2389 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2389 Project: Hibernate3 Type: Improvement Components: query-hql Versions: 3.2.1 Environment: Development based on v 3.2.1 Reporter: Nicolas Billard Priority: Minor Attachments: DB2Dialect.java The class joined to this issue overrides the DB2 dialect. The dialect included in hibernate doesn't work very well when you want to limit returned results (when you call setFirstResult and / or setMaxResults on a query) : - the instructions "fetch first XXX row only is not used - a temporary table is used when it's not usefull - when you have subselects, an exception can occur if subselects have order by clause (because of the getRowNumber method, not corrected here). This version of getLimitString() method generates faster requests (tests made on a table of 300000 rows shows that fetching rows from 20 to 30 takes 0.3 seconds with original version, 0.02 with this one). -- 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

14 years, 10 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-1994) Problem with case sensitive column and tables names and Identity mapping with postgreSQL

by Alex Samad (JIRA)

Problem with case sensitive column and tables names and Identity mapping with postgreSQL ---------------------------------------------------------------------------------------- Key: HHH-1994 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1994 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Hibernate 3.1.3, Java 1.5.0_07 (sun) windos and linux ( 32 & 64 bit). POstgres SQL 8.1 Windows and linux Reporter: Alex Samad Whilst trying to insert into a table with a primary key (ID mapping) which has a identity generator. And the columns and/or the table has been defined with case sensitivey ie back ticks. It fails to get the next serial number and thus fails any inserts. The problem lies in dialect/PostgreSQLDialect.java public String getIdentitySelectString(String table, String column, int type) { return new StringBuffer().append("select currval('") .append(table) .append('_') .append(column) .append("_seq')") .toString(); } table is inclosed in quotes and column is inclosed in quotes which gives a name like "table"_"Column"_seq - which fails I would suggest a fix is to test each of table or column for " and if it exist then to strip it of both of table and column and encluse the whole name in "". This mighe break some old code where say the table is coded in case insensitive table name and case sensitive column key. Sorry not much of a java programmer. -- 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

14 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2655) SQLServer2005Dialect (ROW_NUMBER for Paging)

by Wells Tiedeman (JIRA)

SQLServer2005Dialect (ROW_NUMBER for Paging) -------------------------------------------- Key: HHH-2655 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2655 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.4, 3.2.3, 3.2.2 Environment: SQLServer 2005, Hibernate 3.2.2+ Reporter: Wells Tiedeman Attachments: SQLServer2005Dialect.java Add a SQLServer2005Dialect class to the product that leverages the new ROW_NUMBER capabilities within SQLServer2005 to do paged result sets more efficiently. See attached source... -- 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

14 years, 10 months

14
25
0 / 0

[Hibernate-JIRA] Created: (HHH-2893) Criteria api does not allow a groupProperty to _NOT_ be included in the selected columns

by Antony Stubbs (JIRA)

Criteria api does not allow a groupProperty to _NOT_ be included in the selected columns ---------------------------------------------------------------------------------------- Key: HHH-2893 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2893 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: n/a Reporter: Antony Stubbs When adding a Projections.groupProperty("prop") to a criteria, the property is added to both the GROUP BY and SELECT parts of the generated SQL query. This is a major problem for using the criteria API for complex subselects that require aggregating by a column while grouping by another column. There is presently no way in the criteria API to group by a column and have it _ONLY_ in the GROUP BY clause. i.e. currently Projections.groupProperty("propOne") causes: SELECT propOne, MAX(propTwo) FROM table GROUP BY prop desired option is to have SELECT MAX(propTwo) FROM table GROUP BY prop There have been several people talking about this, but there appears to have been 'no comment'. http://forum.hibernate.org/viewtopic.php?t=939071&highlight=values+groupp... http://forum.hibernate.org/viewtopic.php?t=950803&highlight=groupproperty... http://forum.hibernate.org/viewtopic.php?t=964512&highlight=groupproperty... http://forum.hibernate.org/viewtopic.php?t=957671&highlight=groupproperty... http://forum.hibernate.org/viewtopic.php?p=2317841#2317841 http://forum.hibernate.org/viewtopic.php?t=961617&highlight=groupproperty... Find a 1st cut patch on it's way - I'm just itching my scratch now... Great work on Hibernate guys! -- 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

14 years, 10 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2473) fetch="join" and property-ref

by David CLEMENT (JIRA)

fetch="join" and property-ref ----------------------------- Key: HHH-2473 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473 Project: Hibernate3 Type: Improvement Versions: 3.2.1 Environment: Version 3.2.1, not DB dependant Reporter: David CLEMENT When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the join SQL query but needs another select to find the associated entity by property-ref. It should be able to use the entity fetched in the join instead (maybe this has been done to ensure the unicity of the associated entity, but it introduce a performance issue). -- 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

14 years, 10 months

8
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2596) Add support for Hypersonic 1.8.0.7

by Gail Badner (JIRA)

Add support for Hypersonic 1.8.0.7 ---------------------------------- Key: HHH-2596 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2596 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.3 Environment: Hibernate 3.2.3, Hypersonic 1.8.0.7 Reporter: Gail Badner The version released with Hibernate 3.2.3 (1.8.0.2) is from 2005. It would be good to move to a more recent version. The following unit tests fail when using Hypersonic 1.8.0.7: org.hibernate.test.jpa.lock.JPALockTest.testLockModeTypeRead: Failure: isolation not maintained expected:<lock test> but was:<updated> org.hibernate.test.legacy.IJ2Test.testUnionSubclass: Error: could not set a field value by reflection setter of org.hibernate.test.legacy.J.amount org.hibernate.test.subclassfilter.UnionSubclassFilterTest.testFiltersWithUnionSubclass: Error: Could not execute JDBC batch update org.hibernate.test.unionsubclass.UnionSubclassTest.testUnionSubclass: Failure: junit.framework.AssertionFailedError org.hibernate.test.unionsubclass.UnionSubclassTest.testUnionSubclassManyToOne Error: attempt to create delete event with null entity -- 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

14 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-76) Lazy loaded property isn't indexed properly

by Christian Bauer (JIRA)

Lazy loaded property isn't indexed properly ------------------------------------------- Key: HSEARCH-76 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-76 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.0.0.beta3 Reporter: Christian Bauer @Column(name = "CONTENT") @Length(min = 0, max = 32768) @Basic(fetch = FetchType.LAZY) // Lazy loaded through bytecode instrumentation @org.hibernate.search.annotations.Field(index = org.hibernate.search.annotations.Index.TOKENIZED) private String content; I use fulltextSession.index(o) and I only get two terms indexed "text" and "edit". I don't know where these are coming from actually, no object has these content values. If I trigger an o.getContent() before fulltextSession.index(o), the content is loaded with sequential selects for the lazy property and correctly indexed. -- 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

14 years, 11 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-121) Should optimize set batch to true (for indexWriters)?

by Emmanuel Bernard (JIRA)

Should optimize set batch to true (for indexWriters)? ----------------------------------------------------- Key: HSEARCH-121 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-121 Project: Hibernate Search Issue Type: Bug Components: documentation, engine Reporter: Emmanuel Bernard -- 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

14 years, 11 months

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2578) redesign SessionFactory building

by Steve Ebersole (JIRA)

redesign SessionFactory building -------------------------------- Key: HHH-2578 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2578 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Critical Fix For: cfg-rework Currently a SessionFactory is built by throwing a bunch of stuff into a Configuration object, stirring it, letting it come to a boil, and then pulling out the SessionFactory. In seriousness, there are a few problems with the way we currently operate within a Configuration and how we use it to build a SessionFactory: The general issue that there is no "lifecycle" to when various pieces of information will be available. This is an important omission in a number of ways: 1) consider schema generation. currently we cannot even know the dialect when a lot of db object names are being determined. this would be nice because it would allow us to transparently handle table/column names which are also keywords/reserved-words in the dialect, for example. 2) static-ness of types and the type-mappings. Because we currently have nothing to which to scope them. Ideally a type instance would be aware of the SessionFactory to which it is bound. Instead, what we have now is to change API methods quite a lot of the time to add in the SessionFactory as a passed parameter whenever it is discovered that it is needed. 3) also, most (all?) of the "static" configuration parameters in Hibernate are currently required to be so because of their use from within these static types; thus scoping types would allow us to also scope those config parameters (things like bytecode-provider, use of binary streams, etc). Ideally what I see happening is a scheme where users build a org.hibernate.cfg.Settings (or something similiar) instance themselves. Additionally they would apply metadata to a registry of some sort (lets call it MetadataRegistry for now). Then in order to build a SessionFactory, they would supply these two pieces of information (via ctor? via builder?). The important aspect though is that the information in MetadataRegistry would not be dealt with until that point in time, which would allow us to guarentee that resolving schema object names, types, etc would have access to the runtime Settings (and specifically the dialect) -- 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

14 years, 11 months

3
14
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 2008