August 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Updated: (ANN-261) Allow specifying foreign key constraint name using annotations (inspired by David Hay)

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-261?page=all ] Emmanuel Bernard updated ANN-261: --------------------------------- Summary: Allow specifying foreign key constraint name using annotations (inspired by David Hay) (was: Allow specifying foreign key constraint name using annotations) > Allow specifying foreign key constraint name using annotations (inspired by David Hay) > -------------------------------------------------------------------------------------- > > Key: ANN-261 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-261 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.1beta8 > Reporter: Paul Barry > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.0 > Attachments: hibernate-annotation-3.2.0.CR2-fk2.patch, hibernate-annotations-3.2.0.CR1-fk.patch, hibernate-annotations-fk.patch > > > Using hbm.xml configuration for many-to-one, there is a foreign-key property that allows you to specify the name of the FK constraint. It would be nice if there was something similar for annotations, such as @ManyToOne ( constraintName = "FK_WHATEVER"). Also, a sensible default would be nice to, for example FK_TABLE_NAME_COLUMN_NAME, rather than FK20708CF6792111. I know Oracle has a 30 char limit for constraint names, so there would have to me some logic to find a way to abbreviate it. -- 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

18 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-417) @ForeignKey(inverseName) ignored for @ManyToOne @JoinTable or @OneToOne @JoinTable

by Emmanuel Bernard (JIRA)

@ForeignKey(inverseName) ignored for @ManyToOne @JoinTable or @OneToOne @JoinTable ----------------------------------------------------------------------------------- Key: ANN-417 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-417 Project: Hibernate Annotations Type: Improvement Components: binder Reporter: Emmanuel Bernard -- 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

18 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Resolved: (ANN-261) Allow specifying foreign key constraint name using annotations

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-261?page=all ] Emmanuel Bernard resolved ANN-261: ---------------------------------- Resolution: Fixed Assign To: Emmanuel Bernard I've used the ideas of David's patch. The patch does not work on @ManyToOne @JoinTable or @OneToOne @JoinTable because I map that using a <join> If someone can provide a patch for that, that'd be great. > Allow specifying foreign key constraint name using annotations > -------------------------------------------------------------- > > Key: ANN-261 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-261 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.1beta8 > Reporter: Paul Barry > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.0 > Attachments: hibernate-annotation-3.2.0.CR2-fk2.patch, hibernate-annotations-3.2.0.CR1-fk.patch, hibernate-annotations-fk.patch > > > Using hbm.xml configuration for many-to-one, there is a foreign-key property that allows you to specify the name of the FK constraint. It would be nice if there was something similar for annotations, such as @ManyToOne ( constraintName = "FK_WHATEVER"). Also, a sensible default would be nice to, for example FK_TABLE_NAME_COLUMN_NAME, rather than FK20708CF6792111. I know Oracle has a 30 char limit for constraint names, so there would have to me some logic to find a way to abbreviate it. -- 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

18 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1944) generated subqueries and jpaql compliance (derived select clause) check

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1944?page=all ] Steve Ebersole updated HHH-1944: -------------------------------- Summary: generated subqueries and jpaql compliance (derived select clause) check (was: JPA compliance complains when IS EMPTY is used) > generated subqueries and jpaql compliance (derived select clause) check > ----------------------------------------------------------------------- > > Key: HHH-1944 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1944 > Project: Hibernate3 > Type: Bug > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > is empty is actually translated by the AST into a subtree having an implicit select clause > On my version I've check that we're at level 1 before raising the exception. This might not be the perfect fix > if ( getSessionFactoryHelper().isStrictJPAQLComplianceEnabled() && fromClause.getLevel() == 1 ) { > throw new QuerySyntaxException( "JPA-QL compliance requires select clause" ); > } -- 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

18 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1944) generated subqueries and jpaql compliance (derived select clause) check

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1944?page=all ] Steve Ebersole closed HHH-1944: ------------------------------- Resolution: Fixed trunk and 3.2 > generated subqueries and jpaql compliance (derived select clause) check > ----------------------------------------------------------------------- > > Key: HHH-1944 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1944 > Project: Hibernate3 > Type: Bug > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > is empty is actually translated by the AST into a subtree having an implicit select clause > On my version I've check that we're at level 1 before raising the exception. This might not be the perfect fix > if ( getSessionFactoryHelper().isStrictJPAQLComplianceEnabled() && fromClause.getLevel() == 1 ) { > throw new QuerySyntaxException( "JPA-QL compliance requires select clause" ); > } -- 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

18 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2015) where= does not set parenthesis leading to unexpected query when multiclause are used

by Emmanuel Bernard (JIRA)

