February 2007 - hibernate-issues - Jboss List Archives

[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, 12 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

16 years

6
16
0 / 0

[Hibernate-JIRA] Created: (HHH-2407) rework HQL translator

by Steve Ebersole (JIRA)

rework HQL translator --------------------- Key: HHH-2407 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2407 Project: Hibernate3 Type: Improvement Components: query-hql, query-criteria Reporter: Steve Ebersole Assigned to: Steve Ebersole Priority: Blocker Fix For: 3.3 Formalization of the work already started on the HQL_ANTLR_2 branch in SVN. Specifically, split the translation into 4 phases instead of 3 phases (we really sorta, kinda have 4 phases already with the join-post-processor). This is pre-requisite for many requested enhancements to HQL. Also the idea is to consolidate code between HQL and Criteria translation, thus giving Criteria queries all the capabilities available in HQL. -- 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

1
3
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: (ANN-558) @OneToMany(mappedBy="") can not recognize properties in parent classes

by Amir Pashazadeh (JIRA)

@OneToMany(mappedBy="") can not recognize properties in parent classes ---------------------------------------------------------------------- Key: ANN-558 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-558 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.1 Reporter: Amir Pashazadeh @Entity @Inheritance(strategy=InheritanceType.SINGLE_TABLE) public class A { @ManyToOne private B b; } @Entity @DiscriminatorValue("c") public class C extends A { } @Entity public class B { @OneToMany(mappedBy="b") private List<C> cs; } there would be an exception in this mapping, and it says that there is no such property found in C class (which is mapped by "b") ------ by the way I'm not sure whether this is a Hibernate Annotations bug, or a Hibernate Core bug (I've not tested it without annotations). -- 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, 1 month

7
10
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, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-900) Support ctrl+shift+t in the Hibernate Console perspective

by Joseph Marques (JIRA)

Support ctrl+shift+t in the Hibernate Console perspective --------------------------------------------------------- Key: HBX-900 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-900 Project: Hibernate Tools Type: Bug Versions: 3.2beta8 Reporter: Joseph Marques In other perspectives, ctrl+shift+t will pop open a dialog that allows me to select some type (some class on the source path). I find myself wanting to work in the Hibernate perspective more often, but I'm hindered by the fact that I can't easily open new types with this shortcut. I took a look at "preferences > general > keys" but I didn't see anything that should prevent the shortcut from working in the Hibernate perspective. Oddly, ctrl+shift+r works in the perspective, and it seems to be set up nearly identically in the keyboard shortcuts. Is there something that I'm missing? -- 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, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (ANN-527) reference a target entity (in a collection) by entity name

by Armin Haaf (JIRA)

reference a target entity (in a collection) by entity name ---------------------------------------------------------- Key: ANN-527 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-527 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Armin Haaf It is only possible to reference a targetEntity by class. @ManyToMany(targetEntity = TestImpl.class) List<Test> myList; This makes it impossible to exchange TestImpl.class implemention by another implemention by the mappings definition. It would be helpful to reference a targetEntity by name. @ManyToMany(targetEntityName = "Test") This would help a lot to implement moduls and frameworks. Another way to support this would be to search for a implementation of the collection elements (which are typically Interfaces) in the mapped entities -- 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, 2 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HBX-860) cfg.xml generation should have option if it should generate <mappings>

by Max Rydahl Andersen (JIRA)

cfg.xml generation should have option if it should generate <mappings> ---------------------------------------------------------------------- Key: HBX-860 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-860 Project: Hibernate Tools Type: Improvement Reporter: Max Rydahl Andersen Fix For: 3.2beta10 adding <mapping> for class when JPA does not make sense. -- 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, 2 months

2
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2007