March 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3825) Allow variable arguments in Session.createQuery(...)

by Ricardo Mayerhofer (JIRA)

Allow variable arguments in Session.createQuery(...) ---------------------------------------------------- Key: HHH-3825 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3825 Project: Hibernate Core Issue Type: Improvement Reporter: Ricardo Mayerhofer Priority: Minor I think variable arguments in createQuery would really simplify its syntax. E.g.: createQuery( "select from Clazz c where c.attribute = ?", value ); instead of Query query = createQuery( "select from Clazz c where c.attribute = ?" ); query.setParam( 0, value ); -- 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, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-310) Out of Mem on Sorted ScrollableResults

by Sanne Grinovero (JIRA)

Out of Mem on Sorted ScrollableResults -------------------------------------- Key: HSEARCH-310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-310 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.0.1.GA Environment: Java SE, 3.0.1.GA Reporter: Sanne Grinovero Fix For: 3.1.0 http://forum.hibernate.org/viewtopic.php?p=2400452 I think this is more appropriate for 3.1.1 Emmanuel said: "The implementation suffers several flows: - we do create an EntityInfo[] as big as the number of hits - we lazily load this array but we never release "old content" - we lazily load the content (ie objects) by window but we never release it Some Soft reference based cache can help." -- 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, 2 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3823) Obtain current revision entity by AuditReader

by Jan Ritzenhoff (JIRA)

Obtain current revision entity by AuditReader --------------------------------------------- Key: HHH-3823 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3823 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Jan Ritzenhoff Implement a new method in the AuditReader class, like: auditReader.getCurrentRevisionEntity(boolean create) The method would return the current revision entity, letting you to fill any of the custom fields. The create parameter would specify if a revision entity should be created, even if no audited entities have been modified. So you dont have to lookup anything in the RevisionListener and you can easy pass some revision-information from the front to the back. Based on forum discussion: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151959 -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2882) QueryKey.equals() returning false with distributed caching

by Daniel Campagnoli (JIRA)

QueryKey.equals() returning false with distributed caching ---------------------------------------------------------- Key: HHH-2882 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2882 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Reporter: Daniel Campagnoli We noticed some issues recently with the query cache when using Coherence as the cache provider. This was due to instances of org.hibernate.cache.QueryKey not being equal after being serialized then deserialized. The equals check was failing on the [ResultTransformer customTransformer] field which in our case had an instance of RootEntityResultTransformer (which comes from the field CriteriaSpecification.ROOT_ENTITY). This is because RootEntityResultTransformer doesnt override equals, so the check is done by reference equality. When the QueryKey has been serialized and deserialized out of the cache, the instance will always be different, so the equals check will fail. A fix for this to be implement equals for RootEntityResultTransformer (and possibly the other ResultTransformer's). I used the following which worked fine. public boolean equals(Object obj) { return obj != null && this.getClass() == obj.getClass(); } ps. I created HHH-1665 a while ago, a real simple fix, could that be looked at :) -- 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, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-107) Implement a Hibernate Core specifc implementation of TraversableResolver

by Hardy Ferentschik (JIRA)

Implement a Hibernate Core specifc implementation of TraversableResolver ------------------------------------------------------------------------ Key: HV-107 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-107 Project: Hibernate Validator Issue Type: Task Components: engine Affects Versions: 4.0.0.Alpha2 Reporter: Hardy Ferentschik -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3035) could not read column value from result set: MEDFAC1_14_0_; Invalid column name SQL Error: 17006, SQLState: null

by sanjeev singh (JIRA)

could not read column value from result set: MEDFAC1_14_0_; Invalid column name SQL Error: 17006, SQLState: null ---------------------------------------------------------------------------------------------------------------- Key: HHH-3035 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3035 Project: Hibernate3 Issue Type: Bug Components: core, query-criteria, query-hql, query-sql Affects Versions: 3.2.2 Environment: JDK5 , Hibernate Junit Test case,WIndows XP Reporter: sanjeev singh The following is my section of hibernate mapping file. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="gov.njdhss.hippocrates.ems.valueobjects"> <class name="HeprEmsMedfacFacilityVO" table="HEPR_MEDFAC"> <id name="medfacId" column="MEDFAC_ID" type="java.lang.Long"> <generator class="sequence"> <param name="sequence">HEPR_MEDFAC_SEQ</param> </generator> </id> <property name="medfacName" type="java.lang.String" column="MEDFAC_NAME" update="true" insert="true"> </property> <property name="facCode" type="java.lang.String" column="FAC_CODE" update="true" insert="true"> </property> </class> <sql-query name="allfacility"> <return alias="facilities" class="HeprEmsMedfacFacilityVO" > <return-property name="medfacName" column="MEDFAC_NAME"/> </return> <![CDATA[ select facilities.MEDFAC_NAME AS medfacName from HEPR_MEDFAC facilities ]]> </sql-query> </hibernate-mapping> I am trying to execute the query using the following client code: public List getAllFacility() { List listAllFacilities = null; listAllFacilities = getHibernateTemplate().findByNamedQuery( "allfacility"); return listAllFacilities; } The following is the error: Hibernate: select facilities.MEDFAC_NAME AS medfacName from HEPR_MEDFAC facilities - could not read column value from result set: MEDFAC1_14_0_; Invalid column name - SQL Error: 17006, SQLState: null - Invalid column name - Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml] - SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase] Any idea if it is a bug or there is any error in my code. -- 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, 2 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-554) NPE with @Id on @OneToOne

by Loïc Minier (JIRA)

