May 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-757) Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl>

by Dan Ports (JIRA)

Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl> -------------------------------------------------------------------------------------------- Key: HBX-757 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-757 Project: Hibernate Tools Type: Improvement Components: ant Versions: 3.2beta7 Reporter: Dan Ports Priority: Minor The file name, delimiter, halt on error, and format options are provided by SchemaExport/<hbm2ddl> already, so it makes sense to add their functionality to SchemaUpdate as well. I'll submit a patch shortly. (Is this the right place to post this, since SchemaUpdate is in the Hibernate core SVN?) -- 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

17 years, 1 month

3
17
0 / 0

[Hibernate-JIRA] Created: (EJB-362) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp

by josef (JIRA)

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

17 years, 2 months

5
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2310) LazyInitializationException: Initializing many-to-one and one-to-one associations to a maximum of max-fetch-depth fails when using a SQLProjection on a Criteria generated Query

by Nico De Groote (JIRA)

LazyInitializationException: Initializing many-to-one and one-to-one associations to a maximum of max-fetch-depth fails when using a SQLProjection on a Criteria generated Query -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2310 Project: Hibernate3 Type: Bug Components: core Versions: 3.0.5 Reporter: Nico De Groote Priority: Critical Initializing many-to-one and one-to-one associations to a maximum of max-fetch-depth fails when using a SQLProjection on a Criteria generated Query Following scenario occurs. I have a max-fetch-depth = default value. I have a the following businessobject having the following associations. BO -> BO2 (One to one) BO -> list of BO3 (one to many) I want to query for BO objects with the where clause containing a condition on one of the properties of the BO3 objects. When I now generate my query via the Criteria API and having the following projection set to retrieve only my BO objects (and none of the outer joinables) Projection projection = Projections.sqlProjection( "{alias}." + primaryKeyColumn + " theObj__", new String[]{"theObj__"}, new Type[]{Hibernate.entity(BO.getClass())}); I get my BO objects but the BO2 object is not initialized, as it should ne because of the max-fetch-depth. When not using the Projection I do get the one-to-one relation (BO2 object) as the max-fetch-depth is default value, but the query takes too much time because of the non required properties for the outerjoinable associations in the select clause. It seams that the fetching of the many-to-one and the one-to-one associations for the max-fetch-depth is disabled when using projections. Or am I missing the point here? -- 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

17 years, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-703) @Past and @Future should support inclusive and exclusive boundaries

by Dan Allen (JIRA)

@Past and @Future should support inclusive and exclusive boundaries ------------------------------------------------------------------- Key: ANN-703 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-703 Project: Hibernate Annotations Issue Type: Improvement Components: validator Affects Versions: 3.3.1.CR1 Reporter: Dan Allen Fix For: 3.3.1 The @Future and @Past annotations do not offer a way to include the current date in the range, operating under the pretense of an exclusive boundary condition. The current date is often needed in the range. For instance, a registration date can be today or any time in the future. You might have recorded an observation today or any time in the past. My suggestion is to add an attribute named "inclusive" which implies that the current date is included. @Future(inclusive = true) @Past(inclusive = true) Feel free to use another name for the attribute. The default, of course, is false for backwards compatibility. -- 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

17 years, 2 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HV-49) Czech translation

by Petr Ferschmann (JIRA)

Czech translation ----------------- Key: HV-49 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-49 Project: Hibernate Validator Issue Type: Patch Affects Versions: 3.0.0.ga Reporter: Petr Ferschmann Attachments: DefaultValidatorMessages_cs.properties Here is czech translation of hibernate validator. It is against 3.0.0.GA. -- 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

17 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-44) Make Hibernate Validator multi-lingual

by Olle Hallin (JIRA)

Make Hibernate Validator multi-lingual -------------------------------------- Key: HV-44 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-44 Project: Hibernate Validator Issue Type: Improvement Affects Versions: 3.0.0.ga Reporter: Olle Hallin Hibernate Validator 3.0.0 is unfortunately useless in a multi-lingual web app, since it uses Locale.getDefault() for locating the validation message bundle. Each and every HTTP request can have a different locale, in it's own thread. Please add something in line with Spring's LocaleContextHolder (a ThreadLocal), which can be set early in the request handling chain. If not set, it could fall back to the platform's Locale.getDefault(). -- 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

17 years, 2 months

6
16
0 / 0

[Hibernate-JIRA] Created: (HV-52) unified unit testing pattern for standalone validators

by Sanne Grinovero (JIRA)