where= does not set parenthesis leading to unexpected query when multiclause are used ------------------------------------------------------------------------------------- Key: HHH-2015 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2015 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr3 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor where="1=1 or 1 != 0" leads to select ... from ... where ... and 1=1 or 1 != 0 should really be select ... from ... where ... and (1=1 or 1 != 0) -- 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

18 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (ANN-261) Allow specifying foreign key constraint name using annotations

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-261?page=co... ] Emmanuel Bernard commented on ANN-261: -------------------------------------- arrrg no unit test! > Allow specifying foreign key constraint name using annotations > -------------------------------------------------------------- > > Key: ANN-261 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-261 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.1beta8 > Reporter: Paul Barry > Priority: Minor > Fix For: 3.2.0 > Attachments: hibernate-annotation-3.2.0.CR2-fk2.patch, hibernate-annotations-3.2.0.CR1-fk.patch, hibernate-annotations-fk.patch > > > Using hbm.xml configuration for many-to-one, there is a foreign-key property that allows you to specify the name of the FK constraint. It would be nice if there was something similar for annotations, such as @ManyToOne ( constraintName = "FK_WHATEVER"). Also, a sensible default would be nice to, for example FK_TABLE_NAME_COLUMN_NAME, rather than FK20708CF6792111. I know Oracle has a 30 char limit for constraint names, so there would have to me some logic to find a way to abbreviate it. -- 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

18 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Resolved: (ANN-382) Exception raising : Strange behaviour depending on package names

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-382?page=all ] Emmanuel Bernard resolved ANN-382: ---------------------------------- Resolution: Fixed This should be fixed in SVN, I'd apreciate a test in your environment. > Exception raising : Strange behaviour depending on package names > ---------------------------------------------------------------- > > Key: ANN-382 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-382 > Project: Hibernate Annotations > Type: Bug > Environment: Hibernate's annotations packaged in JBoss EJB 3.0 RC8- FD > Microsoft SQL Server 2000 > Reporter: Pierre Fourès > Assignee: Emmanuel Bernard > Fix For: 3.2.0 > Attachments: BugEJB3.zip > > > As described in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=960763) and discussed with Emmanuel, I encounter a strange behaviour with annotations depending of my package's names. > Supposing hibernate load classes by package alphabetical order; if it get the "parent" class first all works fine, if it get the "child" class first, it raise an exception ! > Here is a subset of my classes, cleaned of getters, setters and all unrelated things, then followed by the exception stack : > /////////////////////////////////////////////// > package fr.ifis.entity.field.card; > import java.io.Serializable; > import javax.persistence.Embeddable; > import javax.persistence.Entity; > import javax.persistence.Id; > import javax.persistence.ManyToOne; > import fr.ifis.entity.project.Card; > @Entity > public class CardField { > @Id > private PrimaryKey primaryKey = new PrimaryKey(); > > // cardtmp is a trick used in order to wait for http://opensource.atlassian.com/projects/hibernate/browse/ANN-381 resolution > @ManyToOne > private Card cardtmp; > @Embeddable > private class PrimaryKey implements Serializable { > > @ManyToOne(optional = false) > private Card card; > > @ManyToOne(optional = false) > private CardKey key; > } > } > /////////////////////////////////////////////// > package fr.ifis.entity.field.card; > import javax.persistence.Entity; > import javax.persistence.GeneratedValue; > import javax.persistence.Id; > @Entity > public class CardKey { > @Id > @GeneratedValue > private int id; > } > /////////////////////////////////////////////// > package fr.ifis.entity.project; > import java.io.Serializable; > import java.util.Set; > import javax.persistence.CascadeType; > import javax.persistence.Embeddable; > import javax.persistence.Entity; > import javax.persistence.FetchType; > import javax.persistence.Id; > import javax.persistence.ManyToOne; > import javax.persistence.OneToMany; > import fr.ifis.entity.field.card.CardField; > @Entity > public class Card { > @Id > private CardPrimaryKey primaryKey = new CardPrimaryKey(); > > @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER, mappedBy="cardtmp") // > private Set<CardField> fields; > > @Embeddable > private class CardPrimaryKey implements Serializable { > > @ManyToOne(optional = false) > private Project project; > > //An other @ManyToOne is also present in the real model > //The problem still occurs even when i remove this relation, it was no use to kept it for describe the problem > } > } > /////////////////////////////////////////////// > package fr.ifis.entity.project; > import javax.persistence.Entity; > import javax.persistence.GeneratedValue; > import javax.persistence.Id; > @Entity > public class Project { > @Id > @GeneratedValue > private int id; > } > /////////////////////////////////////////////// > [java] ERROR 29-06 19:42:18,272 (AbstractController.java:incrementState:350) -Error installing to Start: name=persistence.units:unitName=Refonte state=Create > [java] org.hibernate.MappingException: Foreign key (FK6771BFAA1845E8B:CardField [])) must have same number of columns as the referenced primary key (Card [project_id]) > [java] at org.hibernate.mapping.ForeignKey.alignColumns(ForeignKey.java:90) > [java] at org.hibernate.mapping.ForeignKey.alignColumns(ForeignKey.java:73) > [java] at org.hibernate.cfg.Configuration.secondPassCompileForeignKeys(Configuration.java:1182) > [java] at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1089) > [java] at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:302) > [java] at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1034) > [java] at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1015) > [java] at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:154) > [java] at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:751) > [java] at org.hibernate.ejb.Ejb3Configuration.createContainerEntityManagerFactory(Ejb3Configuration.java:350) > [java] at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:119) > [java] at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:585) > [java] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55) > [java] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:107) > [java] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) > [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:100) > [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.installAction(KernelControllerContextActions.java:582) > [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextActions.java:175) > [java] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) > [java] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226) > [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593) > [java] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346) > [java] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438) > [java] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379) > [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225) > [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151) > [java] at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:79) > [java] at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:73) > [java] at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:91) > [java] at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:626) > [java] at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:475) > [java] at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.start(EJB3StandaloneDeployer.java:460) > [java] at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:291) > [java] at fr.ifis.Main.main(Unknown Source) > /////////////////////////////////////////////// > Indeed, depending on the package names I get or not an excpetion ! > It doesn't work with the package fr.ifis.entity.project but if I rename the package in fr.ifis.entity.aproject and then move it "before" the field.card package, all works fine. > In order to facilitate the identification of the problem, I also include as attachement the eclipse project of this problem repport. > In order to keep reasonable the size of the attachement, I did not included the libraries nor the configuration files for launch ejb3-embedded. Thoses files are issued from the project simple-deployment included in JBoss EJB 3.0 RC8-FD. The only change i've done was to specify in embedded-jboss-beans.xml the properties of my database. > Regards, > Pierre. -- 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

