August 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-441) nullable=true is ONLY a hint for schema generation, but Hibernate uses it for validation

by Francisco Peredo (JIRA)

nullable=true is ONLY a hint for schema generation, but Hibernate uses it for validation ---------------------------------------------------------------------------------------- Key: EJB-441 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-441 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.2.GA Reporter: Francisco Peredo With the following JPA @Entity (note the @Basic(optional=true), @Column(nullable=false) at the getName method): @Entity public class Customer { private Long id; private String name; @Id @GeneratedValue(strategy=GenerationType.AUTO) public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Basic(optional=true) @Column(nullable=false) public String getName() { return name; } public void setName(String name) { this.name = name; } } And then the following test @Test public void persistCustomerInTransaction() throws Exception { factory = Persistence.createEntityManagerFactory(PERSISTENCE_UNIT_NAME); EntityManager em = factory.createEntityManager(); em.getTransaction().begin(); Customer customer = new Customer(); em.persist(customer);em.getTransaction().commit(); em.close(); } What exception should be the root cause of this problem? According to the spec @Column(nullable=false) is JUST a schema generation hint, and Hibernate should NOT use it for object level validation, so it should crash with a java.sql.SQLException as the root exception, and not with a org.hibernate.PropertyValueException thrown by org.hibernate.engine.Nullability.checkNullability. -- 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
4
0 / 0

[Hibernate-JIRA] Created: (EJB-384) JPQL Constructor Queries containing Timestamp cause exception

by Bjorn Beskow (JIRA)

JPQL Constructor Queries containing Timestamp cause exception ------------------------------------------------------------- Key: EJB-384 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-384 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Hibernate 3.3.1.GA, Derby, JDK1.5, Windows. Reporter: Bjorn Beskow Priority: Minor Attachments: hibernate-jpql-timestamp-bug.zip When a constructor JPQL query projects a Timestamp, it causes an org.hibernate.hql.ast.QuerySyntaxException: Unable to locate appropriate constructor. For example, given the following Entity: @Entity public class Employee { ... private Timestamp lastUpdatedAsTimestamp; ... } and the following Pojo for the constructor query: public EmployeeDto(String name, Timestamp lastUpdated) {...} the following query will throw an exception: String query = "SELECT new test.dto.EmployeeDtoUsingTimestamp(e.name, e.lastUpdatedAsTimestamp) " + "FROM Employee e ORDER BY e.name"; List<EmployeeDto> reportList = em.createQuery(query).getResultList(); java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: Unable to locate appropriate constructor on class [test.dto.EmployeeDto] [SELECT new test.dto.EmployeeDto(e.name, e.lastUpdated) FROM test.entities.Employee e ORDER BY e.name] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:601) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:96) at test.ConstructorQueryTest.testEmployeesQuery(ConstructorQueryTest.java:63) ... This problem has been reported before (see HHH-278), but the workaround is not a portable JPA solution (having the type Timestamp in the Entity and the type Date in the Pojo constructor is not in line with the Spec, and does not work in other JPA implementations). I have attached a minimal Maven project with a test case which highlights the problem. -- 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: (HHH-3911) Remove openConnection()/closeConnection() from Batcher interface

by Steve Ebersole (JIRA)

