December 2008 - hibernate-issues - Jboss List Archives

[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

16 years, 6 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

16 years, 6 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

16 years, 6 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

16 years, 6 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3589) Sql generated for criteria intermittently causes "invalid identifier" error by assigning incorrect table alias to query elements

by Todd Currie (JIRA)

Sql generated for criteria intermittently causes "invalid identifier" error by assigning incorrect table alias to query elements -------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3589 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3589 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate Core 3.3.1.GA Oracle 10.02.03 JRE Q1.5.0_16-b02 Reporter: Todd Currie Application is encountering intermittent ORA-00904 "invalid identifier" errors in production and test build environment. Error occurs approximately 1:460 executions in the test build environment. In each occurence it happens with a different test, but when it occurs every criteria query generated for that test class fails. In production typically causes application to crash because of the unexpected exception thrown. The issue appears to be caused during construction of the CriteriaJoinWalker. The CriteriaLoader creates a CriteriaQueryTranslator that is responsible for the where condition and order by for non-projection queries (or additionally the select and group by for projection queries). The translator constructor is passed the CriteriaQueryTranslator.ROOT_SQL_ALIAS, "this_", which it uses for its rootSQLAlias. But when the CriteriaLoader next creates the CriteriaJoinWalker instance that is responsible for the rest of the query elements, it does not use the constructor that takes the root alias. The CriteriaJoinWalker then calls super(persister, factory, enabledFilters, alias); with a null passed in the alias parameter. The constructor in the parent class, AbstractEntityJoinWalker, calls generateRootAlias when the alias parameter is null. The method generateRootAlias is implemented both in the parent class JoinWalker and the child class CriteriaJoinWalker. To implement this form of polymorphism, java uses dynamic method binding to determine which method to call for the instance at run time. It appears that most of the time it calls the CriteriaJoinWalker implementation of generateRootAlias function which is hard coded to return CriteriaQueryTranslator.ROOT_SQL_ALIAS, "this_". The queries then generated by the CriteriaJoinWalker then execute correctly. But intermittently it calls the JoinWalker implementation which uses the passed in persistor's entityName to generate the table alias. This table alias that is then used for the rest of the query is different then the alias used by the CriteriaQueryTranslator and the resulting sql generates the invalid identifier error seen upon execution. This can be fixed in a number of ways. 1) pass the CriteriaQueryTranslator.ROOT_SQL_ALIAS into the constructor for the CriteriaJoinWalker. 2) make the generateRootAlias abstract in the JoinWalker (less reliable). 3) use an AbstractFactory pattern to construct the objects (more work). I have implemented #1 in our environment and am working on generating a clean test case to submit here. But for those who are interested here is the patch: ### Eclipse Workspace Patch 1.0 #P hibernate-core Index: src/main/java/org/hibernate/loader/criteria/CriteriaLoader.java =================================================================== --- src/main/java/org/hibernate/loader/criteria/CriteriaLoader.java (revision 15443) +++ src/main/java/org/hibernate/loader/criteria/CriteriaLoader.java (working copy) @@ -94,7 +94,8 @@ factory, criteria, rootEntityName, - enabledFilters + enabledFilters, + CriteriaQueryTranslator.ROOT_SQL_ALIAS ); initFromWalker(walker); Example stack trace: could not execute query; nested exception is org.hibernate.exception.SQLGrammarException: could not execute query org.springframework.dao.InvalidDataAccessResourceUsageException: could not execute query; nested exception is org.hibernate.exception.SQLGrammarException: could not execute query at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:615) at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:412) at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:424) at org.springframework.orm.hibernate3.HibernateTemplate.executeWithNativeSession(HibernateTemplate.java:374) at org.springframework.orm.hibernate3.HibernateTemplate.findByCriteria(HibernateTemplate.java:1051) at org.springframework.orm.hibernate3.HibernateTemplate.findByCriteria(HibernateTemplate.java:1044) at com.onstation.service.PersistenceServiceImpl.findByCriteria(Unknown Source) at com.onstation.service.MailingServiceTest.shouldFailToFindStateConversions(MailingServiceTest.java:52) Caused by: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:90) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2231) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306) at org.springframework.orm.hibernate3.HibernateTemplate$36.doInHibernate(HibernateTemplate.java:1061) at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:419) Caused by: java.sql.SQLException: ORA-00904: "THIS_"."SOURCE": invalid identifier at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:810) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:850) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1134) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3384) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1808) at org.hibernate.loader.Loader.doQuery(Loader.java:697) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) Example query: Hibernate: select stateconve0_.FAILEDID as FAILEDID311_0_, stateconve0_.CREATED as CREATED311_0_, stateconve0_.LOG as LOG311_0_, stateconve0_.SOURCE as SOURCE311_0_ from STATECONVERTFAILED stateconve0_ where this_.SOURCE=? -- 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

16 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2826) IS [NOT] NULL checks with component values

by Steve Ebersole (JIRA)

IS [NOT] NULL checks with component values ------------------------------------------ Key: HHH-2826 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2826 Project: Hibernate3 Issue Type: Improvement Components: query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.6, 3.3 Currently the HQL translator attempts to render IS NULL and IS NOT NULL checks against a component using tuple syntax. Would be much better to instead "explode" these. For example, consider Person with a name property which is a component type of Name and the HQL: "from Person p where p.name is null" Currently, we'd end up with SQL like: "... from person p where (p.f_name, p.l_name) is null" but the exploded form would make much more sense here: "... from person p where ( p.f_name is null and p.l_name is null )" -- 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

16 years, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-327) Capability to reuse IndexWriter instances across transactions

by Sanne Grinovero (JIRA)

Capability to reuse IndexWriter instances across transactions ------------------------------------------------------------- Key: HSEARCH-327 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-327 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Fix For: 3.1.1 don't close the IndexWriter but reuse it for the work on the next transaction. It is needed that this can be disabled for some configurations: create a new configuration parameter. -- 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

16 years, 6 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HBX-952) some way to generate DDL output

by Dan Allen (JIRA)

some way to generate DDL output ------------------------------- Key: HBX-952 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-952 Project: Hibernate Tools Issue Type: Improvement Components: eclipse Environment: Eclipse 3.2.2 Hibernate Tools beta10 Reporter: Dan Allen After diligent searching, I could not find a way to get the generated DDL for the current hibernate.dialect from the Hibernate Console in Eclipse. Either this feature isn't available, or it needs to be better documented so that someone can locate its whereabouts. What I am looking for is an output that looks like CREATE TABLE foo ( id bigint(20) unsigned NOT NULL auto_increment ) and so on... I would think this would be an "exporter", but no dice. -- 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

16 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-666) @SQLInsert does not work

by Alex (JIRA)

