July 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (HHH-7449) Bad request built from a criteria with a specific mapping

by Nicolas Carlot (JIRA)

11 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-7275) {h-schema} tag is not replaced in discriminator formula

by Glen Leskinen (JIRA)

{h-schema} tag is not replaced in discriminator formula ------------------------------------------------------- Key: HHH-7275 URL: https://hibernate.onjira.com/browse/HHH-7275 Project: Hibernate ORM Issue Type: Bug Reporter: Glen Leskinen It is currently possible to embed {h-schema} in sql defined in <sql-query> tags and have the place holder be replaced by the value of the default_schema property. However, we can place native sql in discriminator formulas and {h-schema} is not replaced there. <discriminator formula="(select d.defn_type_name from {h-schema}defn d where d.defn_id = defn_id)" type="string" /> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] (HHH-7448) hbm mapping xsd improve

by Strong Liu (JIRA)

11 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] (HV-595) Determine how to handle different versions of validation-configuration and validation-mapping xsd

by Hardy Ferentschik (JIRA)

11 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7447) ValueHolder used in NaturalIdCacheKey is not Serializable

by Strong Liu (JIRA)

11 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-900) faceting with manytoone relationship give wrong faceting count

by pragnesh (JIRA)

faceting with manytoone relationship give wrong faceting count -------------------------------------------------------------- Key: HSEARCH-900 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-900 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 4.0.0.Alpha1, 3.4.1.Final, 3.4.0.Final Environment: mysql 5.1.41, linux Reporter: pragnesh Attachments: facet_test.zip faceting with manytoone realtionship give wrong faceting count, although it show correct faceting item, I have create minimal test in hibernate search codebase. Please look into attached zip file,drop java file into corrosponding package and test it. related hibernate forum discussion -> https://forum.hibernate.org/viewtopic.php?f=9&t=1012464 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

5
12
0 / 0

[Hibernate-JIRA] Created: (HHH-2394) Support filter tag in subclass

by Welkin Hu (JIRA)

Support filter tag in subclass ------------------------------ Key: HHH-2394 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2394 Project: Hibernate3 Type: Improvement Components: core Versions: 3.0 beta 4 Reporter: Welkin Hu Assigned to: Steve Ebersole Fix For: 3.0 rc 1 According to a user: http://forum.hibernate.org/viewtopic.php?p=2229539#2229539 It's not possible to get a filter to apply to a subclass. This is Bad ;-) Steve, is that correct? -- 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, 10 months

7
9
0 / 0

[Hibernate-JIRA] Created: (HBX-1123) Reveng foreign-key map to non-primary key column produces incorrect mapping file

by Michael Sabin (JIRA)

Reveng foreign-key map to non-primary key column produces incorrect mapping file -------------------------------------------------------------------------------- Key: HBX-1123 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1123 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.4 Beta1 Environment: Eclipse Platform Version: 3.4.2 Build id: M20090211-1700 Hibernate Tools 3.2.4.GA-R200903141626-H5 Windows XP Pro SP3 JRE 6 Tested on Oracle 10g and Apache Derby Reporter: Michael Sabin Priority: Minor Attachments: CodeGenCfg1.png, CodeGenCfg2.png Creating a mapping from a column in one table to a non-primary key column in another table produces incorrect mapping file missing a property-ref to the non-primary key. How to reproduce using Apache Derby: Create a database and connect to the database. jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine Create these tables in the myDB database, in the ME schema. create table vehicles ( make_id integer, model_id integer, name varchar(50), PRIMARY KEY (make_id, model_id) ); create table owners ( owner_id integer PRIMARY KEY, favorite_make_id integer, name varchar(20) ); -- optional content insert into vehicles values (1, 10, 'Chevrolet Corvette'); insert into vehicles values (2, 11, 'Ford Focus'); insert into vehicles values (3, 12, 'Honda Accord'); insert into vehicles values (4, 13, 'Toyota Camry'); insert into owners values (50, 3, 'Jim'); insert into owners values (51, 1, 'Alex'); insert into owners values (52, 4, 'Sue'); insert into owners values (53, 1, 'Casey'); Create this Hibernate Configuration file. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd"> <hibernate-configuration> <session-factory> <property name="hibernate.connection.driver_class">org.apache.derby.jdbc.EmbeddedDriver</property> <property name="hibernate.connection.url">jdbc:derby://localhost:1527/myDB</property> <property name="hibernate.connection.username">me</property> <property name="hibernate.connection.password">mine</property> <property name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</property> <property name="hibernate.current_session_context_class">thread</property> <property name="hibernate.default_schema">ME</property> <property name="hibernate.show_sql">true</property> </session-factory> </hibernate-configuration> Setup a Hibernate Console Configuration with the configuration above and connection to the Derby database. Create this Hibernate reverse engineering configuration <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-reverse-engineering PUBLIC "-//Hibernate/Hibernate Reverse Engineering DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" > <hibernate-reverse-engineering> <table-filter match-name="OWNERS"/> <table-filter match-name="VEHICLES"/> <table name="VEHICLES"> <foreign-key foreign-table="OWNERS"> <column-ref local-column="MAKE_ID" foreign-column="FAVORITE_MAKE_ID" /> </foreign-key> </table> </hibernate-reverse-engineering> Setup a Hibernate Code Generation configuration like in the attached images. Running the Code Generation configuration will produce this Vehicles.hbm.xml mapping file. <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class name="reveng.Vehicles" table="VEHICLES"> <composite-id name="id" class="reveng.VehiclesId"> <key-property name="makeId" type="int"> <column name="MAKE_ID" /> </key-property> <key-property name="modelId" type="int"> <column name="MODEL_ID" /> </key-property> </composite-id> <many-to-one name="owners" class="reveng.Owners" update="false" insert="false" fetch="select"> <column name="MAKE_ID" not-null="true" /> </many-to-one> <property name="name" type="string"> <column name="NAME" length="50" /> </property> </class> </hibernate-mapping> The many-to-one tag should have this additional attribute: property-ref="favoriteMakeId" -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] (HHH-1829) Allow join on any property using property-ref

