January 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Créée: (HHH-2060) To be able to use <generator> with <composite-id>

by Xavier Brénuchon (JIRA)

To be able to use <generator> with <composite-id> ------------------------------------------------- Key: HHH-2060 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr4 Environment: Hibernate 3.x Reporter: Xavier Brénuchon Hello, This is the continuation of HB-389 We develop an application which has very strong need for performance with several tens of million recordings. Partitioning is a need. So for that, I use <composite-id>. But my primary key is not a natural key, but a real technical key : - column of partitioning for optimization of the data base - column of technical id So I need to have a generator, for exemple : <composite-id name="id" class="IdPartition"> <key-property name="org" type="string" column="ORG"/> <key-property name="id" type="long" column="ID"/> <generator class="fr.test.xavier.IdPartitionGenerator"> <param name="table">TAB_SEQ</param> <param name="column">LAST</param> </generator> </composite-id> The good news is that Hibernate can use that (HB-389). In fact, it is enough to modify the DTD to authorize <generator> in <composite-id> and it is all. The current code of Hibernate manages it very well. Is it possible that Hibernate is enriched by this functionality? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

7
17
0 / 0

[Hibernate-JIRA] Created: (EJB-254) Allow DataSource overriding through createEntityManager(String, Map override)

by Emmanuel Bernard (JIRA)

Allow DataSource overriding through createEntityManager(String, Map override) ----------------------------------------------------------------------------- Key: EJB-254 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-254 Project: Hibernate Entity Manager Type: Improvement Components: EntityManager Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
7
0 / 0

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

by Dan Ports (JIRA)

Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl> -------------------------------------------------------------------------------------------- Key: HBX-757 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-757 Project: Hibernate Tools Type: Improvement Components: ant Versions: 3.2beta7 Reporter: Dan Ports Priority: Minor The file name, delimiter, halt on error, and format options are provided by SchemaExport/<hbm2ddl> already, so it makes sense to add their functionality to SchemaUpdate as well. I'll submit a patch shortly. (Is this the right place to post this, since SchemaUpdate is in the Hibernate core SVN?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
17
0 / 0

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

by Nico De Groote (JIRA)

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

15 years, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-770) Consider integration/union between Eclipse Dali and Hibernate Tools

by Diego Pires Plentz (JIRA)

Consider integration/union between Eclipse Dali and Hibernate Tools ------------------------------------------------------------------- Key: HBX-770 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-770 Project: Hibernate Tools Type: Improvement Reporter: Diego Pires Plentz What about? Consider integration/union between Eclipse Dali and Hibernate Tools. An official Hibernate project, fully integrated with an oficial Eclipse project. http://www.eclipse.org/dali/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2354) Schema validation too rigid for MySql enums

by Zeljko Trogrlic (JIRA)

Schema validation too rigid for MySql enums ------------------------------------------- Key: HHH-2354 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2354 Project: Hibernate3 Type: Bug Components: metamodel Environment: jboss-seam-1.1.0.GA, MySQL 5 Reporter: Zeljko Trogrlic Enum column type in MySQL is handled as CHAR in their JDBC driver and should be mapped to String Java type. However, Hibernate expects varchar(n) and fails to do the validation. This is how DatabaseMetaData.getColumns describes it: DATA_TYPE=1 TYPE_NAME=enum Note that although TYPE_NAME is enum, DATA_TYPE represents CHAR. Hibernate reports following exception: 13:49:31,397 INFO [TableMetadata] table found: configuration.userdb_domain_acl 13:49:31,397 INFO [TableMetadata] columns: [id, enabled, tablename, domain] 13:49:31,397 WARN [ServiceController] Problem starting service persistence.units:ear=msmgui.ear,unitName=msmgui javax.persistence.PersistenceException: org.hibernate.HibernateException: Wrong column type: enabled, expected: varchar( 2) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:698) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Validation should be fixed/relaxed to avoid this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2193) Introduce a flag to avoid checking NamedQuery at startup

by Emmanuel Bernard (JIRA)

Introduce a flag to avoid checking NamedQuery at startup -------------------------------------------------------- Key: HHH-2193 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2193 Project: Hibernate3 Type: Improvement Components: core Reporter: Emmanuel Bernard Fix For: 3.2.2 With the ratio of 1 query out of 60 entities (60 entities and 10 named queries), checking the named queries at startup takes 7% (specifically the HQLQueryPlan creation). I imagine that one want to avoid the overhead while doing unit 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

15 years, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2077) Providing an escape sequence for Criteria queries

by Tobias Dietl (JIRA)

Providing an escape sequence for Criteria queries ------------------------------------------------- Key: HHH-2077 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2077 Project: Hibernate3 Type: Improvement Components: query-criteria Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3, 3.2.0.cr4 Environment: Hibernate 3.1.3, MySQL, HSQLDB, Oracle Reporter: Tobias Dietl Up to now, there is no way of setting the escape sequence to use for string comparisions with like for Criteria queries. This is necessary as MySQL on the one hand and HSQLDB / Oracle on the other behave differently... If you want to search for '_abc' in MySQL, you have to use: value like '\\_abc' In Oracle or HsqlDB, you have to use: value like '\_abc' If you want to switch to another escape sequence like '|' , you can set it in HQL with value like '|_abc' escape '|'. Unfortunately, there is no way of setting it for Criteria queries, which would force me to rewrite all my Criteria queries in HQL. It would really be nice if the feature/improvement would be added... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 12 months

6
16
0 / 0

[Hibernate-JIRA] Created: (ANN-509) referencedColumnName of fk column causes MappingException

by Matthew D. Frederes (JIRA)

referencedColumnName of fk column causes MappingException --------------------------------------------------------- Key: ANN-509 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-509 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.0.ga Environment: Hibernate 3.2.0.GA inside JBoss EJB install Reporter: Matthew D. Frederes Attachments: jiratest.ejb3 See attached test ejb3 file. Using a referencedColumnName of fk column causes MappingException: org.hibernate.MappingException: Unable to find column with logical name: vendor_id in org.hibernate.mapping.Table(ItemCost) and its related supertables and secondary tables @ManyToOne @JoinColumns({ @JoinColumn(name="vendor", referencedColumnName="vendor_id", insertable=false, updatable=false), @JoinColumn(name="item", referencedColumnName="item_id", insertable=false, updatable=false) }) public ItemCost getDefaultCost() { return defaultCost; } -- 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

4
15
0 / 0

[Hibernate-JIRA] Created: (HHH-2383) Generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages in Oracle.

by Carlos Eugênio P. da Purificação (JIRA)

Generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages in Oracle. --------------------------------------------------------------------------------------------------------------------- Key: HHH-2383 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2383 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.2 Environment: Hibernate 3.2.2 GA, Oracle 10 Reporter: Carlos Eugênio P. da Purificação Attachments: test.zip The generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages. -- 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

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2007