May 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2308) Adjusting the Outer Join Predicate using Criteria Query

by Ben Grant (JIRA)

Adjusting the Outer Join Predicate using Criteria Query ------------------------------------------------------- Key: HHH-2308 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2308 Project: Hibernate3 Type: New Feature Components: query-criteria Versions: 3.2.1 Environment: Linux Using MS SQLServer Reporter: Ben Grant I have two tables Table A ||Col_1||Col_2|| |London| UK | |Liverpool| UK | | New York | USA | Table B ||Col_1||Col_2|| Col_3|| | UK | Europe | 0 | USA | Americas | 1 Using the Criteria class, Restriction Class and FetchMode, Hibernate manages to create a query that looks like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 where TableB3_.Col_3=1 When really i need the query to be like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 AND TableB3_.Col_3=1 currently their isn't any know way for hibernate to adjust or apply filters within the join 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

11 years, 11 months

12
27
0 / 0

[Hibernate-JIRA] Created: (HBX-939) Composite IDs and many-to-many relationships

by Markus Kramer (JIRA)

Composite IDs and many-to-many relationships -------------------------------------------- Key: HBX-939 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-939 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2beta9 Environment: Hibrnate 3.2.1, Postgresql 8.1.8 Reporter: Markus Kramer Attachments: B.hbm.xml, testdb.sql The detection of many-to-many relationships doesn't work correctly if the primary key of one of the involved tables consists of more than one field. An example: One of two tables (table 'A') of a many-to-many relationship has a primary key consisting of two attributes (id1 and id2). The generated B.hbm.xml for the table 'B' contains this: <set name="as" inverse="true" table="a_b"> <key> <column name="b_id" not-null="true" /> </key> <many-to-many entity-name="test.A"> <column name="a_id1" not-null="true" /> </many-to-many> </set> But there should be another entry for the referenced primary key: <column name="a_id2" not-null="true" /> The SQL code for the used tables and the complete B.hbm.xml are attached. -- 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

11 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2058) puhs SessionImplementor.getInterceptor up into Session

by Max Rydahl Andersen (JIRA)

puhs SessionImplementor.getInterceptor up into Session ------------------------------------------------------ Key: HHH-2058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2058 Project: Hibernate3 Type: Improvement Components: core Reporter: Max Rydahl Andersen Being able to get the actual interceptor used for a certain Session is beneficial. any reason why it is not exposed on Session ? -- 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

11 years, 12 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-537) Support @Comment or column attribute on @Table and @Column

by Max Rydahl Andersen (JIRA)

Support @Comment or column attribute on @Table and @Column ---------------------------------------------------------- Key: ANN-537 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-537 Project: Hibernate Annotations Type: Improvement Components: binder Versions: 3.2.1 Reporter: Max Rydahl Andersen with hbm2ddl and hbm2doc its a shame that Annotation does not support setting a comment on table and columns. -- 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

12 years

9
22
0 / 0

[Hibernate-JIRA] Created: (HHH-2331) bulk deletes on ID must not use HT_ tables

by Amir Pashazadeh (JIRA)

bulk deletes on ID must not use HT_ tables ------------------------------------------ Key: HHH-2331 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2331 Project: Hibernate3 Type: Improvement Components: core Reporter: Amir Pashazadeh when using bulk deletes hibernate inserts ids of rows which must be deleted in a temporary table (with HT_ prefix); I believe that's just for knowing primary keys of objects which must be deleted and updating caches. so if that is the reason there is no need to do so when deleting on primary key property, (for example "delete from MyEntity where id = ?") -- 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

12 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2049) LEFT OUTER JOIN subcriteria filters children

by Mattias Jiderhamn (JIRA)

LEFT OUTER JOIN subcriteria filters children -------------------------------------------- Key: HHH-2049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2049 Project: Hibernate3 Type: Bug Components: query-criteria Versions: 3.1.3, 3.2.0.cr4 Environment: Hibernate 3.1.3/3.2.0rc4, hsqldb 1.8 Reporter: Mattias Jiderhamn Attachments: SubCriteriaTestCase.zip When using the Criteria API with LEFT OUTER JOIN to add criterias to the children, i.e. criteria.createCriteria("children", JoinFragment.LEFT_OUTER_JOIN) the child collections will only contain those children matching the criteria. (Even when *not* using any Filters). The attached testcase (also found here: http://forum.hibernate.org/viewtopic.php?p=2320786) will explain it in more detail. -- 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

12 years, 1 month

13
52
0 / 0

[Hibernate-JIRA] Created: (HHH-2223) BatchFetchQueue.getXXXBatch() cache check impeding batch fetching

by Joel Caplin (JIRA)

BatchFetchQueue.getXXXBatch() cache check impeding batch fetching ----------------------------------------------------------------- Key: HHH-2223 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2223 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: 3.2.0GA, Mac OS X/Solaris 10, Sybase 12.5/HSQLDB Reporter: Joel Caplin Priority: Minor Attachments: testcase.tar I have attached a test case which demonstrates the issue at hand by implementing a cheap data model: Pub >---|- Manager -|--< Employee Pub and Employee are uncached; Manager is cached (tried under both Eh and the non-prod HashMap implementation). All associations are lazy. The test case has a default batch size of 10 and uses hsqldb to demonstrate the problem - which was diagnosed against Sybase. When BatchFetchQueue.getXXXBatch() is invoked, it does not load any objects it finds in the second level cache - it merely acknowledges their presence by logging to INFO (isCached()). This in turn means that any child associations in that cached object will not have a proxy created for them. Suppose we want to find all the employees of the pubs in our database. We choose to do this by loading all the Pubs ("FROM Pub") and calling thePub.getManager().getEmployees() iteratively. When the managers are in the second level cache, Hibernate issues 11 select statements: one to load the pubs and one for each distinct manager. When the Managers are not in the cache, Hibernate issues 3 select statements: one to load the pubs, one to load the managers and one to load the employees. A solution might be to load the object from the cache instead of just ignoring 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

12 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2280) Not-Null Constraint-Violation with unidirectional one-to-many mapping