18 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1685) DetachedCriteria doesn't create alias on subcriteria

by sharad (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1685?page=c... ] sharad commented on HHH-1685: ----------------------------- same problem with 3.1.3. For now, the workaround is to use createAlias(assoPath, aliasName) > DetachedCriteria doesn't create alias on subcriteria > ---------------------------------------------------- > > Key: HHH-1685 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1685 > Project: Hibernate3 > Type: Bug > Components: query-criteria > Versions: 3.1.3 > Reporter: John > Attachments: hhh1685-example.txt > > > DetachedCriteria has two createCriteria methods: > public DetachedCriteria createCriteria(String associationPath) throws HibernateException > public DetachedCriteria createCriteria(String associationPath, String alias) throws HibernateException > However, the code for both was identical - they called the inner criteria's createCriteria(String) method. The version with the alias did not call the inner's version with the alias. The following patch snipped shows the change: > public DetachedCriteria createCriteria(String associationPath, String alias) > throws HibernateException { > - return new DetachedCriteria( impl, criteria.createCriteria(associationPath) ); > + return new DetachedCriteria( impl, criteria.createCriteria(associationPath, alias) ); > } > This bug was discovered while trying to link a 2-deep subquery to its parent via aliases. (Surfacing this issue might only be possible with the patch HHH-952 in place - I'm not sure. Seems like a bug regardless, as it definitely fixed my alias reference issue.) I'll get an example posted shortly. -- 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

18 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Sergey (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123?page=c... ] Sergey commented on HHH-1123: ----------------------------- This appears to be related to an old HB-655 bug (incorrectly labeled as an enhancement). Are there plans to fix this bug? The attached patch takes the hardcoding approach for the number of items. This goes against the tendency of Hibernate to make things as configurable as possible while providing reasonable defaults. I think that this parameter needs to be configurable as well. I think the estimate of 1 hour is too optimistic though, because one needs to factor in the updates to the documentation etc. > Cannot put more than 1000 elements in a InExpression > ---------------------------------------------------- > > Key: HHH-1123 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 rc2, 3.2.0.alpha1 > Environment: Oracle 9i > Reporter: Alexis Seigneurin > Attachments: patch.txt > > Original Estimate: 1 hour > Remaining: 1 hour > > The number of elements that we can put in a "in" expression is limited to a certain amount (1000 for Oracle, for instance). When creating a criteria query, the org.hibernate.criterion.InExpression class should split the expression into several smaller ones. > Attached is a patch which splits the expression by slices of 500 elements. For example, if we have 1001 elements to put in the "in" expression, the result would be : > (entity.field in (?, ?, ?...) or entity.field in (?, ?, ?...) or entity.field in (?)) > The surrounding parantheses are useful to avoid problems with other conditions (a "and" condition taking over the one of the "or" conditions). -- 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

18 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2006