@SQLInsert does not work ------------------------- Key: ANN-666 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-666 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.2.1 Environment: hibernate-3.2.3.ga.zip, MySQL client version: 5.0.22, MSSQL 2005 Reporter: Alex http://forum.hibernate.org/viewtopic.php?p=2367176#2367176 @Entity @Table(name = "CONTACTS") @SQLInsert(sql="INSERT INTO CONTACT(FIRST_NAME, LAST_NAME) VALUES(upper('aaa'),upper('bbb'))") public class Contact { // ... } I've tried the both - sql-query and stored procedure inside the @SQLInsert. But the both not work for me. It looks like the @SQLInsert annotation is just ignored for some reason. Usual "insert into CONTACT (FIRST_NAME, LAST_NAME) values (?, ?)" statement is generated despite of the @SQLInsert annotation. At the same time other annotations (@NamedNativeQuery, @Loader) work ok for the class. How to make it works, please? Thanks a lot in advance. Hibernate version: hibernate-3.2.3.ga.zip Mapping documents: sessionFactory = new AnnotationConfiguration() .addPackage("model") .addAnnotatedClass(Contact.class) .addAnnotatedClass(SpaceShip.class) .setProperty("hibernate.dialect", "org.hibernate.dialect.MySQLMyISAMDialect") .setProperty("hibernate.connection.url", "jdbc:mysql://localhost/test") .setProperty("hibernate.connection.driver_class", "com.mysql.jdbc.Driver") .setProperty("hibernate.connection.username", "usname") .setProperty("hibernate.connection.password", "1231123") .setProperty(Environment.HBM2DDL_AUTO, "update") .setProperty(Environment.SHOW_SQL, "true") .setProperty("hibernate.cache.provider_class", "org.hibernate.cache.NoCacheProvider") .buildSessionFactory(); Code between sessionFactory.openSession() and session.close(): session = HibernateUtil.getSession(); session.beginTransaction(); session.saveOrUpdate(newContact); session.getTransaction().commit(); Full stack trace of any exception that occurs: None Name and version of the database you are using: MySQL client version: 5.0.22 The generated SQL (show_sql=true): Hibernate: insert into CONTACT (FIRST_NAME, LAST_NAME) values (?, ?) -- 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

16 years, 6 months

8
14
0 / 0

[Hibernate-JIRA] Created: (ANN-594) Filters for MappedSuperClass

by Shawn Clowater (JIRA)

Filters for MappedSuperClass ---------------------------- Key: ANN-594 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-594 Project: Hibernate Annotations Issue Type: New Feature Components: binder Affects Versions: 3.3.0.ga Reporter: Shawn Clowater Priority: Minor Based on discussion from http://forum.hibernate.org/viewtopic.php?t=963539&start=0 Essentially, it would be nice to be able to define filters on a MappedSuperClass and have them 'trickle down' to the subclasses. (at the class level - not sure if property level filters are carried down right now). I see the MappedSuperClass as a means to define generic behaviour (common columns, etc) and I think it makes sense for the filters to play nicely as well. In addition, I don' t know if it is already a separate JIRA request, filters off of an Interface would be fantastic as well as our application is using filters heavily and are always looking at ways to reduce the amount of filter annotations that we have to spread around. Right now, we're either forced to copy filter annotations all over the place OR we've actually been a bit sneaky and have tapped into custom persisters to dynamically apply common filters. However, there is a separate issue based on the order that entity persisters are built. -- 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

16 years, 6 months

3
4
0 / 0

[Hibernate-JIRA] Created: (ANN-752) Setup continous integration

by Hardy Ferentschik (JIRA)

Setup continous integration --------------------------- Key: ANN-752 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-752 Project: Hibernate Annotations Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Priority: Minor Hibernate Annotations should be build continuously via Hudson. If possible each build should run the tests against multiple databases. -- 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

16 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-753) Allow running tests against different databases by using a simple switch

by Hardy Ferentschik (JIRA)

Allow running tests against different databases by using a simple switch ------------------------------------------------------------------------ Key: ANN-753 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-753 Project: Hibernate Annotations Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Priority: Minor Currently you have to edit hibernate.properties to be able to run the tests against a different database. The settings of this file should be externalized and filters should be used to filter appropriate settings according to a property, eg 'ant clean junit -Dtargetdb=mysql'. To make this really useful one would also need a way within the test to skip it for a particular database. Some tests don't make sense against a certain target db. This might be a separate issue. Maybe one could switch to Junit 4 and add some custom annotation for enabling/disabling a test depending on the db. -- 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

16 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2412) Hibernate 3 cannot be compiled under JDK 6

by Ahmet A. Akin (JIRA)

Hibernate 3 cannot be compiled under JDK 6 ------------------------------------------ Key: HHH-2412 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2412 Project: Hibernate3 Type: Task Components: core Versions: 3.2.1, 3.2.2 Environment: windows xp, JDK 6 Reporter: Ahmet A. Akin Hibernate code cannot be compiled under JDK 6. Problems and possible solutions: 1- org.hibernate.jdbc.ResultSetWrapper implements ResultSet. But in Java 6, there are big changes in Resultset interface, and maybe 20+ more methods needs to be implemented in the ResultSetWrapper class. i would suggest eliminating this wrapper class once and for all, because it is only used in one method (in ColumnNameCache, getIndexForColumnName method) and i dont think there is a justification for using that wrapper class. 2- org.hibernate.lob.SerializableBlob needs to implement new Blob interface methods: public void free() throws SQLException; public InputStream getBinaryStream(long pos, long length) throws SQLException But, if this class is publicly accesible or used by API's back compatibility issues needs to be checked. 3- Same as number 2, org.hibernate.lob.BlobImpl class needs to implement new Blob methods. 4- org.hibernate.lob.SerializableClob class needs to implent new Clob methods. 5- org.hibernate.lob.ClobImpl , same as 4. In fact, Java 6 has a lot of JDBC improvements, maybe a java6 special extra package can be created., but that is a whole different issue. -- 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

16 years, 6 months

8
18
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-246) Run optimize at the end of the transaction even if flushToIndexes() is used

by Emmanuel Bernard (JIRA)

Run optimize at the end of the transaction even if flushToIndexes() is used --------------------------------------------------------------------------- Key: HSEARCH-246 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-246 Project: Hibernate Search Issue Type: Improvement Components: optimizer Reporter: Emmanuel Bernard Fix For: 3.1.0 I am not sure if it's easily feasible but it should be the case. I am mentioning as the feature in the book for now. -- 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

16 years, 6 months

3
11
0 / 0

[Hibernate-JIRA] Created: (ANN-786) Filters on collections are ignored

by Eric Ford (JIRA)

