June 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-73) optimize() index every nth operations

by Emmanuel Bernard (JIRA)

optimize() index every nth operations ------------------------------------- Key: HSEARCH-73 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-73 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Priority: Minor See discussions in HSEARCH-11 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Commented: (ANN-122) Add natural-id annotation

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-122?page=co... ] Emmanuel Bernard commented on ANN-122: -------------------------------------- Hi Nicolás, sorry for the delay. The bug is marked for the next version, I'll check the patch when I'll work on it, hopefully soon. It seems OK, though. > Add natural-id annotation > ------------------------- > > Key: ANN-122 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-122 > Project: Hibernate Annotations > Issue Type: New Feature > Components: binder > Affects Versions: 3.1beta6 > Reporter: Mathias Bogaert > Priority: Minor > Fix For: 3.3.1 > > Attachments: natural-id-v2.patch, natural-id-v3.patch, natural-id.patch > > > HIbernate 3.0.5 introduced natural-id. Add this to Annotations, as a @NaturalId annotation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-292) Update dependency version for hibernate-commons-annotations (pom.xml)

by Anthony Whitford (JIRA)

Update dependency version for hibernate-commons-annotations (pom.xml) --------------------------------------------------------------------- Key: EJB-292 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-292 Project: Hibernate Entity Manager Issue Type: Improvement Affects Versions: 3.3.1.GA Reporter: Anthony Whitford Maven pom declares hibernate-commons-annotations 3.0.0.ga as dependency when 3.3.0.ga is available. <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-commons-annotations</artifactId> <version>3.0.0.ga</version> </dependency> http://mirrors.ibiblio.org/pub/mirrors/maven2/org/hibernate/hibernate-ent... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

3
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-1860) Autogeneration of primary keys for Sybase IDENTITY columns fails with latest jConn3 driver

by Nick Chalko (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1860?page=c... ] Nick Chalko commented on HHH-1860: ---------------------------------- This bug is fixed in EBF 13489. > Autogeneration of primary keys for Sybase IDENTITY columns fails with latest jConn3 driver > ------------------------------------------------------------------------------------------ > > Key: HHH-1860 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1860 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.2.0 cr1 > Environment: JBoss 4.0.4GA, Adaptive Server Anywhere 9, jConnect using com.sybase.jdbc3.jdbc.SybDriver / jConn3.jar > Reporter: Erica Kane > Priority: Minor > > Sybase provides an IDENTITY column which is very useful for autogenerating primary keys for entity beans. However, if version 6.05 of jConnect (the standard Sybase driver) is used, with com.sybase.jdbc3.jdbc.SybDriver, all inserts fail with a message that it was not possible to obtain the generated identity. > Changing the datasource configuration to use com.sybase.jdbc2.jdbc.SybDriver fixes the problem. > Hopefully this can be fixed -- I realize it may be Sybase's fault -- but if not, I hope this spares someone else the agony of figuring it out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-293) Unknown dependency jboss-common-core 2.0.4.GA

by Anthony Whitford (JIRA)

Unknown dependency jboss-common-core 2.0.4.GA --------------------------------------------- Key: EJB-293 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-293 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.1.GA Reporter: Anthony Whitford The pom for 3.3.1 GA references jboss-common-core as a dependency, but this is not available on Ibiblio: <dependency> <groupId>jboss</groupId> <artifactId>jboss-common-core</artifactId> <version>2.0.4.GA</version> ... </dependency> http://mirrors.ibiblio.org/pub/mirrors/maven2/org/hibernate/hibernate-ent... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

4
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-1951) Table using back-tick not passing validation on Oracle

by Matt Solnit (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1951?page=c... ] Matt Solnit commented on HHH-1951: ---------------------------------- It turns out this is a duplicate of HHH-1629. The upgrade to Hibernate 3.2.3 fixed the problem :-). > Table using back-tick not passing validation on Oracle > ------------------------------------------------------ > > Key: HHH-1951 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1951 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.1.3 > Environment: Client: Hibernate 3.1.3, Java 1.5.0_06, Mac OS X 10.4.7 > Database server: Windows XP SP2, Oracle XE > Reporter: Matt Solnit > > I have a table mapping that looks similar to the following: > <class name="User" table="`User`"> >  > Notice the back-ticks around the table name. > When I use Hibernate to create the schema for me, it correctly generates a table name called "User" (including the quote marks). But when I validate the schema, it cannot find the table and so validation fails. > I am thinking the problem is somewhere in org/hibernate/tool/hbm2ddl/DatabaseMetadata.getTableMetadata(). It tries to look for "USER", because OracleDatabaseMetaData.storesUpperCaseIdentifiers() returns true. But the code doesn't realize that quoted tables are a special case and it has to look for "User" instead. > Another symptom of the same problem is that if I generate a schema update script, it will attempt to re-create the existing table. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1951) Table using back-tick not passing validation on Oracle

