April 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5428) collection tables are improperly non-quoted when the owning table is quoted

by Emmanuel Bernard (JIRA)

collection tables are improperly non-quoted when the owning table is quoted --------------------------------------------------------------------------- Key: HHH-5428 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5428 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.0.Beta1, 3.5.4 Reporter: Emmanuel Bernard Fix For: 3.6.0.Beta2 -- 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

2
18
0 / 0

[Hibernate-JIRA] Created: (HHH-5352) Misleading replacement of commas with cross joins

by Patras Vlad (JIRA)

Misleading replacement of commas with cross joins ------------------------------------------------- Key: HHH-5352 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5352 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2 Environment: Hibernate 3.5.3 Ms SQL Server 2005 Reporter: Patras Vlad There was a new feature implemented in 3.5.0-Beta-2: HHH-1480, as a result, for many dialects, the comma operator "," was replaced with "cross join". As it's already obvious from the feature's description, this changes join precedence. If the query contains outer joins (left or right) this replacement changes the results (because outer join precedence is important). This might not be interpreted as a bug if you know what SQL operator will be generated when you place a comma in HQL, but it's misleading if you don't. A HQL query like: {noformat}select a from A a, B left join B.c c{noformat} is not equivalent with the SQL query: {noformat}select a.* from A.a, B b left join C c on b.cid = c.id{noformat} because the actual SQL query is: {noformat}select a.* from A.a cross join B b left join C c on b.cid = c.id{noformat} The first SQL query would make a left join on B and C and then a cross join with the result and A (and this is what we should expect). The second SQL query makes a cross join on A and B and then a left join with the result and C (this is not expected since we had a comma in HQL). I understand the issues presented in HHH-1480, but they should be expected, i.e. a developer SHOULD expect a faliure from a query like {noformat}select a from A a, B b join a.c C{noformat} because "a" is not visible in the join. Hibernate should not use a cross join behind the scenes to allow such a query at the expense of providing misleading results for others. Maybe turn this into a feature/improvement or add another to allow explicit comma or croos join in HQL, or support parenthesis in HQL. The only workaround I can see for now is to re-order the query like this: {noformat}select a from B left join B.c c, A a{noformat} -- 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

3
14
0 / 0

[Hibernate-JIRA] Created: (HHH-6090) cleanup unnecessary uses of debugf / tracef

by Steve Ebersole (JIRA)

cleanup unnecessary uses of debugf / tracef ------------------------------------------- Key: HHH-6090 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6090 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Steve Ebersole Assignee: John Verhaeg Fix For: 4.0.0.Alpha3 I have cleaned up cases already where debugf is used when it is totally not needed. We need to make sure that is the case everywhere as this is a potential perf impact -- 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

1
2
0 / 0

[Hibernate-JIRA] Closed: (HHH-468) MysqlDialect incorrectly maps java.lang.Boolean to SQL BIT

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-468?page=co... ] Steve Ebersole closed HHH-468. ------------------------------ Resolution: Fixed > MysqlDialect incorrectly maps java.lang.Boolean to SQL BIT > ---------------------------------------------------------- > > Key: HHH-468 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-468 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.0.3 > Environment: Hibernate 3.0, MySQL. > Reporter: Mark Matthews > Assignee: Steve Ebersole > Fix For: 4.0.0.Alpha3 > > Time Spent: 38m > Remaining Estimate: 0h > > I didn't track down how java.lang.Boolean gets mapped to Types.BIT in hibernate, but you probably _don't_ want to map to "bit" like you do in MysqlDialect. > "bit", according to SQL99 (it's not in the core standard, and the type was actually dropped for sql2k3) is a bitfield, not a boolean value. You can of course define a bit(1), but it is technically more correct for java.lang.Boolean to map to a SQL BOOLEAN for MySQL since we support a BOOLEAN and a BIT. > It looks like the JDBC-3.0 guys ignored what the standard said, because in reality you'd want BIT to map to something like byte[], or java.util.BitSet if you were tracking how the SQL standard defines BIT. > I'm guessing you probably want to map to "boolean", which the JDBC driver will automagically convert for you, as it silently maps to TINYINT(1) on the server side. -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (OGM-42) Add support for Date and Calendar types

by Emmanuel Bernard (JIRA)

Add support for Date and Calendar types --------------------------------------- Key: OGM-42 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-42 Project: Hibernate OGM Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 1.0-next -- 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

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4073) discriminator formula creates problem in hibernate envers