Filters on collections are ignored ---------------------------------- Key: ANN-786 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-786 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.2.0.ga Environment: Hibernate 3.2; MySql 5.0.51a; Java 1.6 Stand-alone app - no server Reporter: Eric Ford I have two classes: Topic and Narrative. A topic has one-to-many narratives. I want to impose a filter such that only narratives with a particular state value are returned when I look up a topic. @Entity public class Topic { //unrelated attributes not shown private Set<Narrative> narratives = new HashSet<Narrative>(); @OneToMany(mappedBy="topic") @Filter(name="byState", condition=":state = state") public Set<Narrative> getNarratives() { return narratives; } public void setNarratives(Set<Narrative> narratives) { this.narratives = narratives; } } @Entity @FilterDef(name="byState", defaultCondition=":state = state", parameters=@ParamDef(name="state",type="string")) @Filter(name="byState", condition=":state = state") public class Narrative { private String content = ""; private String state = ""; private Topic topic = null; //getters and setters not shown } @Test public void FindSystemById(){ //for this test, the indicated topic has two narratives, //one is "published" and the other is "draft" session.enableFilter("byState").setParameter("state", "published"); Topic result = null; result = TopicDao.findById(new Long(1), noLock); // assertNotNull(result); //this always passes, as expected System.out.println(result.getNarratives().size(); //this always returns 2 assertTrue(result.getNarratives().size() == 1); //this always fails, obviously } The sql code does not show the filter being applied when fetching the collection. I've tried variations including adding the @Filter annotation to the getNarratives() method only and adding the @Filter annotation to the Narrative class only. I've also tried putting the @FilterDef annotation on the Topic class instead of the Narrative class. None of these variations has given the desired result of only one narrative returned from the getNarratives() method. I am coding with Java 1.6, Hibernate 3.2, and MySql 5.0.51a using Eclipse 3.4 and testing with JUnit 4. -- 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

16 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3580) import entitymanager into core as a module

by Steve Ebersole (JIRA)

import entitymanager into core as a module ------------------------------------------ Key: HHH-3580 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3580 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Hardy Ferentschik Fix For: 3.4 -- 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

16 years, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2967) Cast to date in Formula still doesn't work

by Frederic Leitenberger (JIRA)

Cast to date in Formula still doesn't work ------------------------------------------ Key: HHH-2967 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2967 Project: Hibernate3 Issue Type: Bug Components: query-criteria, query-hql, query-sql Affects Versions: 3.2.5 Environment: Hibernate-Version: 3.2.5.ga Oracle 9i/10g Reporter: Frederic Leitenberger Priority: Minor Similar to HHH-473. Oracle 10g supports trunc(TS). (TS is a timestamp) Oracle 9i only supports trunc(cast(TS as date)) [and 10g supports this still too]. Therefore i need to add the cast to the Forumla. @Basic @Column(nullable = false, updatable = false) @Temporal(TemporalType.TIMESTAMP) public Date getCreated() { return created; } public void setCreated(Date created) { this.created = created; } @Formula(value = "trunc(cast(created as date))") public Date getDate() { return date } public void setDate(Date date { this.date= date } This results in the following query: select eventlog0_.id as id9_0_, eventlog0_.created as created9_0_, ......... trunc(cast(eventlog0_.created as eventlog0_.date)) as formula6_0_ from ICCS6.EventLog eventlog0_ where eventlog0_.id=? The alias in front of "date" is obviously misplaced there. I also tried renaming the formula (since it was called "date"), but this didn't change the result. -- 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

16 years, 7 months

5
7
0 / 0

[Hibernate-JIRA] Created: (ANN-764) Split test involving database specific features (like sequence / identity)

by Emmanuel Bernard (JIRA)

Split test involving database specific features (like sequence / identity) -------------------------------------------------------------------------- Key: ANN-764 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-764 Project: Hibernate Annotations Issue Type: Improvement Reporter: Emmanuel Bernard Priority: Minor Use the dialect unit test framework and split platform dependent tests -- 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

16 years, 7 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3236) Prevent classloader leaks to JBC and JGroups when using a shared cache

by Brian Stansberry (JIRA)

Prevent classloader leaks to JBC and JGroups when using a shared cache ---------------------------------------------------------------------- Key: HHH-3236 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3236 Project: Hibernate3 Issue Type: Sub-task Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.3.0 JGroups spawns a number of threads when a channel is created. JBC can spawn an eviction thread as well. A newly spawned thread inherits its thread context classloader from the thread that spawned it. If a shared JBC CacheManager is used (e.g. in an appserver) it is important to set the TCCL away from any application classloader and to the CacheManager's TCCL before starting a cache. This ensures that the application classloader doesn't leak to any JBC or JGroups threads. -- 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

16 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-593) Ability for an @NamedQuery on a @MappedSuperclass to be copied up to the subclass

by John Newman (JIRA)

Ability for an @NamedQuery on a @MappedSuperclass to be copied up to the subclass --------------------------------------------------------------------------------- Key: ANN-593 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-593 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.2.1 Environment: INFO Version:15 - Hibernate Annotations 3.2.1.GA 09:15:01,755 INFO Environment:500 - Hibernate 3.2.1 INFO SettingsFactory:81 - RDBMS: Microsoft SQL Server, version: 08.00.0760 09:15:06,114 INFO SettingsFactory:82 - JDBC driver: jTDS Type 4 JDBC Driver for MS SQL Server and Sybase, version: 1.2 09:15:06,255 INFO Dialect:151 - Using dialect: org.hibernate.dialect.SQLServerDialect Reporter: John Newman If I use a @MappedSuperclass (which is a very useful annotation btw) I have to manually copy any queries I want with taht class up to all subclasses. The binder should check any mapped superclasses and pull those named queries up. i.e. /** * Base User class that different projects user classes derive from. * Hibernate annotations doesn't pick up that query, so you have to copy it up to your subclass */ @MappedSuperclass @NamedQueries({ @NamedQuery(name="User.findByLoginName", query="FROM User WHERE loginName = ?") // this is useless down here, i just put it here for reference }) public class BaseUser<PK extends Serializable> extends IdEntity<PK> { private static final long serialVersionUID = -4443522925041212381L; protected String loginName; @Column(unique=true) public String getLoginName() { return this.loginName; } public void setLoginName(String loginName) { this.loginName = loginName; } } /** * Custom user class for a certain application */ @Entity @Table(name="tbl_user") @GenericGenerator(name=IdGen.NAME, strategy=IdGen.AUTO) @NamedQueries({ @NamedQuery(name="User.findByLoginName", query="FROM User WHERE loginName = ?") // had to copy this up from the base class }) public class User extends BaseUser<Short> { private static final long serialVersionUID = -6199544722824321999L; private String firstName; ... } so in short it would be nice if the scanner would check for that and bind any named queries up to the subclass -- 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

16 years, 7 months

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3000) Allow a TypeDef to be associated with a class

by Darren Bell (JIRA)

Allow a TypeDef to be associated with a class --------------------------------------------- Key: HHH-3000 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3000 Project: Hibernate3 Issue Type: Improvement Reporter: Darren Bell This would allow you to just define it once and not have to worry about adding extra details to the mapping file or by annotating a field. For instance: @TypeDef( name="internalHeaderType", typeClass=com.dolby.mapics.GenericEnumUserType.class, targetClass=com.dolby.mapics.InternalHeaderType, parameters= { @Parameter(name="enumClass", value="com.dolby.mapics.InternalHeaderType"), @Parameter(name="identifierMethod", value="toString"), @Parameter(name="valueOfMethod", value="fromString") }) by adding the targetClass attribute would enable this. -- 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

16 years, 7 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2326) NullPointerException from merge on composite id

by Greg Adams (JIRA)