Remove openConnection()/closeConnection() from Batcher interface ---------------------------------------------------------------- Key: HHH-3911 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3911 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3.x, 3.5 All access to a session-scoped connection should go through ConnectionManager. And in fact AbstractBatcher does get its connection from ConnectionManager as well. Currently the Batcher open/close connection methods are only used during Isolator. Those uses can be replaced with direct calls to the ConnectionProvider. -- 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

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3804) Cleanup usage of deprecated APIs in testsuite (Session#find, etc)

by Steve Ebersole (JIRA)

Cleanup usage of deprecated APIs in testsuite (Session#find, etc) ----------------------------------------------------------------- Key: HHH-3804 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3804 Project: Hibernate Core Issue Type: Task Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3.x, 3.5 -- 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

1
3
0 / 0

[Hibernate-JIRA] Created: (HBX-951) Folder selection dialog should allow creating a new folder

by Dan Allen (JIRA)

Folder selection dialog should allow creating a new folder ---------------------------------------------------------- Key: HBX-951 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-951 Project: Hibernate Tools Issue Type: Improvement Components: eclipse Affects Versions: 3.2beta9, 3.2beta10 Environment: Eclipse 3.2.2 Hibernate Tools beta10 Reporter: Dan Allen Attachments: new_folder.png The folder selection dialog used by the Hibernate Code Generation... definition screen (Main tab, Output directory) does not allow creating new folders. The lack of this feature is very inconvenient. For instance, if I would like to export my schema to HTML documentation, I go into the tool to setup a new Exporter. But I cannot create a new folder to put the docs. So I have to quit the dialog, go create a new folder using the Eclipse File > New > Folder dialog. Then I have to go back into the tool and configure it to use this folder. The attached screenshot shows what I am looking for. -- 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: (HHH-2897) Adding support for use of sequence objects in DB2 V8 OS390

by Tobias Sternvik (JIRA)

Adding support for use of sequence objects in DB2 V8 OS390 ---------------------------------------------------------- Key: HHH-2897 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2897 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Environment: Hibernate Core 3.2.5ga, DB2 UDB V8 OS390 (Z/OS) Reporter: Tobias Sternvik Attachments: DB2390Dialect.java Since version 8 of DB2 sequence objects are supported on the OS390 platform. But, the syntax for use of sequences varies between OS390 platform and the "rest". For retreival of next value in DB2 OS390 the syntax is "select nextval for <theSequenceName> from sysibm.sysdummy1" while in the "rest" it is "values nextval for <theSequenceName>". There migt be the case that within AS/400 environment the syntax is imilar to OS390, but I have not verified this. Also other differences exists.. I've included a enhanced verion of DB2390Dialect.java that has been proven to work in DB2 mainframe environment. -- 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-201) IndexWriter settings meant for transactional operations won't be inherited by the settings meant for batch operations

by Sanne Grinovero (JIRA)

IndexWriter settings meant for transactional operations won't be inherited by the settings meant for batch operations --------------------------------------------------------------------------------------------------------------------- Key: HSEARCH-201 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-201 Project: Hibernate Search Issue Type: Deprecation Components: engine Reporter: Sanne Grinovero Priority: Minor Fix For: 3.2.0 Currently if a property has been set for "transaction" but not for "batch", the batch operation will use the same setting as defined in the transaction property; It appears to be a bit confusing and difficult to understand which settings are being set. Current inheritance is to be considered "deprecated" and will be disabled, please begin declaring both values independently. -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3529) ConnectionWrapper is not visible from class loader

by Vladimir Kralik (JIRA)

ConnectionWrapper is not visible from class loader --------------------------------------------------- Key: HHH-3529 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3529 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1, 3.2.6 Environment: SpringFramework 2.5.5, Hibernate 3.2.6 / 3.3.1, Tomcat 5.5, CommonJ Timer ( http://www.myfoo.de/commonj/ ) Reporter: Vladimir Kralik Attachments: hibernate-3.2.6_p2.patch Hibernate/Spring libraries are in app.war/WEB-INF/lib. Timer is configured as resources in Tomcat and his libraries are in $CATALINA_HOME/common/lib/. Function call from GUI works, but the same function called by timers gives this exception : org.springframework.transaction.CannotCreateTransactionException: Could not openHibernate Session for transaction; nested exception is java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader at org.springframework.orm.hibernate3.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:599) .... Caused by: java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581) at org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnectionProxy.java:67) at org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.java:163) at org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111) at org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359) at org.springframework.orm.hibernate3.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:510) It's the same bug as was in HHH-2215, but this is not resolved. I think, that the problem is extracting classloader from currentThread(). This is always not null, so the next test in method getProxyClassLoader() is always false. I my case, timer thread lives in top class loader, but hibernate libraries are inside application class loader. Attached patch removes classloader extracting from currentThread(). It works for my case. -- 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

9
12
0 / 0

[Hibernate-JIRA] Created: (ANN-748) @JoinColumn overrides scale and percision in ManyToOne map..

by Andrew C. Oliver (JIRA)

@JoinColumn overrides scale and percision in ManyToOne map.. ------------------------------------------------------------ Key: ANN-748 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-748 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.CR1 Environment: Postgresql but not Hypersonic (haven't tried other DBs, but suspect any real non-java db will replicate) Reporter: Andrew C. Oliver Attachments: patch.tar.gz http://forum.hibernate.org/viewtopic.php?t=987527 Since you asked nicely... This is a patch against your test cases. Sorry for the not patch style patch. It is against the latest download of Annotations (3.4.0.CR1). I'm on a hotel network that seems to really make SVN angry. There are 4 files: 1. Bunny has many 2. PointyTooth (teeth) 3. IdTest.java, only "testBlownPrecision" is new and "getMappings" includes the rabid bunny and teeth 4. UUIDGenerator - I wouldn't have included it but I couldn't find a decent way to autogenerate 128-bit keys. (The linked wikipedia article is amusing). You'll probably want to unzip these into the annotations root directory, then do the svn diff. Following this you may want to pretty print. As the test notes, it will FAIL with the @JoinColumn mapping and succeed if it is commented out. The failure notes a precision error. Obviously batching must be disabled to read it. If you look at the generated table it will have like NUMBER[19]. With JoinColumn commented out it is the expected NUMBER[128]. Thanks to PaaKow Acquah for finding this. If you want more details, I'll be a TacoMac having another Aventinus... -- 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: (EJB-461) Implement JPA 2.0 criteria apis (compiling)

by Steve Ebersole (JIRA)

Implement JPA 2.0 criteria apis (compiling) ------------------------------------------- Key: EJB-461 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-461 Project: Hibernate Entity Manager Issue Type: Sub-task Reporter: Steve Ebersole Assignee: Steve Ebersole -- 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

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 August 2009