unified unit testing pattern for standalone validators ------------------------------------------------------ Key: HV-52 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-52 Project: Hibernate Validator Issue Type: Patch Affects Versions: 3.0.0.ga Reporter: Sanne Grinovero Priority: Minor Attachments: validator-testing-cleanup.patch Hi, I've seen some bugs in the validator I would like to help solving, but the main issue I've seen is that to write unittests the code is quite verbose; the consequence is that mission-critical code is well tested but most trivial code is untested. It looks like to me that most JIRA issues here are relevant to this "untested trivial" code... I would appreciate if you could apply this patch that greatly simplifies writing of unit tests for standalone validators, as I would like to send some more patches using this code to develop test-first. This affects only the "test" source, diffed from 3.0.0.GA, and includes some new testing of @NotEmpty and @Digits; I would add much more tests if you're not against it. With "standalone validators" i mean that this is not useful for graph/integration testing, just each validator on some property. Sanne -- 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

17 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-42) Reference Documentation: broken example

by Robert Spielmann (JIRA)

Reference Documentation: broken example --------------------------------------- Key: HV-42 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-42 Project: Hibernate Validator Issue Type: Bug Components: documentation Reporter: Robert Spielmann Priority: Trivial The Hibernate Validator Reference Guide (Hibernate Validator 3.0.0.GA) contains examples for writing custom annotations and validators, section 1.4 "writing your own constraints". There, it says that the class CapitalizedValidator implements Validator<Capitalized> and PropertyConstraint. The example class, however, does not implement the "apply" method. Thus, the example class does not compile. Additionally, the class "Capitalize" (containing constants like FIRST) is not defined anywhere. This leaves the example incomplete and thus - unless you quickly implement this class - unsuable for practical experiments. -- 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

17 years, 2 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HV-25) Generated DDL ignores Validator annotations on component fields and superclass fields

by Ben Anderson (JIRA)

Generated DDL ignores Validator annotations on component fields and superclass fields ------------------------------------------------------------------------------------- Key: HV-25 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-25 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 3.0.0.ga Environment: Windows XP, Hibernate 3.2.4.sp1, Hibernate Annotations 3.3.0.ga, Postgres, HSQL Reporter: Ben Anderson Attachments: model.zip The DDL generated for entities containing components or superclass properties does not reflect any Validator length restrictions or not-null constraints that have been defined on those component or superclass properties i.e. a component with a property containing the @Length(max = 50) and @NotNull annotation is generated as varchar(255) with nulls permitted (at the database level). I've posted a more detailed example to the forum at http://forum.hibernate.org/viewtopic.php?t=975612 Another example can be found at http://www.ibm.com/developerworks/web/library/j-hibval.html - the SQL generated when this schema is exported is: create table cc (id integer not null, fname varchar(255), mi varchar(255), lname varchar(255), addr1 varchar(255), addr2 varchar(255), city varchar(255), zipcode varchar(255), state_id varchar(255), cvv2 varchar(6) not null, expiration_date timestamp not null, type_id integer not null, num varchar(30) not null, customer_id integer not null, primary key (id)); create table customer (id integer not null, dob timestamp, phone varchar(255), fax varchar(255), email varchar(255), fname varchar(255), mi varchar(255), lname varchar(255), addr1 varchar(255), addr2 varchar(255), city varchar(255), zipcode varchar(255), state_id varchar(255), primary key (id)); The SQL should be: create table cc (id integer not null, fname varchar(30) not null, mi varchar(1), lname varchar(30) not null, addr1 varchar(50) not null, addr2 varchar(50), city varchar(50) not null, zipcode varchar(15) not null, state_id varchar(2) not null, cvv2 varchar(6) not null, expiration_date timestamp not null, type_id integer not null, num varchar(30) not null, customer_id integer not null, primary key (id)); create table customer (id integer not null, dob timestamp, phone varchar(13), fax varchar(13), email varchar(40), fname varchar(30) not null, mi varchar(1), lname varchar(30) not null, addr1 varchar(50) not null, addr2 varchar(50) not null, city varchar(50) not null, zipcode varchar(15) not null, state_id varchar(2) not null, primary key (id)); I've attached the relevant classes from this example. -- 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

17 years, 2 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HV-31) Support user defined Locale for the ResourceBundle

by Emmanuel Bernard (JIRA)

Support user defined Locale for the ResourceBundle -------------------------------------------------- Key: HV-31 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-31 Project: Hibernate Validator Issue Type: New Feature Components: 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

17 years, 2 months

2
1
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 May 2008