NullPointerException from merge on composite id ----------------------------------------------- Key: HHH-2326 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2326 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1ga, tested against Oracle 10g and Derby Reporter: Greg Adams Priority: Critical Attachments: HibernateMergeBug.zip Merge is throwing an NPE from the bowels of Hibernate when I have a class mapped with a composite ID. Stacktrace: [junit] java.lang.NullPointerException [junit] at org.hibernate.type.AbstractType.getHashCode(AbstractType.java:112) [junit] at org.hibernate.type.AbstractType.getHashCode(AbstractType.java:120) [junit] at org.hibernate.type.EntityType.getHashCode(EntityType.java:279) [junit] at org.hibernate.type.ComponentType.getHashCode(ComponentType.java:189) [junit] at org.hibernate.engine.EntityKey.generateHashCode(EntityKey.java:104) [junit] at org.hibernate.engine.EntityKey.<init>(EntityKey.java:48) [junit] at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:100) [junit] at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:687) [junit] at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:669) [junit] at org.hibernate.engine.CascadingAction$6.cascade(CascadingAction.java:245) [junit] at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268) [junit] at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216) [junit] at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) [junit] at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:296) [junit] at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:242) [junit] at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:219) [junit] at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) [junit] at org.hibernate.engine.Cascade.cascade(Cascade.java:130) [junit] at org.hibernate.event.def.AbstractSaveEventListener.cascadeAfterSave(AbstractSaveEventListener.java:437) [junit] at org.hibernate.event.def.DefaultMergeEventListener.entityIsTransient(DefaultMergeEventListener.java:194) [junit] at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:123) [junit] at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:53) [junit] at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:677) [junit] at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:661) [junit] at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:665) [junit] at com.foo.test.HibernateTest.doMerge(Unknown Source) [junit] at com.foo.test.HibernateTest.testInsert(Unknown Source) [junit] at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) [junit] at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) [junit] at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) [junit] at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) [junit] at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) [junit] at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71) [junit] at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) [junit] at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) [junit] at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) [junit] at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) [junit] at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:32) I've attached a zipped-up project that reproduces the error. Just extract and run ant. -- 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

16 years, 7 months

11
13
0 / 0

[Hibernate-JIRA] Created: (ANN-626) @Generated annotation not inserting during insert

by Rob (JIRA)

@Generated annotation not inserting during insert ------------------------------------------------- Key: ANN-626 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-626 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga, 3.2.0.ga Environment: MSSQL 9.00.3042.00 Hibernate annotations version 3.2.0 GA and also tested 3.30 GA Reporter: Rob Priority: Critical The @Generated annotation is not working similiar to the hbm generated tag. Annotation Mapping: @Generated(GenerationTime.INSERT) @Column (name="CreatedOn", length=23, nullable=false, insertable=false, updatable=false) private Date mCreatedOn; Mapping Document: <property name="createdOn" generated="insert" type="TimestampType"> <column name="CreatedOn" length="23"/> </property> The generated SQL (show_sql=true): Hibernate: insert into Zone (CreatedByUserID, ZoneDescription, ZoneFile, ModifiedByUserID, ModifiedOn, ZoneName, RowStatus, SOAExpire, SOAMinimum, SOARefresh, SOARetry, SOAWho, ZoneTTL, ZoneType, ZoneClass) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) Debug level Hibernate log excerpt: 18:37:42 WARN org.hibernate.util.JDBCExceptionReporter 77 SQL Error: 515, SQLState: 23000 18:37:42 ERROR org.hibernate.util.JDBCExceptionReporter 78 Cannot insert the value NULL into column 'CreatedOn', table 'DB.dbo.Zone'; column does not allow nulls. INSERT fails. -- 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

16 years, 7 months

8
20
0 / 0

[Hibernate-JIRA] Created: (HHH-2597) Criteria API should handle entity aliases

by Emmanuel Bernard (JIRA)

Criteria API should handle entity aliases ----------------------------------------- Key: HHH-2597 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2597 Project: Hibernate3 Issue Type: Improvement Components: query-criteria Reporter: Emmanuel Bernard Priority: Minor HQL takes entity alias into account Criteria does not seem to do so "I'm trying to use @Entity(name="Test") to map a very simple pojo, but hibernate seems to ignore entity name, ie.: session.createCritirea("Test").list() throws "org.hibernate.MappingException: Unknown entity: Test" but session.createCritirea(myPojoClassName).list() works. " http://forum.hibernate.org/viewtopic.php?p=2350219 -- 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

16 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HBX-970) POJO generation should have full contructor as an option

by Alberto A. Flores (JIRA)

POJO generation should have full contructor as an option -------------------------------------------------------- Key: HBX-970 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-970 Project: Hibernate Tools Issue Type: Bug Components: hbm2java, reverse-engineer Affects Versions: 3.2beta9 Environment: Hibernate3, Oracle 10g Reporter: Alberto A. Flores When using hbm2java (for reverse engineering the database to generate POJOs), there is no real way to declare full constructor generation as an option (which is not required in Hibernate anyway). In a large table, I found the error of "can't create a constructor with more than 255 parameters" (which could easily grow if you use inheritance). We had to fix the PojoContructors.ftl code to never generate that full contructor. Potential fixes: - Find a way to initialize the BasicPojoClass to initialize the needFullContructor using <property> in the hbm2java - Using the <property> feature within hbm2java, fix the PojoConstructor.ftl to check for a variable that is (optionally) visible by virtue of the <property> tag instead of always checking for "pojo.needFullConstructor" - Provide a way to replace BasicPojoClass as part of the hbm2java task. By default, this uses the hardcoded code to always use this template. -- 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

16 years, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-21) Should we enfore Validator instances cannot have their metadata changed?

by Emmanuel Bernard (JIRA)

Should we enfore Validator instances cannot have their metadata changed? ------------------------------------------------------------------------ Key: BVAL-21 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-21 Project: Bean Validation Issue Type: Task Components: spec-general 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

16 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-43) Open API to resolve list of constraints for a given group (resolving group sequences)

by Emmanuel Bernard (JIRA)

Open API to resolve list of constraints for a given group (resolving group sequences) ------------------------------------------------------------------------------------- Key: BVAL-43 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-43 Project: Bean Validation Issue Type: Bug Components: spec-general 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

16 years, 7 months

1
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-19) Clarify when the metadata API is needed

by Emmanuel Bernard (JIRA)

Clarify when the metadata API is needed --------------------------------------- Key: BVAL-19 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-19 Project: Bean Validation Issue Type: Improvement Components: ri-general Reporter: Emmanuel Bernard Priority: Minor I think I will add a note on the chapter describing metadata. If somehow the data can be injected in the bean, it's better to use the runtime validation. If this is not possible, the metadata is helpful. From the spec, JCA or Joe Six-Pack are both clients. -- 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

16 years, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-66) Consider using a MessageContext to simplify the MessageResolver API

by Emmanuel Bernard (JIRA)

Consider using a MessageContext to simplify the MessageResolver API ------------------------------------------------------------------- Key: BVAL-66 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-66 Project: Bean Validation Issue Type: Improvement Components: spec-general 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

