October 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-530) Allow application of filters on subqueries

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Steve Ebersole commented on HHH-530: ------------------------------------ Shawn, not strictly relevant to this issue, but I wanted to answer your question. Currently users can mix positional and named parameters (in theory) *as long as* all positional parameters are encountered first during parsing. I have never liked that and especially considering the code to handle it is extremely optimistic and fails in various cases. So it either needs to be restricted moving forward or the handling improved (which I have an idea for). > Allow application of filters on subqueries > ------------------------------------------ > > Key: HHH-530 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-530 > Project: Hibernate3 > Issue Type: Patch > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Fix For: 3.3 > > Attachments: HHH-530.patch, hibernate_filter_fix-3.0.5.patch, hibernate_filter_fix-3.0.5_14.patch > > > Currently filter conditions are applied in subselects, they should not be. -- 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

17 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-530) Allow application of filters on subqueries

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Steve Ebersole updated HHH-530: ------------------------------- Fix Version/s: 3.3 Issue Type: Patch (was: Bug) Summary: Allow application of filters on subqueries (was: Better handling of filter params in HQL to allow filter use on subqueries) Taking a look for 3.3 > Allow application of filters on subqueries > ------------------------------------------ > > Key: HHH-530 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-530 > Project: Hibernate3 > Issue Type: Patch > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Fix For: 3.3 > > Attachments: HHH-530.patch, hibernate_filter_fix-3.0.5.patch, hibernate_filter_fix-3.0.5_14.patch > > > Currently filter conditions are applied in subselects, they should not be. -- 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

17 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-822) <key-property> will actually pick up <type> tags if it were allowed by the DTD

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-822?page=co... ] Gail Badner commented on HHH-822: --------------------------------- Please open a new ticket for this issue. > <key-property> will actually pick up <type> tags if it were allowed by the DTD > ------------------------------------------------------------------------------ > > Key: HHH-822 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-822 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0 final, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5 > Reporter: amit bhayani > Fix For: 3.1 beta 2 > > > The DTD does not allow map to have a composite-map-key where one of it's property is a usertype that implements ParameterizedType. > for example: > <map name="pgtaPermission" table="USERDESKPERMISSIONS_TABLE" lazy="false" fetch="select"> > <key column="USERDBID"/> > <composite-map-key class="UserPermDBImpl$UserPermissionData$PitGroupTAPermissionKey"> > <key-property name="pitGroup" column="PITGROUPDBID"> > <type name="com.tullib.core.hibernate.usertype.BasicEnumUserType"> > <param name="CLASS"> com.tullib.sds.party.User$UserType</param> > </type> > </key-property> > ............... > </composite-map-key> > </map> > If hibernate-mapping-3.0.dtd is modified to have <type> in <key-property> tag it should work -- 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

