[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Diego Pires Plentz commented on HHH-2952: ----------------------------------------- http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#querycrite... List cats = sess.createCriteria(Cat.class) .createAlias("kittens", "kt") .createAlias("mate", "mt") .add( Restrictions.eqProperty("kt.name", "mt.name") ) .list(); This? :-) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Julian Wood commented on HHH-2952: ---------------------------------- Would love to see this. Here's my use case: Criteria criteria = session.createCriteria(Message.class); criteria.createAlias("folder", "f"); criteria.createAlias("f.owner", "owner"); criteria.add(Restrictions.eq("owner.username", recipient.getUsername())); criteria.add(Restrictions.sqlRestriction("f1_.FolderType = 'Inbox'")); I'm looking for messages whose folder has a discriminator (FolderType) of 'Inbox'. Can I rely on the fact that hibernate called my folder alias f1_ in my sql restriction? This would be more reassuring, as described above: criteria.add(Restrictions.sqlRestriction("{f}.FolderType = 'Inbox'")); (Or how can I make a discriminator into an accessible property?) J -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Sergey Pulyaev updated HHH-2952: -------------------------------- Attachment: SQLAliasedProjection.java Aliased Projection -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Sergey Pulyaev updated HHH-2952: -------------------------------- Attachment: RestrictionsExt.java Improoved version of Restrictions -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Günter Graf commented on HHH-2952: ---------------------------------- @ Sergey Pulyaev: I tried to add your files to my project, but there are two issues in the SQLAliasedCriterion and SQLAliasedProjection classes: 1st: The method getAliasedCriteria(String) from the type CriteriaQueryTranslator is not visible 2nd: The method getOuterQueryTranslator() is undefined for the type CriteriaQueryTranslator Do I have to do anything else to get your classes working? note: i am using Hibernate 3.2.5, so there may have been changes in Hibernate that cause your files not being usable anymore. If there's allready another approacht for using aliases in the sqlRestriction method, I would appreciate to hear of 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Günter Graf commented on HHH-2952: ---------------------------------- Thanks, I'll give it a try. I was wondering if we could avoid changing the visibility of the getAliasedCriteria(String) method and adding the getter. your code to get the aliased criteria is: cri = ((org.hibernate.loader.criteria.CriteriaQueryTranslator) criteriaQuery).getAliasedCriteria(alias); Due to lack of time, I haven't tried it out yet, but my idea is to use cri = (Criteria) ((org.hibernate.loader.criteria.CriteriaQueryTranslator) criteriaQuery).getRootCriteria().iterateSubcriteria().next(); to recursively iterate over all criterias and then use the cri.getAlias() or criteriaQuery.getSQLAlias(criteria) method to get the alias property. Do you think, that could be possible? Maybe you have allready made experiences with the iterateSubcriteria() method. To get the outerQueryTranslator we could use reflection (if it is allowed in the java security manager (ReflectPermission)). -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Sergey Pulyaev commented on HHH-2952: ------------------------------------- This is possible, but : if i already made some changes in several classes - why to implement slower logic if i can just can patch just one additional file instead? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Sergey Pulyaev commented on HHH-2952: ------------------------------------- I'm sorry again :-) i make a wrong link - i mean ticket HHH-2308 -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Kai Prünte updated HHH-2952: ---------------------------- Attachment: SQLAliasedCriterion.java I also run into this problem and try your classes. As mentioned before sometimes it is not easy to patch Hibernate or other third party libs. I will get into trouble with my deployment. Because of that reason I changed SQLAliasedCriterion in that way, that no modifications of existing Hibernate code is necessary. If you want to use it, please have a look into the exception handling. This is only quick and dirty. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952?page=c... ] Ondrej Medek commented on HHH-2952: ----------------------------------- Hi guys, thanks very much for your SQLAliasedCriterion. I think I have simplified it - it is no necessary to change the core Hibernate files, no "Reflection magic". -- 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