16 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-9) Turn all raw types into generics

by Emmanuel Bernard (JIRA)

Turn all raw types into generics -------------------------------- Key: BVAL-9 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-9 Project: Bean Validation Issue Type: Bug Components: spec-general Reporter: Emmanuel Bernard Assignee: 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

16 years, 7 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3621) Assertion failure in MigrationTest

by Juraci Paixao Krohling (JIRA)

Assertion failure in MigrationTest ---------------------------------- Key: HHH-3621 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3621 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.3.x Environment: Oracle 9i/Oracle 10g/Sybase 12/MySQL and Branch_3_3 Reporter: Juraci Paixao Krohling The test testSimpleColumnAddition (org.hibernate.test.schemaupdate.MigrationTest) fails due to an assertion failure. It seems something related to the environment, but as the tests are running without changes from SVN, it needs to be fixed. The tests are running using to the profiles specified in the "testsuite" maven configuration file. Stack trace: junit.framework.AssertionFailedError: expected:<0> but was:<1> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:277) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:195) at junit.framework.Assert.assertEquals(Assert.java:201) at org.hibernate.test.schemaupdate.MigrationTest.testSimpleColumnAddition(MigrationTest.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at org.hibernate.junit.UnitTestCase.runBare(UnitTestCase.java:63) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- 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

16 years, 7 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2936) Unclear warning in the logs from LoadContexts.cleanup: fail-safe cleanup (collections)

by Anders Wallgren (JIRA)

Unclear warning in the logs from LoadContexts.cleanup: fail-safe cleanup (collections) -------------------------------------------------------------------------------------- Key: HHH-2936 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2936 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: MySQL 5.0 Reporter: Anders Wallgren We're seeing warning in our logs from this piece of code, but it's unclear from the warning message whether this indicates a problem in my code or in hibernate itself. The error message should be clarified. -- 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

16 years, 7 months

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-548) Joins break when using composite primary key classes

by Vincent Jenks (JIRA)

Joins break when using composite primary key classes ---------------------------------------------------- Key: ANN-548 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-548 Project: Hibernate Annotations Type: Bug Versions: 3.2.1, 3.2.2 Environment: JBoss 4.0.5.GA w/ Hibernate 3.2.2 and Annoations 3.2.2 (from SVN). Also reproduced w/ JBoss 4.0.5.GA w/ stock annotations, hibernate, and entity manager, unmodified. The attached test-case was run against MSSQL 2000 but is trivial to point at another database. The issue was also reproduced on a OpenEdge Progress 10.1A database. Reporter: Vincent Jenks Attachments: CarBean.java, Carz.java, Lotz.java Joins break when using composite primary key classes JBoss 4.0.5.GA w/ Hibernate 3.2.2 and Annoations 3.2.2 (from SVN). Also reproduced w/ JBoss 4.0.5.GA w/ stock annotations, hibernate, and entity manager, unmodified. The attached test-case was run against MSSQL 2000 but is trivial to point at another database. The issue was also reproduced on a OpenEdge Progress 10.1A database. In a case where there are composite keys on one (or each) side of a relationship, Hibernate cannot join the entities together if all of the primary key fields are not used in the relationship. A (very) simple example, two entities Carz and Lotz (pardon the names, it's simply cars and car lots): @Entity @Table(name="car") public class Carz implements Serializable { @Id private Integer id; @Column(name="make", nullable=false) private String make; @Column(name="model", nullable=false) private String model; @Column(name="manufactured", nullable=false) @Temporal(TemporalType.TIMESTAMP) private Date manufactured; @ManyToOne(fetch=FetchType.LAZY) @JoinColumns //Hibernate docs state that @JoinColumns must be used since Lotz has composite PK, a single @JoinColumn does not deploy anyhow ({ @JoinColumn(name="loc_code", referencedColumnName="loc_code", insertable=false, updatable=false) }) private Lotz lot; ........................... } @Entity @Table(name="lot") public class Lotz implements Serializable { @EmbeddedId protected LotzPK lotPK; @Column(name="name", nullable=false) private String name; @Column(name="location", nullable=false) private String location; @OneToMany(mappedBy="lot", fetch=FetchType.LAZY, cascade=CascadeType.ALL) private List<Carz> cars; ........................... } @Embeddable public class LotzPK implements Serializable { @Column(name="id", nullable=false) private Integer id; @Column(name="loc_code", nullable=false) private String locCode; ........................... } In this case I need a one-to-many relationship on Carz.id = Lotz.locCode. However, there doesn't appear to be a way to do this. When this is deployed, this exception occurs: org.hibernate.AnnotationException: Column name id of hqb.model.Lotz not found in JoinColumns.referencedColumnName at org.hibernate.cfg.annotations.TableBinder.bindFk(TableBinder.java:306) at org.hibernate.cfg.FkSecondPass.doSecondPass(FkSecondPass.java:64) at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:433) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:287) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1211) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:154) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:847) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:385) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor263.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) ........................... I can deploy the app if I map both fields in the Lotz PK class like so: @Entity @Table(name="car") public class Carz implements Serializable { @Id private Integer id; ........................... @ManyToOne(fetch=FetchType.LAZY) @JoinColumns ({ @JoinColumn(name="loc_code", referencedColumnName="loc_code", insertable=false, updatable=false), @JoinColumn(name="", referencedColumnName="id", insertable=false, updatable=false) //INCORRECTLY DEFINED RELATIONSHIP! }) private Lotz lot; ........................... } But obviously this is no good, it generates bad SQL at runtime: /* select c from Carz c left join fetch c.lot */ select carz0_.id as id198_0_, lotz1_.id as id199_1_, lotz1_.loc_code as loc2_199_1_, carz0_.make as make198_0_, carz0_.model as model198_0_, carz0_.manufactured as manufact4_198_0_, carz0_.lot_id as lot5_198_0_, carz0_.loc_code as loc6_198_0_, --no such column... lotz1_.name as name199_1_, lotz1_.location as location199_1_ from car carz0_ left outer join lot lotz1_ on carz0_.lot_id=lotz1_.id --oops! Hibernate defaulted a relationship here... and carz0_.loc_code=lotz1_.loc_code In reality, this is the SQL I'm trying to achieve, by repairing the above query manually: select carz0_.id as id198_0_, lotz1_.id as id199_1_, lotz1_.loc_code as loc2_199_1_, carz0_.make as make198_0_, carz0_.model as model198_0_, carz0_.manufactured as manufact4_198_0_, carz0_.loc_code as loc6_198_0_, lotz1_.name as name199_1_, lotz1_.location as location199_1_ from car carz0_ left outer join lot lotz1_ on carz0_.loc_code=lotz1_.loc_code This is consistent w/ the EJB 3.0 spec (and Glassfish+Toplink) but that's only because the spec doesn't define exacltly how to handle this. However, that being said, this seems important enough for Hibernate to be able to manage? -- 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

16 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3461) Enhance DialectFactory to support Sybase Adaptive Server Anywhere

by Jason Stern (JIRA)

Enhance DialectFactory to support Sybase Adaptive Server Anywhere ----------------------------------------------------------------- Key: HHH-3461 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3461 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6.GA, Sybase Adaptive Server Anywhere Reporter: Jason Stern Priority: Minor Currently, the org.hibernate.dialect.DialectFactory class has native support for Sybase Adaptive Server Enterprise (ASE), but throws the following exception when used with Sybase Adaptive Server Anywhere (ASA): "org.hibernate.HibernateException: Hibernate Dialect must be explicitly set for database: Adaptive Server Anywhere" I have manually set the dialect for now, but if you could add the following line of code to the DialectFactory class, it would help with future portability: MAPPERS.put( "Adaptive Server Anywhere", new VersionInsensitiveMapper( "org.hibernate.dialect.SybaseAnywhereDialect" ) ); Thanks for all your hard work! -- 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

16 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-11) Incorrect use of generics

by Emmanuel Bernard (JIRA)

Incorrect use of generics ------------------------- Key: BVAL-11 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-11 Project: Bean Validation Issue Type: Bug Components: ri-general Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik There is too many @SuppressWarning("unchecked") For a library using no legacy code, this should not happen. Some might be the fault of an improper Bean Validation generics design but I have seen incorrect uses of generics in the ri itself hidden by @SWs I will open specific reports for the one I have seen but the goal is to get rid of (almost) all @SuppressWarnings. -- 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

16 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2988) UnionSubclassEntityPersister.generateSubquery() does not use column.getQuotedName()