by Vadim Lotarev (JIRA)

11 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-625) @OrderBy usage on a joined classes (when using join table) produces incorred SQL syntax.

by Dima Gutzeit (JIRA)

@OrderBy usage on a joined classes (when using join table) produces incorred SQL syntax. ---------------------------------------------------------------------------------------- Key: ANN-625 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-625 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Dima Gutzeit Please consider the following mapping : @ManyToMany(cascade = {CascadeType.PERSIST, CascadeType.MERGE}, fetch = FetchType.LAZY) @IndexColumn(name = "ListIndex") @JoinTable(name = "odp_rulemanipulatorjoin", joinColumns = @JoinColumn(name = "RoutingRuleId"), inverseJoinColumns = @JoinColumn(name = "ManipulatorComponentId")) @OrderBy(value = "priority asc") public List<RoutingManipulationComponent> getManipulators() { if (manipulators == null) { manipulators = new ArrayList<RoutingManipulationComponent>(); } return manipulators; } *********************************** @Entity(name = "RoutingManipulationComponent") @DiscriminatorValue("RoutingManipulationComponent") public abstract class RoutingManipulationComponent extends RoutingComponent implements Initializable { /** * Applies the manipulation to the given context. * * @param context the routing context to manipulate * @return true if any manipulation was applied, false if no manipulation * occurred */ public abstract boolean apply(RoutingContext context); } ****************************************** @Entity(name = "RoutingComponent") @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name = "RoutingComponentType", discriminatorType = DiscriminatorType.STRING) @DiscriminatorValue("RoutingComponent") @Table(name = "odp_routingcomponent") public abstract class RoutingComponent extends DialPlanProvisionalEntity { @Deprecated public RoutingComponent() { // blank } /** * @param name * @param description */ public RoutingComponent(String name, String description) { super(name, description); } } ******************************* @MappedSuperclass @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) public abstract class DialPlanProvisionalEntity extends ProvisionalEntity implements Initializable { private Long entityId; private boolean visible = true; private int priority; /** * Not for direct instantiation - this constructor also serves as public * constructor for hibernate, jax-ws etc. <br> */ @Deprecated public DialPlanProvisionalEntity() { this("(no name set)", "(no description set)"); } /** * @param name * @param description */ public DialPlanProvisionalEntity(String name, String description) { creationDate = GregorianCalendar.getInstance(); // now } @Id @GeneratedValue(strategy = GenerationType.AUTO) @Override public Long getId() { return entityId; } @Override public void setId(Long ruleCollectionId) { this.entityId = ruleCollectionId; } /** * @return Returns the priority. */ public int getPriority() { return priority; } /** * @param priority The priority to set. */ public void setPriority(int priority) { this.priority = priority; } @Override public boolean equals(Object o) { if (this == o) { return true; } if (o == null || Hibernate.getClass(this) != Hibernate.getClass(o)) { return false; } final ProvisionalEntity other = (ProvisionalEntity) o; return MiscUtils.equalOrBothNull(this.getName(), other.getName()); } @Override public int hashCode() { String name = this.getName(); return getClass().getName().hashCode() + 13 * name.hashCode(); } } The above mapping should use the "priority" field to the ordering. SQL that is produced is : select criteria0_.RoutingRuleId as RoutingR1_1_, criteria0_.CriteriaComponentId as Criteria2_1_, criteria0_.ListIndex as ListIndex1_, routingcri1_.id as id73_0_, routingcri1_.creationDate as creation3_73_0_, routingcri1_.description as descript4_73_0_, routingcri1_.lastModificationDate as lastModi5_73_0_, routingcri1_.name as name73_0_, routingcri1_.predefined as predefined73_0_, routingcri1_.status as status73_0_, routingcri1_.priority as priority73_0_, routingcri1_.visible as visible73_0_, routingcri1_.matcher_id as matcher25_73_0_, routingcri1_.criterion_id as criterion27_73_0_, routingcri1_.location_id aslocation26_73_0_, routingcri1_.RoutingComponentType as RoutingC1_73_0_ from odp_rulecriteriajoin criteria0_ left outer join odp_routingcomponent as routingcri1_ on criteria0_.CriteriaComponentId=routingcri1_.id where criteria0_.RoutingRuleId=1 order by odp_routingcomponent .priority asc It is wrong since not the table alias is used in the order by clause, but the real table name. Mysql fails with exception that odp_rulecriteriajoin.priority is unknown table. Changing the query to include "order by criteria0_.priority asc" returns the correct result. -- 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, 10 months

9
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2012