August 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3955) Infinispan cache support

by Chris Bredesen (JIRA)

Infinispan cache support ------------------------ Key: HHH-3955 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3955 Project: Hibernate Core Issue Type: New Feature Components: caching (L2) Affects Versions: 3.3.1 Reporter: Chris Bredesen Assignee: Chris Bredesen Fix For: 3.3.x Provide a RegionFactory and related implementations that support JBoss Infinispan data grid. This request is tracked on the Infinispan JIRA here: https://jira.jboss.org/jira/browse/ISPN-6 -- 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, 5 months

3
7
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, 5 months

8
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3972) Adding FETCH FIRST and OFFSET support to DerbyDialect

by Evan Leonard (JIRA)

Adding FETCH FIRST and OFFSET support to DerbyDialect ----------------------------------------------------- Key: HHH-3972 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3972 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.3.1, 3.2.0.ga Reporter: Evan Leonard Attachments: Added_FETCH_FIRST_and_OFFSET_support_to_Derby_Dialect.patch I've add support to the DerbyDialect for its recent addition of a limit clause [1]. Attached is a patch for this addition. Thank you, Evan Leonard [1] - http://db.apache.org/derby/docs/10.5/ref/rrefsqljoffsetfetch.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
9
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, 5 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-367) Support only one kind of Similarity per index

by Sanne Grinovero (JIRA)

Support only one kind of Similarity per index --------------------------------------------- Key: HSEARCH-367 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-367 Project: Hibernate Search Issue Type: Bug Reporter: Sanne Grinovero Fix For: 3.2.0 pasted from the developer's list: Each time a new Document is added to the index, the similarity relevant to that entity is looked up from the pertaining documentBuilder and set to the indexwriter: AddWorkDelegate: Similarity similarity = documentBuilder.getSimilarity(); writer.setSimilarity( similarity ); writer.addDocument( work.getDocument(), analyzer ); So the analyzer is scoped per document, the similarity is globally set on the indexwriter. Does this make sense to update the similarity for each add operation type? This is a problem as I can't use two (more) threads to add documents to the same index. Is there a good use case for which someone might need a different Similarity implementation for different entities contained in the same index? I'd like to change that to an "illegal configuration". -- 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, 5 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-394) @ProvidedId gets ignored

by Hardy Ferentschik (JIRA)

@ProvidedId gets ignored ------------------------ Key: HSEARCH-394 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-394 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.1.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0 The check for the @ProvidedId has to be moved into the init() method of DocumentBuilderIndexedEntity -- 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, 5 months

1
2
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, 5 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, 5 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, 5 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, 5 months

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