17 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-991) HIbernateConsoleRuntimeException: Problems while loading database driver class(com.microsoft.jdbc.sqlserver.SQLServerDriver

by Sriram Srinivasan (JIRA)

HIbernateConsoleRuntimeException: Problems while loading database driver class(com.microsoft.jdbc.sqlserver.SQLServerDriver --------------------------------------------------------------------------------------------------------------------------- Key: HBX-991 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-991 Project: Hibernate Tools Issue Type: Bug Components: eclipse Affects Versions: 3.2beta10 Environment: Eclipse Europa IDE with WST and Hibernate 3.2 beta 10 plugin for eclipse using JBoss 4.2 server and SQL Server Driver. Reporter: Sriram Srinivasan Attachments: EclipseHibernateError.JPG I created a EJB project in eclipse. And then i tried to create a hibernate configuration file within the project. Then i tried to create a Hibernate Console Configuration using that configuration file. When i do that, i get the following exception. -- 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

17 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2872) MappingException thrown for @ManyToOne join if table on the left of the association is alphabetically lower than table on the right

by Mukesh (JIRA)

MappingException thrown for @ManyToOne join if table on the left of the association is alphabetically lower than table on the right ------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2872 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2872 Project: Hibernate3 Issue Type: Bug Components: core, query-hql Affects Versions: 3.2.5 Reporter: Mukesh I get a MappingException for @ManyToOne join if table on the left of the association is alphabetically lower than table on the right I have tables VO_USER, V_ORGANIZATIONAL and VO_AREA VO_USER has USR_IDR as primary key. V_ORGANIZATIONAL has a composite primary key of BUSINESS_AREA_CODE and CODE VO_AREA has BUS_ARA_IDR as the primary key I get the following exception when I join the VO_USER table with the V_ORGANIZATIONAL table "org.hibernate.MappingException: Unable to find column with logical name: BUSINESS_AREA_CODE in org.hibernate.mapping.Table(V_ORGANIZATIONAL_GRADE) and its related supertables and secondary tables" Howerver, if I rename the table V_ORGANIZATIONAL to VO_ORGANIZATIONAL, it works fine - which makes me conclude that it is an issue with the alphabetical ordering of the tables in the association. The table name on the left side of the @ManyToOne join must be alphabetically greater than the table on the right side - perhaps of the way hibernate loads the classes ?? Can someone confirm that is the issue, and what is the workaround/solution as I dont want to change the name of the table The simplified Code : @Entity @org.hibernate.annotations.Entity(mutable = true) @Table(name = "VO_USER") @Cache(usage = CacheConcurrencyStrategy.READ_WRITE, region = "user") public class User implements Serializable { private static final long serialVersionUID = -1894472442328538017L; @Id @Column(name = "USR_IDR") private String userId; @ManyToOne @JoinColumn(name = "BUS_ARA_IDR", insertable = false, updatable = false, unique = false, nullable = false) private BusinessArea businessArea; @ManyToOne(targetEntity = Organizational.class) @JoinColumns( { @JoinColumn(name = "BUS_ARA_IDR", referencedColumnName = "BUSINESS_AREA_CODE", unique = false, insertable = false, updatable = false, nullable=true), @JoinColumn(name = "USR_GRD", referencedColumnName = "CODE", unique = false, insertable = false, updatable = false, nullable=true) }) private Organizational organizational; .... } @Entity @Table(name = "V_ORGANIZATIONAL") @IdClass(OrganizationalKey.class) @Cache(usage = CacheConcurrencyStrategy.READ_ONLY, region = "organization") public class Organizational implements CodedValue, Comparable<Organizational>, Serializable { private static final long serialVersionUID = 7414956278287853961L; @Id private String code; @Id private BusinessArea businessArea; private Organizational() { } .... } public class OrganizationalKey implements Serializable { private static final long serialVersionUID = -8022957102173252455L; @ManyToOne(targetEntity = BusinessArea.class) @JoinColumn(name = "BUSINESS_AREA_CODE", insertable = false, updatable = false) private BusinessArea businessArea; @Column(name = "CODE", length = 5, insertable = false, updatable = false) private String code; OrganizationalKey() { } .... } @Entity @Table(name = "VO_AREA") @Cache(usage = CacheConcurrencyStrategy.READ_ONLY, region = "organization") public class BusinessArea implements CodedValue, Serializable { private static final long serialVersionUID = 6911068689852530787L; @Id @Column(name = "BUS_ARA_IDR", length = 3, updatable = false) private String code; private BusinessArea() { }; } -- 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

17 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Assigned: (HHH-1593) Infinite loop/StackOverflow when calling configuration.setListener(null)

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1593?page=c... ] Gail Badner reassigned HHH-1593: -------------------------------- Assignee: Gail Badner > Infinite loop/StackOverflow when calling configuration.setListener(null) > ------------------------------------------------------------------------ > > Key: HHH-1593 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1593 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1, 3.1.3 > Reporter: Shawn Kerstetter > Assignee: Gail Badner > Attachments: Configuration.patch > > > calling config.setListener(null) will result in an infinite loop. > It's a one character problem/fix: > public void setListener(String type, Object listener) { > if ( listener == null ) { > setListener( type, null ); //infinite recursion > } > should be: > public void setListener(String type, Object listener) { > if ( listener == null ) { > setListeners( type, null ); //need the plural > } -- 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

17 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-530) Better handling of filter params in HQL to allow filter use on subqueries

by Shawn Clowater (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Shawn Clowater updated HHH-530: ------------------------------- Attachment: HHH-530.patch Changes to enable working with filters for subqueries. > Better handling of filter params in HQL to allow filter use on subqueries > ------------------------------------------------------------------------- > > Key: HHH-530 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-530 > Project: Hibernate3 > Issue Type: Bug > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Attachments: HHH-530.patch, hibernate_filter_fix-3.0.5.patch, hibernate_filter_fix-3.0.5_14.patch > > > Currently filter conditions are applied in subselects, they should not be. -- 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

17 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-530) Better handling of filter params in HQL to allow filter use on subqueries

