March 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2624) NullPointerException when Query.list()

by Eddie Man (JIRA)

NullPointerException when Query.list() -------------------------------------- Key: HHH-2624 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2624 Project: Hibernate3 Issue Type: Bug Components: core Environment: MySQL database Reporter: Eddie Man Priority: Critical Attachments: src.zip The following exception was thrown when I calling Query.list(): Exception in thread "main" java.lang.NullPointerException at org.hibernate.persister.entity.AbstractEntityPersister.loadByUniqueKey(AbstractEntityPersister.java:1641) at org.hibernate.type.EntityType.loadByUniqueKey(EntityType.java:608) at org.hibernate.type.EntityType.resolve(EntityType.java:382) at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:116) at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:842) at org.hibernate.loader.Loader.doQuery(Loader.java:717) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2211) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2095) at org.hibernate.loader.Loader.list(Loader.java:2090) Reference issue : http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-48 Steps for reproduce the problem ================== 1. Unzip the attached file. 2. Execute the "schema.ddl" to create the tables. 3. Execute the "data.ddl" to insert the simple records. 4. Compile the src, and run the Main class. -- 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

15 years

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2993) NPE on org.hibernate.hql.ast.HqlSqlWalker, When Using explicit inner join on primitive type

by Vincent YSMAL (JIRA)

NPE on org.hibernate.hql.ast.HqlSqlWalker, When Using explicit inner join on primitive type -------------------------------------------------------------------------------------------- Key: HHH-2993 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2993 Project: Hibernate3 Issue Type: Bug Environment: Hibernate 3.2.5ga , oracle 10G, Windows Reporter: Vincent YSMAL Hi, trying to make an inne join on a primitve type cause an NPE. java.lang.NullPointerException at org.hibernate.hql.ast.HqlSqlWalker.createFromJoinElement(HqlSqlWalker.java:310) at org.hibernate.hql.antlr.HqlSqlBaseWalker.joinElement(HqlSqlBaseWalker.java:3275) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3067) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:2945) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:688) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:544) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.orm.hibernate3.HibernateTemplate$CloseSuppressingInvocationHandler.invoke(HibernateTemplate.java:1219) Trying some HQL like this : "from Cat as cat inner join cat.name as a0 " cause an NPE -- 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

15 years

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-902) Support naming / renaming HQL editor tabs

by Joseph Marques (JIRA)

Support naming / renaming HQL editor tabs ----------------------------------------- Key: HBX-902 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-902 Project: Hibernate Tools Type: New Feature Versions: 3.2beta8 Reporter: Joseph Marques Right now, if I open multiple HQL editors under the same configuration they are ALL named "HQL: <configuration>" When I have 3 or 4 of them open, I sometimes forget which query is in which, so I waste time poking around to find the right one. If they could be suffixed with the unique user-chosen token, then they would be much easier to work with. So something like: "HQL: <configuration>: <name>" Or, even better, since HQL isn't really needed (because the HQL editor has a distinct editor icon), it could be removed entirely, leaving us with: "<configuration>: <name>" Thoughts? -- 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

15 years, 1 month

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2399) FlushMode.AUTO practically unusable - should not flush before EVERY query

by Piotr Kołaczkowski (JIRA)