by benoit heinrich (JIRA)

UnionSubclassEntityPersister.generateSubquery() does not use column.getQuotedName() ----------------------------------------------------------------------------------- Key: HHH-2988 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2988 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Reporter: benoit heinrich Priority: Critical Hi all, I'm new to hibernate and I'm trying to use the Inheritance strategy TABLE_PER_CLASS with a Postgres database. The postgres database contains tables and column with upper cases names (names must be quoted). In the entity I used the back-quote ` sign to quote the table names and column names. All basic requests work but when I have an association going to the virtual parent table then I got an error due to the fact that the Union subclass entity persister does not quote the column names inside the sub query. I've locate the problem and I think it occurs here: org.hibernate.persister.entity.UnionSubclassEntityPersister.java (svn rev. 11398) line 395 ------------------------------------------------------------------------------------------------ while ( citer.hasNext() ) { Column col = (Column) citer.next(); if ( !table.containsColumn(col) ) { int sqlType = col.getSqlTypeCode(mapping); buf.append( dialect.getSelectClauseNullString(sqlType) ) .append(" as "); } buf.append( col.getName() ); buf.append(", "); But should be ------------------------------------------------------------------------------------------------ buf.append( col.getQuotedName() ); Here is an example to test: Item.java: --------------------------------- @Entity @Inheritance(strategy = InheritanceType.TABLE_PER_CLASS) public abstract class Item implements java.io.Serializable { private long id; private Container parent; /** getter / setter */ @Id @Column(name = "`ID`", unique = true, nullable = false, insertable = true, updatable = true) @GeneratedValue(strategy=GenerationType.SEQUENCE, generator = "item_id_seq_generator") @SequenceGenerator(name="item_id_seq_generator", sequenceName="item_id_seq", allocationSize=1) public long getId() { return this.id; } public void setId(long id) { this.id = id; } @ManyToOne(cascade = {}, fetch = FetchType.LAZY) @JoinColumn(name = "`ParentID`", unique = false, nullable = true, insertable = true, updatable = true) public Container getParent() { return this.parent; } public void setParent(Container parent) { this.parent = parent; } } Container.java --------------------------------- @Entity @Table(name = "`CoNTaiNeR`") public class Container extends Item { private Set<Item> items = new HashSet<Item>(0); @OneToMany(cascade = { CascadeType.ALL }, fetch = FetchType.LAZY, mappedBy = "parent", targetEntity = Item.class) public Set<Item> getItems() { return this.items; } public void setItems(Set<Item> items) { this.items = items; } } SimpleItem.java --------------------------------- @Entity @Table(name = "`SimpleItem`") public class SimpleItem extends Item { /*...*/ } So when you try to get the Container.getItems() then it generates the wrong query. Cheers, /Benoit -- 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

16 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-218) add indexAll( Class type ) to rebuild indexes from all data

by Sanne Grinovero (JIRA)

add indexAll( Class type ) to rebuild indexes from all data ----------------------------------------------------------- Key: HSEARCH-218 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-218 Project: Hibernate Search Issue Type: New Feature Reporter: Sanne Grinovero Assignee: Sanne Grinovero The implementation should be as efficient as possible, to cover this scenarios: * Developers change an entity and want to test the effect on the index structure, they want do to search experiments with the new fields. * A production system is up(down)graded to a new(old) release, involving index changes. (the system is "down for maintenance" but the speed is crucial) * Existing index is corrupted/lost. (Again, speed to recover is critical) * A Database backup is restored, or data is changed by other jobs. * Some crazy developer like me prefers to disable H.Search's event listeners for some reason. (I wouldn't generally recommend it, but have met other people who have a reasonable argument to do this) * A Lucene update breaks the index format (not so irrationale as they just did on trunk). -- 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

16 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3206) criteria.uniqueResult() is null when criteria.firstResult is NOT null when projection is count

by Will Hoover (JIRA)

criteria.uniqueResult() is null when criteria.firstResult is NOT null when projection is count ---------------------------------------------------------------------------------------------- Key: HHH-3206 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3206 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Environment: JBoss 4.0/JDK 1.6/Oracle 10g Reporter: Will Hoover Priority: Minor SYNOPSIS: "criteria.uniqueResult()" is null when criteria.firstResult is NOT null when projection is count. This happens regardless if using "criteria.setProjection(Projections.countDistinct(distinctPropertyName));" or "criteria.setProjection(Projections.rowCount())". The reason why the criterias firstResult is not null is because we are reusing the same criteria to perform "criteria.list()" as "criteria.uniqueResult()" to avoid having to set all of the same restrictions etc. twice. -- 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

16 years, 8 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-572) @Node(name=, embedXml=true|false) for DOM4J

by Emmanuel Bernard (JIRA)

@Node(name=, embedXml=true|false) for DOM4J ------------------------------------------- Key: ANN-572 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-572 Project: Hibernate Annotations Type: Improvement Components: binder 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

16 years, 8 months

7
18
0 / 0

[Hibernate-JIRA] Created: (ANN-684) Query with an IN Clause object that holds an Enum is failing with ORA-01722: invalid number (Criteria) OR ORA-17041: Missing IN or OUT parameter at index (HQL)

by Li Ho (JIRA)

Query with an IN Clause object that holds an Enum is failing with ORA-01722: invalid number (Criteria) OR ORA-17041: Missing IN or OUT parameter at index (HQL) --------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-684 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-684 Project: Hibernate Annotations Issue Type: Bug Components: search Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0 (cr4) Oracle Annotations Reporter: Li Ho I am trying to do a query with an IN clause. The object I am passing into the IN clause contains an Enum. I'm not 100% sure, but I think the Enum is causing the problem based on the resulting error message. When I use the Criteria API, I get the following error: ORA-01722: invalid number When I use the equivalent HQL, I get: ORA-17041: Missing IN or OUT parameter at index Here is some code (using criteria) that produces the error List<AccountKey> accountKeys; // AccountKey contains some Strings and an Enum ... List results = session.createCriteria(MyObject.class). add(Expression.in("key.account.key", accountKeys)). list(); The debug SQL looks right... and when I manually try it by replacing the ? params with valid values, it works! So, it seems like there's a problem with the passing of the query parameter values. I am currently working around this issue by bypassing the object comparison. I extract the variables I want to compare and force it to do a direct String comparison on those elements. -- 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

16 years, 8 months

3
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-74) Make sure Validator<T> is thread-safe in the RI

by Emmanuel Bernard (JIRA)

Make sure Validator<T> is thread-safe in the RI ----------------------------------------------- Key: BVAL-74 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-74 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft -- 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

16 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3161) No Dialect mapping for JDBC type: -4

by cyrus (JIRA)

No Dialect mapping for JDBC type: -4 ------------------------------------ Key: HHH-3161 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3161 Project: Hibernate3 Issue Type: Bug Components: core, query-hql, query-sql Affects Versions: 3.2.1 Environment: hibernate 3.2.1 + mysql Reporter: cyrus Priority: Critical When I execute the statement below: SELECT concat(case ip_protocol when 6 then 'TCP' when 17 then 'UDP' else 'OTHER' end, ', PORT ', repeat(' ', 5 - length(if(port is NULL, 0, port))), if(port is NULL, 0, port)) as protocol, concat(case ip_protocol when 6 then 'TCP' when 17 then 'UDP' else 'OTHER' end, if(port is NULL, 0, port)) as id, sum(byte_subtotal) as total FROM usage_sum_minute WHERE from_unixtime(time_min * 60) between '2008-02-03 14:00:00' and '2008-03-05 13:59:00' GROUP BY protocol ORDER BY total DESC LIMIT 0, 20 DB schema: CREATE TABLE `ascot`.`usage_sum_minute` ( `id` int(11) NOT NULL auto_increment, `igateway_id` smallint(5) NOT NULL, `time_min` int(11) NOT NULL, `user_name` varchar(255) default NULL, `mac_local` varchar(80) NOT NULL, `ip_local` bigint(20) NOT NULL, `ip_remote` bigint(20) NOT NULL, `ip_protocol` smallint(5) NOT NULL, `port` smallint(6) default NULL, `domain_name` char(80) default NULL, `url` varchar(1024) default NULL, `byte_subtotal` int(11) NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `id` (`id`), KEY `index_igateway` (`igateway_id`), KEY `index_protocol` (`ip_protocol`), KEY `index_minute` (`time_min`), KEY `index_user` (`user_name`), KEY `index_port` (`port`), KEY `index_ip` (`ip_remote`) ) ENGINE=InnoDB AUTO_INCREMENT=505699 DEFAULT CHARSET=latin1 It give an exception "No Dialect mapping for JDBC type: -4" -- 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

16 years, 9 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2767) TimestampType uses SimpleDateFormat, which does not include Timestamp nanoseconds

by Alan Krueger (JIRA)

TimestampType uses SimpleDateFormat, which does not include Timestamp nanoseconds --------------------------------------------------------------------------------- Key: HHH-2767 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2767 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Hibernate 3.2.2 Reporter: Alan Krueger Priority: Minor TimestampType uses SimpleDateFormat when storing the value as a string, which does not include java.sql.Timestamp's nanoseconds. This appears to mean that auto-flushes see Timestamp fields changing value when using EntityType.DOM4J when there is a nanosecond component to the timestamp. -- 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

16 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-751) Hibernate reports erroneous "possible typo error" for properties with protected accessor methods

by Stephen R. Saucier (JIRA)

Hibernate reports erroneous "possible typo error" for properties with protected accessor methods ------------------------------------------------------------------------------------------------ Key: ANN-751 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-751 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.3.0.ga Reporter: Stephen R. Saucier Priority: Minor Attachments: checkForOrphanProperties.patch According to the EJB3 spec, section 2.1.1 (Persistent Fields and Properties), "property accessor methods must be public or protected." However, the checkForOrphanProperties method of org.hibernate.cfg.annotations.reflection.EJB3OverridenAnnotationReader only looks for public methods (by virtue of the fact that it is using the getMethods method of Class. I believe that the checkForOrphanProperties method ought to look at the protected methods implemented in the entity class as well in order to eliminate the erroneous warning messages that are reported when using hibernate with protected property accessor methods. I've attached a patch which implements this additional behavior. -- 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

16 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1093) Missing inverseJoinColumn at ManyToMany relations with composite keys

by Nils Kelleter (JIRA)

Missing inverseJoinColumn at ManyToMany relations with composite keys --------------------------------------------------------------------- Key: HBX-1093 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1093 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.2, 3.2LATER Environment: Hibernate Tools version 3.2.2.Beta1 and 3.2.4.CR1-N200810300202, Oracle Database Reporter: Nils Kelleter Using the hbm2java tool for reverse engineering of database tables, the following problem exists: At ManyToMany relations with composite keys an inverseJoinColumn is missing. Wrong code: @ManyToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinTable(name = "ET_MANY_TO_MANY_COMP_MAPPING", joinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP1_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP11_ID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP2_ID", nullable = false, updatable = false) }) public Set<EtManyToManyComp2> getEtManyToManyComp2s() { return this.etManyToManyComp2s; } @ManyToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinTable(name = "ET_MANY_TO_MANY_COMP_MAPPING", joinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP2_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP22_ID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP1_ID", nullable = false, updatable = false) }) public Set<EtManyToManyComp1> getEtManyToManyComp1s() { return this.etManyToManyComp1s; } Correct code: @ManyToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinTable(name = "ET_MANY_TO_MANY_COMP_MAPPING", joinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP1_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP11_ID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP2_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP22_ID", nullable = false, updatable = false) }) public Set<EtManyToManyComp2> getEtManyToManyComp2s() { return this.etManyToManyComp2s; } @ManyToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinTable(name = "ET_MANY_TO_MANY_COMP_MAPPING", joinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP2_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP22_ID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP1_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP11_ID", nullable = false, updatable = false) }) public Set<EtManyToManyComp1> getEtManyToManyComp1s() { return this.etManyToManyComp1s; } For reproducing this, you can use the following Oracle SQL scripts: CREATE TABLE ET_MANY_TO_MANY_COMP1 ( ET_MANY_TO_MANY_COMP1_ID NUMBER, ET_MANY_TO_MANY_COMP11_ID NUMBER, FIELD VARCHAR2(10), PRIMARY KEY (ET_MANY_TO_MANY_COMP1_ID, ET_MANY_TO_MANY_COMP11_ID) ); CREATE TABLE ET_MANY_TO_MANY_COMP2 ( ET_MANY_TO_MANY_COMP2_ID NUMBER, ET_MANY_TO_MANY_COMP22_ID NUMBER, FIELD VARCHAR2(10), PRIMARY KEY (ET_MANY_TO_MANY_COMP2_ID, ET_MANY_TO_MANY_COMP22_ID) ); CREATE TABLE ET_MANY_TO_MANY_COMP_MAPPING ( FK_ET_MANY_TO_MANY_COMP1_ID NUMBER, FK_ET_MANY_TO_MANY_COMP11_ID NUMBER, FK_ET_MANY_TO_MANY_COMP2_ID NUMBER, FK_ET_MANY_TO_MANY_COMP22_ID NUMBER, FOREIGN KEY (FK_ET_MANY_TO_MANY_COMP1_ID,FK_ET_MANY_TO_MANY_COMP11_ID) REFERENCES ET_MANY_TO_MANY_COMP1(ET_MANY_TO_MANY_COMP1_ID,ET_MANY_TO_MANY_COMP11_ID), FOREIGN KEY (FK_ET_MANY_TO_MANY_COMP2_ID, FK_ET_MANY_TO_MANY_COMP22_ID) REFERENCES ET_MANY_TO_MANY_COMP2(ET_MANY_TO_MANY_COMP2_ID, ET_MANY_TO_MANY_COMP22_ID), PRIMARY KEY (FK_ET_MANY_TO_MANY_COMP1_ID,FK_ET_MANY_TO_MANY_COMP11_ID,FK_ET_MANY_TO_MANY_COMP2_ID,FK_ET_MANY_TO_MANY_COMP22_ID) ); -- 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

16 years, 9 months

5
9
0 / 0

[Hibernate-JIRA] Created: (ANN-657) @Enumerated(value=EnumType.STRING) for Maps (java.util.EnumMap) ?

by Michael Grünewald (JIRA)

@Enumerated(value=EnumType.STRING) for Maps (java.util.EnumMap) ? ----------------------------------------------------------------- Key: ANN-657 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-657 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.3.0.ga Environment: hibernate 3.2.4.sp1; PostgresSql 8.2 Reporter: Michael Grünewald Priority: Minor Hi, I faced the problem, that I can't enforce a String-Mapping for an enum type key of an Map. E.g.: Map<? extends Enum<?>, String> I would suppose to use an attribute for @MapKey to do that. E.g.: @MapKey (enumerated=EnumType.STRING) Please read the forum entry for more informations. http://forum.hibernate.org/viewtopic.php?t=97827 Greetings Michael -- 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

16 years, 9 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2603) Deprecate the Session.connection() method

by Steve Ebersole (JIRA)

Deprecate the Session.connection() method ----------------------------------------- Key: HHH-2603 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2603 Project: Hibernate3 Issue Type: Deprecation Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.4 Deprecate the Session.connection() method, in favor of a "JDBC work" API. Schedule for removal in 4.0 -- 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

16 years, 9 months

14
26
0 / 0

[Hibernate-JIRA] Created: (EJB-315) unnecessary update when merge managed entity

by Jifeng Liu (JIRA)

unnecessary update when merge managed entity -------------------------------------------- Key: EJB-315 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-315 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Hibernate Core 3.2.5.ga Hibernate Annotations 3.3.0 GA hsqldb Reporter: Jifeng Liu Attachments: testcase.zip If the entity in em.merge(entity) is managed entity, the merge operation should be ignored. However it issues a update statement in the test case even if there is no changes. In the test case, Parent entity has a list of Image entity with Many-To-Many relation. em.merge() somehow marks the list as dirty, which causes the update statement. The following is trace log of the test case. 07.20,23 INFO ASTQueryTranslatorFactory - Using ASTQueryTranslatorFactory 07.20,601 DEBUG SQL - /* insert test.Parent */ insert into Parent (updateDateTime, Parent_No) values (?, ?) 07.20,617 DEBUG SQL - /* insert test.Image */ insert into Image (name, imageNo) values (?, ?) 07.20,617 DEBUG SQL - /* insert collection row test.Parent.images */ insert into Parent_Image (Parent_Parent_No, images_ imageNo) values (?, ?) 07.20,632 DEBUG SQL - /* load test.Parent */ select parent0_.Parent_No as Parent1_0_0_, parent0_.updateDateTime as updat eDa2_0_0_ from Parent parent0_ where parent0_.Parent_No=? 07.20,648 DEBUG SQL - /* load collection test.Parent.images */ select images0_.Parent_Parent_No as Parent1_1_, images0_. images_imageNo as images2_1_, image1_.imageNo as imageNo1_0_, image1_.name as name1_0_ from Parent_Image images0_ left o uter join Image image1_ on images0_.images_imageNo=image1_.imageNo where images0_.Parent_Parent_No=? 07.20,679 DEBUG SQL - /* update test.Parent */ update Parent set updateDateTime=? where Parent_No=? and updateDateTime=? 07.20,679 DEBUG SQL - /* delete collection test.Parent.images */ delete from Parent_Image where Parent_Parent_No=? 07.20,679 DEBUG SQL - /* insert collection row test.Parent.images */ insert into Parent_Image (Parent_Parent_No, images_ imageNo) values (?, ?) -- 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

16 years, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3560) Assume entities relationships as unversioned by default

by Adam Warski (JIRA)

Assume entities relationships as unversioned by default ------------------------------------------------------- Key: HHH-3560 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3560 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141471 Assume that each relation between entities is unversioned unless entity is explicitly annotated with @Versioned. In current implementation if versioned entity has reference to non-versioned entity an MappingException is being thrown unless the @Unversioned annotation is used in appropriate field. If there is a lot of entities that are referenced but not versioned it requires to apply lot of @Unversioned annotations. This is quite error-prone while it is easy to forgot about some fields. I've suggest to treat each reference to entity as it is annotated with @Unversioned unless the entity is annotated with @Versioned. In other words treat entities ralationships as implicitly @Unversioned unless @Versioned is not set explicitly. -- 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

16 years, 9 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2830) Insert error ignored when using sybase generated identity column

by Martin van Dijken (JIRA)

Insert error ignored when using sybase generated identity column ---------------------------------------------------------------- Key: HHH-2830 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2830 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Hibernate 3.2.2, Sybase 12.5.3 Reporter: Martin van Dijken All our tables have a single database generated identity column. This column is specified in Sybase as: objectId numeric(12) identity A little while ago, Hibernate started throwing NonUniqueObjectExceptions upon insert of a certain object. It turns out, the insert statement could not possibly succeed as the value of one of the columns was larger than the database column. The error is however ignored because Hibernate generates a query: insert into objectTable (objectName, objectNumericErrorField) values (?,?) select @@ identity The value of objectNumericErrorField was larger than the database column allows. The insert statement would therefore fail. The select @@identity however would succeed, only because no new row was inserted it would return the previous ID. Hibernate then assumes the entire query worked fine and would assign the already assigned id to a different object. It would then check whether or not the id was already in use and throw a NonUniqueObjectException -- 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

16 years, 9 months

5
6
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 December 2008