by Shawn Clowater (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Shawn Clowater commented on HHH-530: ------------------------------------ Well, I took a look at this original patch and of course the state of the world changed quite a bit since 3.0.5. However, I think I have something that will work that is much less complex than the original patch. The issue seems to be that once the process filters are done that you can't determine the order of the filters to positional values. But, it looks like all the information is available as the filters are being processed to add both the filters and positional params in the correct order. Essentially the patch is processing the filters in the same manner as it was before but for the positional piece it will add the parameters based on the ordinal value from the positionalValues/Types array as it encounters them. The only changes to QueryParameters are really else { if (token.equals( "?" ) && positionalIndex < getPositionalParameterValues().length) { parameters.add( getPositionalParameterValues()[positionalIndex] ); parameterTypes.add( getPositionalParameterTypes()[positionalIndex] ); positionalIndex++; } result.append( token ); } removal of the parameters.addAll( Arrays.asList( getPositionalParameterValues() ) ); parameterTypes.addAll( Arrays.asList( getPositionalParameterTypes() ) ); and the defining of the positionalIndex int variable. For some reason my IDE wanted to reformat the white space. The first concern I had was what happened if someone mixed and matched positional and named parameters but it would seem the parser disallows that. I don't see any drawback to shuffling the parameters into the right order if all that is being done on the other side is mowing through them in order. Note that this also assumes that the enabled filters are being passed through to the subquery. That is disabled in the latest version of the code. > Better handling of filter params in HQL to allow filter use on subqueries > ------------------------------------------------------------------------- > > Key: HHH-530 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-530 > Project: Hibernate3 > Issue Type: Bug > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Attachments: hibernate_filter_fix-3.0.5.patch, hibernate_filter_fix-3.0.5_14.patch > > > Currently filter conditions are applied in subselects, they should not be. -- 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

17 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-788) formula-based index and lazy="extra"

by Simon Lebettre (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-788?page=co... ] Simon Lebettre commented on HHH-788: ------------------------------------ Update : the previous workaround "some_table.lng_cd" works when you do a get but won't work when you do a put in the extra-lazy map : *** But the syntax <map-key formula="(lng_cd)" type="string"/> (use of parenthesis) will work perfectly for put and get ! explanation : the parenthesis gives you the ability to repeat the same column in the request, without specifying the table name (in the get the table_name is used, but in the put there is an alias based on the class name ) select descriptio0_.lng_cd as lng2_0_, (descriptio0_.lng_cd.lng_cd) as formula0_0_ from some_table descriptio0_ where descriptio0_.id=? ==> This is a crude hack, a true fix would be to let the select clause have duplicate fields when the field is "as formula" . ------- Regards, Simon ( http://www.linkedin.com/in/simonlebettre ) > formula-based index and lazy="extra" > ------------------------------------ > > Key: HHH-788 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-788 > Project: Hibernate3 > Issue Type: Improvement > Components: core > Affects Versions: 3.1 beta 2 > Reporter: Gavin King > Priority: Minor > > Currently, collections with formula-based indexes and lazy="extra" are broken. -- 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

17 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-788) formula-based index and lazy="extra"

by Simon Lebettre (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-788?page=co... ] Simon Lebettre commented on HHH-788: ------------------------------------ Hi. There is a workaround : Just suffix the column name in the formula with the table name. example : instead of <map-key formula="lng_cd" type="string"/> <composite-element class="Description"> <property name="languageCode" column="lng_cd" /> <property name="description" column="prtt_des" /> where "lng_cd" is a column of "some_table" use <map-key formula="some_table.lng_cd" type="string"/> <composite-element class="Description"> <property name="languageCode" column="lng_cd" /> <property name="description" column="prtt_des" /> ------- Regards, Simon ( http://www.linkedin.com/in/simonlebettre ) > formula-based index and lazy="extra" > ------------------------------------ > > Key: HHH-788 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-788 > Project: Hibernate3 > Issue Type: Improvement > Components: core > Affects Versions: 3.1 beta 2 > Reporter: Gavin King > Priority: Minor > > Currently, collections with formula-based indexes and lazy="extra" are broken. -- 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

17 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2007