FlushMode.AUTO practically unusable - should not flush before EVERY query ------------------------------------------------------------------------- Key: HHH-2399 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2399 Project: Hibernate3 Type: Improvement Versions: 3.1.3, 3.2.1, 3.2.2, 3.2.0.ga Environment: PostgreSQL 8.1.5, JDBC 2 and 3, Linux kernel 2.4.x, 2.6.x, Java 1.5.0_09 Reporter: Piotr Kołaczkowski Attachments: hbtest.zip The method flushIfRequired seems to flush before every query execution, even though there wasn't anything changed to the objects in the session, and the objects in the session are of different class than the object(s) queried. When having more than a few such objects in a session, it may lead to large, unneeded overheads (I noticed 10-200 times slowdown on simple queries). Our system uses many fast queries, that uasually return only one result or few results. The average query durations on different levels, measured by System.nanoTime() (see the attachment): - database level: 0.05 ms - pure JDBC code, prepared statements: 0.2 ms - pure JDBC code, no prepared statements: 0.7 ms - not cached hibernate query, no other objects associated with the session: 1.3 ms - cached hibernate query, object in the session cache, no other objects associated with the session: 1.1 ms - cached hibernate query, 10000 very simple objects of some other class in the session: >50 ms 10000 may seem large, but note these were very simple objects, having only 2 properties. On our production system we have classes with many properties, and even 20 objects in a session can cause a sub-millisecond query to run longer than 5 ms. We switched to FlushMode.COMMIT, and now the performance is much better. Can you do something about this? As far as I've read in JIRA, a similar issue exists in Hibernate 2.x, and is still OPEN / UNRESOLVED. BTW. Why is the 1st level cache so slow in my tests? Why reading just a 2 field object from the database cause so much overhead over pure JDBC? What am I doing wrong? There is so much marketing about using cglib reflection optimizer in the performance FAQ but even if I retrieved these objects using JDBC and reflection, I would achieve much better performance. After all 1 ms is very much time, if getting results from DB and sending them to JVM lasts 0.2 ms. -- 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

15 years, 1 month

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2347) Improvement to DerbyDialect default identy generation mode

by Fabrizio Giustina (JIRA)

Improvement to DerbyDialect default identy generation mode ---------------------------------------------------------- Key: HHH-2347 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2347 Project: Hibernate3 Type: Patch Versions: 3.2.1 Reporter: Fabrizio Giustina Attachments: DerbyDialect-identity.diff although derby supports identities org.hibernate.dialect.DerbyDialect strangely uses an HiLo generation strategy for ids (for any other dialects that support identities IdentityGenerator is the default). Even more curiously, DerbyDialect overrides getIdentityColumnString() from the Db2 dialect by using "generated ALWAYS as identity" instead of "generated BY DEFAULT as identity". Derby however fully supports "by default" in identities as clarified in http://db.apache.org/derby/docs/10.1/ref/rrefsqlj37836.html . "by default" should be preferred since it allows a direct insertion when needed (and I can't see no reason why enabling it for db2 and not for derby). The patch attached simply deletes two methods, so that the default implementation from Db2Dialect is used: - removing getIdentityColumnString() make derby use "by default" identities like db2 already does - removing getNativeIdentifierGeneratorClass() make it choose IdentityGenerator.class (it falls back to the default strategy used in org.hibernate.dialect.Dialect) note that part of this issue has already been reported in HHH-1918 (not addressing the identity generation string) -- 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

15 years, 1 month

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3391) DerbyDialect should support limits

by Marijo (JIRA)

DerbyDialect should support limits ---------------------------------- Key: HHH-3391 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3391 Project: Hibernate3 Issue Type: New Feature Components: core Environment: Apache Derby 10.4.1.3 Reporter: Marijo >From Apache Derby FAQ http://db.apache.org/derby/faq.html#limit "Starting with the 10.4.1.3 release Derby also supports limiting the number of rows using the ROW_NUMBER function." The DerbyDialect class should support limiting for the actual Derby release, too. -- 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

15 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-797) using @LOB annotation

by Patrick Walter (JIRA)

using @LOB annotation --------------------- Key: ANN-797 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-797 Project: Hibernate Annotations Issue Type: Bug Reporter: Patrick Walter When I use the @LOB annotation it always creates only VARCHAR(255) for stringData and Binary (255) for binaryData defined below. @Lob @Basic(fetch=FetchType.LAZY) private byte[] binaryData; @Lob @Basic(fetch=FetchType.LAZY) private String stringData; Any help in resolving this would be VERRY!!! appreciated. THANKS -- 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

15 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3555) Extend the query system with the ability to traverse associations

by Adam Warski (JIRA)

Extend the query system with the ability to traverse associations ----------------------------------------------------------------- Key: HHH-3555 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3555 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski Assignee: Adam Warski -- 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

15 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2413) Offer a way to log bound jdbc parameters in a uniform way for UserType implementors

by Baptiste MATHUS (JIRA)