NPE with @Id on @OneToOne ------------------------- Key: ANN-554 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-554 Project: Hibernate Annotations Type: Bug Versions: 3.2.1 Environment: Hibernate 3.2.2 GA, Hibernate Annotations 3.2.1, J2SE 1.6.0-b105 on Debian GNU/Linux sid, PostgreSQL 7.4 Reporter: Loïc Minier Priority: Minor Hi, (Note: I originally reported this on the forum, but the lack of response suggests this might be a bug in Hibernate Annotations or Hibernate; the forum topic is at: http://forum.hibernate.org/viewtopic.php?t=970823) I hope it's not a misuse of Hibernate, but I'm trying to use @Id on @OneToOne, and this causes the following NPE when running hbm2ddl: java.lang.NullPointerException at org.hibernate.util.StringHelper.qualify(StringHelper.java:264) at org.hibernate.cfg.OneToOneSecondPass.doSecondPass(OneToOneSecondPass.java:196) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1130) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:296) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:56) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:287) at org.hibernate.tool.ant.Hbm2DDLExporterTask.execute(Hbm2DDLExporterTask.java:45) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:171) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) What I'm trying to do at the application level is: Foo class and table long foo_id, primary key FooData fooData, nulllable=true FooData class and table foo_id references Foo(foo_id), nullable=false This is expressed in Java as: @Entity @Table(name = "foo") public class Foo { @Id @GeneratedValue @Column(name = "foo_id") Long id; @OneToOne(mappedBy = "foo", cascade = CascadeType.ALL) FooData fooData; ... @Entity @Table(name = "foo_data") public class FooData { @Id @OneToOne @JoinColumn(name = "foo_id", nullable = false) Foo foo; This causes a NPE here. If I use a real Id on FooData, e.g.: @Id @Column(name = "foo_data_id") Long id; it works, and I end up with: - foo_id in table foo as a primary key - foo_data_id in table foo_data as a primary key - foo_id in table foo_data not null - foo_id in table foo_data references foo_id in table foo I don't want a foo_data_id, I don't need it, hence the lack of it which leads to the NPE. Bye, -- 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, 2 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2669) Unequivocally map MySQL LOB types to the LONG variant

by Steve Ebersole (JIRA)

Unequivocally map MySQL LOB types to the LONG variant ----------------------------------------------------- Key: HHH-2669 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2669 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 MySQL differentiates different "sizes" of LOBs. Apparently, the smaller types offer no storage benefit nor performance gain. So we should consider mapping the LOB types in the MySQL dialect to the LON variants in all cases. The current setup causes truncation headaches for users, apparently unnecessarily. -- 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, 2 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HBX-1032) HibernateConsoleRuntimeException: "Could not load JPA Configuration" for JavaSE JPA project

by Donatas Ciuksys (JIRA)

HibernateConsoleRuntimeException: "Could not load JPA Configuration" for JavaSE JPA project ------------------------------------------------------------------------------------------- Key: HBX-1032 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1032 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.0.GA Environment: Eclipse 3.3.1.1, HibernateTools 3.2.0 GA, JDK 1.6.0_03 Reporter: Donatas Ciuksys Priority: Blocker I have Java SE (not EE) project in Eclipse with standard structure like: /src /META-INF/persistence.xml /bin ... I try to create new Hibernate Configuration in "Hibernate Configurations" pannel. I choose project, select JPA (jdk 1.5+) option, fill in persistence unit "InventorizacijaPU", check whether Classpath tab is OK (it contains my project). Press OK. Trying to expand configuration created, I get this exception: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:142) at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:496) at org.hibernate.console.ConsoleConfiguration.access$0(ConsoleConfiguration.java:484) at org.hibernate.console.ConsoleConfiguration$2.execute(ConsoleConfiguration.java:203) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:65) at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:185) at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:106) at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:38) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:97) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:103) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:196) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.hibernate.console.HibernateConsoleRuntimeException: Persistence unit not found: 'InventorizacijaPU'. at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:134) ... 11 more This is my persistence.xml: <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="InventorizacijaPU" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <class>lt.mitsoft.inventorizacija.domain.BuvimoVieta</class> <class>lt.mitsoft.inventorizacija.domain.Inventorizacija</class> <class>lt.mitsoft.inventorizacija.domain.Irasas</class> <class>lt.mitsoft.inventorizacija.domain.IrasuBlokas</class> <class>lt.mitsoft.inventorizacija.domain.Preke</class> <class>lt.mitsoft.inventorizacija.domain.Skanuotojas</class> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.DerbyDialect" />  <property name="hibernate.connection.url" value="jdbc:derby://localhost:1527/InventorizacijaDB" />  <property name="hibernate.connection.driver_class" value="org.apache.derby.jdbc.ClientDriver" /> <property name="hibernate.connection.username" value="admin" /> <property name="hibernate.connection.password" value="admin" /> <property name="hibernate.cache.provider_class" value="org.hibernate.cache.NoCacheProvider" />  </properties> </persistence-unit> </persistence> -- 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, 2 months

4
10
0 / 0

[Hibernate-JIRA] Created: (EJB-403) QueryTest - Native Query for Update using alias causes failure

by Juraci Paixao Krohling (JIRA)

QueryTest - Native Query for Update using alias causes failure -------------------------------------------------------------- Key: EJB-403 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-403 Project: Hibernate Entity Manager Issue Type: Patch Components: EntityManager Environment: PostgreSQL 8.2.3 and Entity Manager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: QueryTest.diff Even though it says in documentation that it supports table aliases in "update" clauses[1], the below test fails when using it. Removing the table alias is enough to make it successful. org.hibernate.ejb.test.QueryTest#testUpdateQuery [1] http://www.postgresql.org/docs/8.2/interactive/sql-update.html -- 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, 2 months

4
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2009