[Hibernate-JIRA] Created: (EJB-362) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
9:25 p.m.
JPA Max/Min aggregate functions do not return same state-field type when argument is a
java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: EJB-362
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-362
Project: Hibernate Entity Manager
Issue Type: Bug
Components: EntityManager
Affects Versions: 3.3.2.GA
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the exception
that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
9:29 p.m.
New subject: [Hibernate-JIRA] Moved: (ANN-743) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-743?page=co...
]
Emmanuel Bernard moved EJB-362 to ANN-743:
------------------------------------------
Affects Version/s: (was: 3.3.2.GA)
3.3.1.GA
Component/s: (was: EntityManager)
binder
Key: ANN-743 (was: EJB-362)
Project: Hibernate Annotations (was: Hibernate Entity Manager)
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: ANN-743
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-743
Project: Hibernate Annotations
Issue Type: Bug
Components: binder
Affects Versions: 3.3.1.GA
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
8:38 p.m.
New subject: [Hibernate-JIRA] Moved: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
Emmanuel Bernard moved ANN-743 to HHH-3320:
-------------------------------------------
Affects Version/s: (was: 3.3.1.GA)
3.3.0.CR1
Component/s: (was: binder)
core
Requires Release Note: [Affirmative]
Key: HHH-3320 (was: ANN-743)
Project: Hibernate3 (was: Hibernate Annotations)
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
2:07 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
Gail Badner commented on HHH-3320:
----------------------------------
Please attach a runnable test case (Java + mapping) that reproduces this issue.
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
1:07 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
josef updated HHH-3320:
-----------------------
Attachment: HibernateUnitTest.zip
Unit test and respective classes attached.
Under /test: hibernateunittest.timestampfault.HibernateTimestampTest
(creates some rows in the database during test setup and then executes the test.)
Under /src/META-INF: persistence.xml (modify according to your environment)
Under /dist/lib: all the libraries you should need.
Under /src: actual entity classes
hibernateunittest.timestampfault.Sender (the parent of the OneToMany relationship, also
defines the namedQuery that uses MAX() aggregate on timestamp)
hibernateunittest.timestampfault.PendingEvent (the child of the OneToMany, defines the
Timestamp member eventTime)
hibernateunittest.timestampfault.LastSenderEventTime (the aggregation class, intending to
represent a Sender and the last time he had an event)
If the eventTime is changed from Timestamp to Date everything works fine. If it is left to
javax.sql.Timestamp the following exception is occurring:
Stderr:
SEVERE: Unable to locate appropriate constructor on class
[hibernateunittest.timestampfault.LastSenderEventTime]
[cause=org.hibernate.PropertyNotFoundException: no appropriate constructor in class:
hibernateunittest.timestampfault.LastSenderEventTime]
18-Jun-2008 12:47:32 org.hibernate.impl.SessionFactoryImpl <init>
SEVERE: Error in named query: getLatestEventTimes
org.hibernate.hql.ast.QuerySyntaxException: Unable to locate appropriate constructor on
class [hibernateunittest.timestampfault.LastSenderEventTime] [SELECT NEW
hibernateunittest.timestampfault.LastSenderEventTime(p.sender.id, MAX(p.eventTime)) FROM
hibernateunittest.timestampfault.PendingEvent p GROUP BY p.sender.id ]
at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:31)
at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:24)
at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:59)
at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:235)
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.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:402)
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:352)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at
hibernateunittest.timestampfault.HibernateTimestampTest.<clinit>(HibernateTimestampTest.java:23)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:336)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766)
Stdout:
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: HibernateUnitTestPU]
Unable to build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at
hibernateunittest.timestampfault.HibernateTimestampTest.<clinit>(HibernateTimestampTest.java:23)
Caused by: org.hibernate.HibernateException: Errors in named queries: getLatestEventTimes
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
Attachments: HibernateUnitTest.zip
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
2:12 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
Max Rydahl Andersen commented on HHH-3320:
------------------------------------------
how about just doing the query and check the type ?
you are mixing in select new syntax which might have challenges about differentiating
between timestamp and datetime types.
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
Attachments: HibernateUnitTest.zip
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
2:24 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
josef commented on HHH-3320:
----------------------------
I am not sure if you are understanding the issue. What do you mean by 'doing the query
and check the type?'
Hibernate is correctly mapping javax.sql.Timestamp to Timestamp types in the database, and
creating them appropriately in the schema too. The type information is clearly
javax.sql.Timestamp everywhere. All the objects are referring to javax.sql.Timestamp.
Nowhere there is any type mixing or anything. It is the aggregate function MAX() which is
not mapping back the result to javax.sql.Timestamp.
Kindly refer to the original incident log for full details.
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
Attachments: HibernateUnitTest.zip
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
2:39 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
Max Rydahl Andersen commented on HHH-3320:
------------------------------------------
I'm saying you are mixing too many things into the test case to say it is actually MIN
that is causing a problem.
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
assumes that the select NEW uses the correct types to look it up - maybe it doesn't.
Do SELECT MAX(p.eventTime) FROM PendingEvent p WHERE p.recipient.id=? GROUP BY p.sender
ORDER BY MAX(p.eventTime) DESC
and assert what the returned result type actually is.
*then* your test would test for what your issue is stating.
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
Attachments: HibernateUnitTest.zip
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
2:58 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
josef commented on HHH-3320:
----------------------------
OK, it was me who wasnt understanding, in fact you are right.
select new(...) is the problem
The following test runs fine:
public static Object getLastSenderEventTime()
{
EntityManager em = emf.createEntityManager();
try
{
Query q = em.createQuery("SELECT MAX(p.eventTime) FROM PendingEvent p");
return q.getSingleResult();
}
finally
{
em.close();
}
}
@Test
public void testTimestampInAggregate()
{
Object o = getLastSenderEventTime();
System.out.println(o.getClass().getName());
System.out.println(o);
assertTrue(o instanceof Timestamp);
}
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
Attachments: HibernateUnitTest.zip
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
3:45 p.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
Max Rydahl Andersen resolved HHH-3320.
--------------------------------------
Resolution: Won't Fix
resolving as wont fix since there is a very trivial and portable workaround for it.
Reopen if JPA spec says otherwise.
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
Attachments: HibernateUnitTest.zip
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
3:50 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
josef commented on HHH-3320:
----------------------------
Yes, however keep in mind that it is very un-userfriendly. A user can go around in circles
for hours until he finds out what might be wrong since types are logically expected to be
preserved.
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
Attachments: HibernateUnitTest.zip
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
1:19 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3320) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320?page=c...
]
Gene Smith commented on HHH-3320:
---------------------------------
I agree with Josef... this was annoying to find and work around. And I dread the thought
that certain other people in my work group might have been the ones trying to find and
avoid it.
Here is a more nasty case, and my work around...
There was already a query with a sub-select, but the table is really big, and joins were
added to the query, so it would bog down the server. And I needed alternative results
where there were and were not parent records. And I needed to sort. And to join another
table... And grouping by virtual columns... And sorting by virtual columns...
Note: The max date is selected only to make it valid SQL, as it is being sorted by.
I wont claim that the "moderation" table is simple, but when you build
structures on top of structures... you don't get simple. And this query does run
fast:) And is relatively easy to understand.
Names changed to protect the guilty;)
SELECT
distinct coalesce(moderation.parentId, moderation.thisId),
MAX(CAST (moderation.date as bigint))
FROM
moderation
[and join(s)]
WHERE
moderation.type = ? and
moderation.status = ?
[and joined criteria]
GROUP BY
coalesce(moderation.parentId, moderation.thisId)
ORDER BY
max(CAST (moderation.date as bigint)) desc
JPA Max/Min aggregate functions do not return same state-field type
when argument is a java.sql.Timestamp
---------------------------------------------------------------------------------------------------------
Key: HHH-3320
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3320
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR1
Environment: JDK 1.6, Postgres 8.2, JDBC 4
Reporter: josef
Attachments: HibernateUnitTest.zip
According the JPQL specification, MAX and MIN aggregate functions should return the type
of the state-field to which they are applied. However, if one tries to query MAX or MIN on
a java.sql.Timestamp entity field and tries to populate a class which expects a
java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with
javax.persistence.PersistenceException. The result of MAX or MIN in this case are being
java.util.Date instead.
The error result in type mismatch should ideally also be more helpful, because it is very
difficult to understand what and where the problem is, unless you know about it
beforehand.
Here is an example Entity, with the aggregate class and query, together with the
exception that occurs:
...
import java.sql.Timestamp;
@Entity
@Table(name="pending_events")
public class PendingEvent implements Serializable
{
...
@Column(name="event_time", updatable=false, nullable=false)
private Timestamp eventTime;
...
}
import java.sql.Timestamp;
public class EventEntry
{
private String sender;
private Timestamp lastEventTime;
public EventEntry(String sender, Timestamp lastEventTime)
{
this.sender= sender;
this.lastEventTime = lastEventTime;
}
...
}
SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE
p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC
java.lang.ExceptionInInitializerError
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to
build EntityManagerFactory
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33)
Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
--
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
5618
days inactive
5887
days old
hibernate-issues@lists.jboss.org
11 comments
5 participants
participants (5)
-
Emmanuel Bernard (JIRA) -
Gail Badner (JIRA)
-
Gene Smith (JIRA)
-
josef (JIRA)
-
Max Rydahl Andersen (JIRA)