by Matt Solnit (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1951?page=c... ] Matt Solnit commented on HHH-1951: ---------------------------------- The same issue exists with PostgreSQL, except that Jdbc3DatabaseMetaData.storesLowerCaseIdentifiers() returns true instead of storesUpperCaseIdentifiers(). I am using version 8.2.4 for Mac OS X, and JDBC driver version 8.2 Build 505. > Table using back-tick not passing validation on Oracle > ------------------------------------------------------ > > Key: HHH-1951 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1951 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.1.3 > Environment: Client: Hibernate 3.1.3, Java 1.5.0_06, Mac OS X 10.4.7 > Database server: Windows XP SP2, Oracle XE > Reporter: Matt Solnit > > I have a table mapping that looks similar to the following: > <class name="User" table="`User`"> >  > Notice the back-ticks around the table name. > When I use Hibernate to create the schema for me, it correctly generates a table name called "User" (including the quote marks). But when I validate the schema, it cannot find the table and so validation fails. > I am thinking the problem is somewhere in org/hibernate/tool/hbm2ddl/DatabaseMetadata.getTableMetadata(). It tries to look for "USER", because OracleDatabaseMetaData.storesUpperCaseIdentifiers() returns true. But the code doesn't realize that quoted tables are a special case and it has to look for "User" instead. > Another symptom of the same problem is that if I generate a schema update script, it will attempt to re-create the existing table. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-122) Add natural-id annotation

by Nicolás Lichtmaier (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-122?page=co... ] Nicolás Lichtmaier commented on ANN-122: ---------------------------------------- So.... is the patch ready to be commited? Should I do something? Hellooo? =) > Add natural-id annotation > ------------------------- > > Key: ANN-122 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-122 > Project: Hibernate Annotations > Issue Type: New Feature > Components: binder > Affects Versions: 3.1beta6 > Reporter: Mathias Bogaert > Priority: Minor > Fix For: 3.3.1 > > Attachments: natural-id-v2.patch, natural-id-v3.patch, natural-id.patch > > > HIbernate 3.0.5 introduced natural-id. Add this to Annotations, as a @NaturalId annotation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2235) Support for null map-keys in <map> mappings

by Igor Lobanov (JIRA)

Support for null map-keys in <map> mappings ------------------------------------------- Key: HHH-2235 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2235 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Reporter: Igor Lobanov Priority: Minor I'm not sure if I should file it as a bug. Hibernate requires index column for <map> mappings to be not null. This is required by the code in AbstractCollectionPersister#readIndex(...), which raises exception if index column is null. However, when I override collection persister and force readIndex method to return null, everything seems to work fine. Hibernate allows me to work with maps using null value as a key. Though I havn't tested it extensivly yet. What is the reason for disallowing null values as a keys? If there are possible complicated error conditions, then this issue is a feature request for null-values support for <map> mappings. If there are no errors possible, then constraining such behavior is probably wrong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

4
21
0 / 0

[Hibernate-JIRA] Created: (HHH-2672) Need Support Readonly Session

by kindy wu (JIRA)

Need Support Readonly Session ----------------------------- Key: HHH-2672 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2672 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.4.sp1 Reporter: kindy wu I think we need a readonly session to impove the Select performance! code is like this: session.SetReadonly(true);//or ReadonlySession rSession = new ReadonlySession(session); Code cs = session.CreateQuery("From Code c");//table codes is very huge if we set the session to Readonly then the Save,Update,Delete,SaveOrUpdate method is disable. and the entities that select from session is not need to write into session cache and don't need to generate proxy for lazy fetch. In a Word Readonly Session work like ibatis and Support good Performance for huge Data Collection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2007