July 2007 - hibernate-issues - Jboss List Archives

[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

15 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2629) Enable ordering by association paths

by Jörg Heinicke (JIRA)

Enable ordering by association paths ------------------------------------ Key: HHH-2629 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2629 Project: Hibernate3 Issue Type: Patch Components: query-criteria Affects Versions: 3.2.4.sp1 Reporter: Jörg Heinicke In Hibernate's criteria API ordering is not possible on association properties without explicitly creating aliases. This also only works on one level, not recursively as it would be needed in the following example. Criteria criteria = session.createCriteria(Account.class); Criteria pCriteria = criteria.createCriteria("person"); pCriteria.add(Example.create(person)); pCriteria.createCriteria("company"); criteria.addOrder(Order.asc("person.company.name")); return criteria.list(); I have changed CriteriaQueryTranslator in a way that it first searches the aliasCriteriaMap, second the associationPathCriteriaMap. And the key used for the search is no longer StringHelper.root( propertyName ); but StringHelper.qualifier( propertyName ); >From what I understand this can't break anything since it has always only worked with one '.' in the path. For those cases the key stays the same. This implementation is still not perfect since 1. you need to create criteria in advance 2. you can't switch between alias and actual association path. The best would probably be to walk the path recursively. -- 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, 6 months

3
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

15 years, 6 months

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

15 years, 6 months

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

15 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-636) Add the annotations to map the User Collection Type

by jason (JIRA)

Add the annotations to map the User Collection Type --------------------------------------------------- Key: ANN-636 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-636 Project: Hibernate Annotations Issue Type: New Feature Components: binder Environment: n/a Reporter: jason I am searching a way from the Hibernate Annotation to map the user defined collection, and find out the following : Can anybody let me know what the status for this? or how i can map the user collection type by hibernate annotation, thanks Add an annotation to specify the UserCollectionType for a OneToMany or ManyToMany. The annotation is named CollectionTypeInfo, perhaps better named UserCollectionType, but I didn't know the standards for naming classes. The change to AnnotationBinder is minor and is delineated by '//dwsjoquist//' comment lines. Usage: @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL) @JoinColumn(name = "id") @CollectionTypeInfo(name = "examples.MyUserCollectionType") public List<ExampleAttribute> getExampleAttributes() { -- 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, 7 months

3
2
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

15 years, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-104) Make @DocumentId optional and rely on @Id

by Emmanuel Bernard (JIRA)

Make @DocumentId optional and rely on @Id ----------------------------------------- Key: HSEARCH-104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-104 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Priority: Minor -- 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, 8 months

2
6
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

15 years, 8 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2546) fetch="select" doesn't work when there are no mapped columns in joined except <key

by Derar Bakr (JIRA)

fetch="select" doesn't work when there are no mapped columns in joined except <key ---------------------------------------------------------------------------------- Key: HHH-2546 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2546 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: Windows XP Pro Reporter: Derar Bakr java.lang.StringIndexOutOfBoundsException: String index out of range: -2 at java.lang.String.substring(String.java:1768) at java.lang.String.substring(String.java:1735) at org.hibernate.persister.entity.AbstractEntityPersister.renderSelect(AbstractEntityPersister.java:2899) at org.hibernate.persister.entity.SingleTableEntityPersister.generateSequentialSelect(SingleTableEntityPersister.java:647) at org.hibernate.persister.entity.SingleTableEntityPersister.postInstantiate(SingleTableEntityPersister.java:696) .... Everything is very simple. There is stupid code in SelectFragment class, method toFragmentString, line 94. String that is being created there, contains list of fields, like a "f1, f2, f3, ..., fn". ", " is being added in every iteration, without check for it is first iteration. And in class AbstractEntityPersister., method renderSelect, line 2899, where that method is called, this first ", " is deleted using substring(2). So no check for empty string. I suggest to add check :))) I just create dynamic mappings programmatically, so create empty join subclass mappings - and in created table there are no fields by default except foreing key. -- 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, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007