Offer a way to log bound jdbc parameters in a uniform way for UserType implementors ----------------------------------------------------------------------------------- Key: HHH-2413 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2413 Project: Hibernate3 Type: Improvement Versions: 3.2.2 Reporter: Baptiste MATHUS Priority: Minor At the moment, when someone implements a UserType, the bound parameters won't be displayed in not explicitly displayed via loggers. For example, here is what the code of NullableType.nullSafeGet() is : public final void nullSafeSet(PreparedStatement st, Object value, int index) throws HibernateException, SQLException { try { if ( value == null ) { if ( IS_TRACE_ENABLED ) { log().trace( "binding null to parameter: " + index ); } st.setNull( index, sqlType() ); } else { if ( IS_TRACE_ENABLED ) { log().trace( "binding '" + toString( value ) + "' to parameter: " + index ); } set( st, value, index ); } } catch ( RuntimeException re ) { log().info( "could not bind value '" + toString( value ) + "' to parameter: " + index + "; " + re.getMessage() ); throw re; } catch ( SQLException se ) { log().info( "could not bind value '" + toString( value ) + "' to parameter: " + index + "; " + se.getMessage() ); throw se; } } IMO, it would be quite a good thing to provide some method in Hibernate, something like logBoundParameter() that would do the log like above : > log().trace( "binding '" + toString( value ) + "' to parameter: " + index ); This method could then be just called by implementors so as to guaranty the display is always the same about bound parameters. Even more, I think it should use a special logger, just like the org.hibernate.SQL one to display this parameters. In fact, at the moment, I feel the reference documentation is not very clear about this : see http://www.hibernate.org/hib_docs/v3/reference/en/html/session-configurat.... It says : > org.hibernate.type Log all JDBC parameters But that's not completely true: it will only log bound parameters that are parameters typed with standard types coming from the org.hibernate.type package. Any custom UserType won't display anything until you: 1) put the right log4j line for the package where your userType is located ; 2) think about explicitly logging those parameter values in your custom UserType (cf. my first point). I'm not sure I made myself totally clear,. If so, please let me know. If you think that would be worth an improvement, I'll give a look to provide a patch for this. Thanks a lot. -- 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

15 years, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1110) Support for abstract/concrete pairs of POJO generation for hbm2java

by Jeff Walker (JIRA)

Support for abstract/concrete pairs of POJO generation for hbm2java ------------------------------------------------------------------- Key: HBX-1110 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1110 Project: Hibernate Tools Issue Type: Patch Components: ant, hbm2java, reverse-engineer Affects Versions: 3.2.4 Beta1 Environment: Hibernate 3.3.1GA, DB2 8.2, ant 1.6.5, Java 5.0 b11, eclipse (myEclipse blue 7.0) on windows xp sp3 Reporter: Jeff Walker Priority: Minor Attachments: HibernateExt.patch I wanted hbm2java to be able to produce pairs of both abstract base classes and concrete classes for each POJO when reverse engineering. I altered the ant tasks to allow this syntax: <hbm2java ejb3="true" jdk5="true"> <base transform="{package-name}/base/{class-name}Base"/> <concrete transform="{package-name}/{class-name}"/> </hbm2java> I then extended the POJO exporter (used only when base or concrete are present). This new exporter takes the meta model and runs once for all components, and then twice for each entity. The first entity run is for the base classes. Using the meta property overrides in the exporter, I force the class to be abstract, and change the generated class name according to the "transform" attribute. I also save the name of the generated class name in a hash, mapped to the original name for use in the second phase. Then for the second run (still inside of the exporter), I force the generated class name (again via the "transform" attribute), and have the class extend the base class that was generated in the first phase. I also introduce two new variables into the template context: basePartOfPair and concretePartOfPair. Set to true or false for the respective phase. They default to false for when the regular exporter is used. In the templates I forced the properties to be protected (instead of private), and turned off the property generation for the concrete class. I have code in the method (exportPersistentClass) to override these at meta properties, but that didn't work, as those properties need to be set on the property level, not the class level. You may refer to the following forum post for more background: http://forum.hibernate.org/viewtopic.php?t=994243 Note that there is no test case for this functionality yet. I'm not sure where to put it or what to do with that, but I will keep looking at that. -- 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

15 years, 1 month

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2009