by Saravana Kumar (JIRA)

discriminator formula creates problem in hibernate envers --------------------------------------------------------- Key: HHH-4073 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4073 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.x Environment: hibernate-3.3.x, envers-1.2.1.ga-hibernate-3.3.jar (Oracle 10g or HSQLDB) Reporter: Saravana Kumar I map my classes using Single Table per class hierarchy as below @Entity @DiscriminatorFormula ("(select t.c_type from t_type t where t.c_id = c_type)") @Audited public class Attribute...{ ... } or <discriminator type="string"> <formula>(select t.c_type from t_type t where t.c_id = c_type)</formula> </discriminator> When I use envers I get the follwoing error Caused by: java.lang.ClassCastException: org.hibernate.mapping.Formula at org.hibernate.envers.configuration.metadata.MetadataTools.addColumns(MetadataTools.java:154) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.generateMappingData(AuditMetadataGenerator.java:263) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.generateFirstPass(AuditMetadataGenerator.java:345) at org.hibernate.envers.configuration.EntitiesConfigurator.configure(EntitiesConfigurator.java:87) at org.hibernate.envers.configuration.AuditConfiguration.(AuditConfiguration.java:86) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:99) at org.hibernate.envers.event.AuditEventListener.initialize(AuditEventListener.java:260) at org.hibernate.event.EventListeners$1.processListener(EventListeners.java:198) at org.hibernate.event.EventListeners.processListeners(EventListeners.java:181) at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:194) When I tried to debug the problem (AuditMetadataGenerator.java:263) has 260: // Checking if there is a discriminator column 261: if (hasDiscriminator) { 262: Element discriminator_element = class_mapping.addElement("discriminator"); 263: MetadataTools.addColumns(discriminator_element, pc.getDiscriminator().getColumnIterator()); 264: discriminator_element.addAttribute("type", pc.getDiscriminator().getType().getName()); 265: } (MetadataTools.java:154) has 152: public static void addColumns(Element any_mapping, Iterator<Column> columns) { 153: while (columns.hasNext()) { 154: Column column = columns.next(); 155: addColumn(any_mapping, column.getName(), column.getLength(), column.getScale(), column.getPrecision(), 156: column.getSqlType()); 157: } 158: } I see that there is nothing to handle Formula :-( Can you investigate? -- 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

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6093) Account for tenant identifier on QueryKey

by Steve Ebersole (JIRA)

Account for tenant identifier on QueryKey ----------------------------------------- Key: HHH-6093 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6093 Project: Hibernate Core Issue Type: Bug Components: caching (L2), core Affects Versions: 4.0.0.Alpha2 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 -- 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

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6106) Fix up IntelliJ project generation

by Steve Ebersole (JIRA)

Fix up IntelliJ project generation ---------------------------------- Key: HHH-6106 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6106 Project: Hibernate Core Issue Type: Improvement Components: build Affects Versions: 4.0.0.Alpha2 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 -- 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

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6095) Improve the way AbstractEntityManagerImpl.flush checks for an active transaction, should apply to other AbstractEntityManagerImpl methods that also check for an active tx

by Scott Marlow (JIRA)

Improve the way AbstractEntityManagerImpl.flush checks for an active transaction, should apply to other AbstractEntityManagerImpl methods that also check for an active tx -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6095 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6095 Project: Hibernate Core Issue Type: Bug Affects Versions: 4.0.0.Alpha2, 3.6.3 Reporter: Scott Marlow Fix For: 3.6.4, 4.0.0.Alpha3 Suggested change is here https://gist.github.com/907193 -- 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

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6118) Make Metadata more user-friendly API

by Steve Ebersole (JIRA)

Make Metadata more user-friendly API ------------------------------------ Key: HHH-6118 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6118 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 -- 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

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2011