by Robert Herschke (JIRA)

Not-Null Constraint-Violation with unidirectional one-to-many mapping --------------------------------------------------------------------- Key: HHH-2280 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2280 Project: Hibernate3 Type: Bug Versions: 3.2.0.cr4 Environment: Hibernate 3.2.0.cr4, Oracle 10XE Reporter: Robert Herschke Priority: Blocker Attachments: one-to-many-test.zip In some cases it is neccessary to have an unidirectional one-to-many mapping, but not using Join-Tables due to a legacy database system. So it must be possible, to have a one-to-many mapping just via a foreign-key-mapping. The Child-Object must not know the Parent-Object in this case. It must also be possible, to pay respect to a NOT-NULL-Constraint at this foreign-key due to restrictions on legacy database systems. Hibernate doesn't support this, but throw a NOT-NULL-Constraint Violation Exception. The documentation says, "this is unusual" - to which I want to dissent. See the attached testcase for details, that is adopted from your "one-to-many" testcase found in the 3.2.0 sources. -- 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

12 years, 2 months

5
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2165) Change logging level in TableMetadata from INFO to DEBUG or TRACE

by Igor A Tarasov (JIRA)

Change logging level in TableMetadata from INFO to DEBUG or TRACE ----------------------------------------------------------------- Key: HHH-2165 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2165 Project: Hibernate3 Type: Improvement Components: metamodel Versions: 3.2.0.ga Reporter: Igor A Tarasov TableMetadata produce too many output to INFO log level. It good thing if it output be at DEBUG level to not hide other impotant information as service start/stop and other. 20.10.06 18:01:58 INFO [main]: SchemaUpdate - updating schema 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.ChageDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, _version, chagedate, created, service, sum, restbalance, comment, customer_id] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, fk8f40c06527214c11, chagedate, primary] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.CustomerDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [phone, firm, group_id, deleted, fio, id, balance, created, updated, address, email, name, comment] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, primary, fk1892e50924b4a799, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.GroupDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, updated, created, name, comment, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, primary, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.HostDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [tarif_id, server_id, ips, mac, deleted, id, created, updated, name, lastactive, comment, disabled, customer_id] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [ips, name, primary, fk812f2053f280a3b1, mac, deleted, fk812f205327214c11, fk812f20537f1e2ff9] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.HostSessionDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, host_id, starttime, chage, speedou, updatetime, speedin, bytesin, stoptime, bytesou, version] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [fk9a9074b995d39b51, id, primary] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.LoginDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, nickname, updated, created, name, comment, password, deleted, customer_id, disabled] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, name, primary, fk77a0599427214c11, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.PPPAccountDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [tarif_id, login_id, id, server_id, updated, created, comment, deleted, disabled, ip] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, fk507abf087f1e2ff9, primary, fk507abf08f280a3b1, fk507abf08820174d9, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.PPPSessionDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [callerid, starttime, account_id, updatetime, speedou, chage, speedin, stoptime, bytesou, version, ip, id, ident, bytesin] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, fke19b413144f3fa61, starttime, ident, updatetime, primary, stoptime] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.PaymentDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, _version, created, nalichka, sum, paydate, comment, newbalance, customer_id] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, fk7249f0f127214c11, primary, paydate] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.ServerDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, updated, created, name, comment, deleted, ip] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, name, primary, deleted, ip] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.TarifDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [costsizein, resetprepaidsize, prepaidsizerest, moncost, resetprepaidusages, costusage, resetprepaidtime, deleted, prepaidtimemonthly, costtime, prepaidsizemonthly, id, prepaidusagesrest, monthenddate, costsizeou, created, updated, name, prepaidtimerest, prepaidusagesmonthly, comment, customer_id] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, primary, fk7893f6d27214c11, deleted] 20.10.06 18:01:58 INFO [main]: SchemaUpdate - schema update complete -- 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

12 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-935) H2MetaDataDialect for identity detection

by Max Rydahl Andersen (JIRA)

H2MetaDataDialect for identity detection ---------------------------------------- Key: HBX-935 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-935 Project: Hibernate Tools Issue Type: Sub-task Components: reverse-engineer Affects Versions: 3.2beta9 Reporter: Max Rydahl Andersen Fix For: 3.2beta10 -- 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

12 years, 3 months

4
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2007