May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5261) Miscellaneous typos and a handful of minor content issues

by David M. Karr (JIRA)

Miscellaneous typos and a handful of minor content issues --------------------------------------------------------- Key: HHH-5261 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5261 Project: Hibernate Core Issue Type: Bug Components: documentation Affects Versions: 3.5.2 Reporter: David M. Karr Priority: Minor This is a collection of typos and minor content issues found in the current Hibernate doc. Technically, this represents multiple issues, but I'm not going to file one ticket for every typo I found. Section 1.1.4, p. 7, first "Note": Change "... this do that ..." to "... this so that ...". Section 1.2.4, p. 19, last paragraph. This paragraph has the first mention of "eager fetch" in the manual, but without any explanation. In a tutorial, it's confusing to mention technical terms without any background, and even worse when a technical term doesn't even sound like a technical term. Section 1.3.1, p. 20, change "... need create ..." to "... need to create ...". Section 1.3.1, p. 21, first code sample. Using "ServletException.class.isInstance(ex)" here seems odd. Why don't you use the more common "ex instanceof ServletException"? The dynamic form is only useful when the class is in a variable. Section 1.3.1, p. 21, paragraph beginning "The pattern applied here ...". The last sentence in this paragraph seems strange here. It refers to not using "auto-commit", which is at least related to the subject of the paragraph, being "session-per-request", but it seems like it was placed in this paragraph accidentally. Section 4.1.1, p. 52. This paragraph repeats a common misstatement I see in much of the Java literature. The statement "All persistent classes must have a default constructor" is incorrect. It should be "All persistent classes must have a no-arguments constructor". The "default constructor" is the constructor that the compiler creates in a class if no constructor is defined. The default constructor is a no-arguments constructor, but the point is that persistent classes need a no-arguments constructor, not a "default constructor". Section 5.1.3, p. 65, definition of "batch-size". This explanation is confusing. It says "... for fetching instances of this class by identifier." Fetching instances of a class by an identifier value will only ever get one (or zero) rows. Section 5.1.3, p. 65, definition of "rowid". Is this explanation correct? It says "... once this option has been set to rowid.". You enable the "rowid" property by setting it to "rowid"? If that's true, it would be helpful to emphasize that. Most people would read that and be confused. Section 5.1.4.5, p. 71. Change "The generator is used ..." to "This generator is used ...". Section 5.1.5, p. 71, paragraph beginning "The first of these new ...". Change "portability generator" to, perhaps, "identity generator". "portability generator", what a concept. :) Section 5.1.13, p. 82, "constrained" definition. Change "... table and references ..." to "... table references ...". Section 11.1, p. 164, change "... already in the in the session ..." to "... already in the session ...". Section 11.1.1, p. 164. Change "... class can created ..." to "... class can be created ...". Chapter 12, p. 173, second paragraph. The paragraph ends with "... Hibernate provides repeatable reads for lookup by identifier and entity queries and not reporting queries that return scalar values." The "not reporting" part doesn't seem to make sense. I can't tell what this was supposed to say. Section 12.4, p. 185, change "... it never lock objects ..." to "... it never locks objects ...". Section 15.10, p. 209. The "simple" case and the "searched" case both refer to an abbreviated code excerpt, which I would assume should not be the same. They appear to be identical, so what exactly is this saying then? Section 15.16, p. 218, code sample after "Properties of a JavaBean can be bound to named query parameters". The query expression begins "from foo Foo as foo ...". That seems wrong. I think it should be "from Foo as foo ...". Section 15.18, p. 219, code sample after "It can also be useful to specify this in the select clause ...". This section is about the row value constructor syntax. This example doesn't appear to demonstrate a row value constructor. It just says "select p.name from Person p". Section 16.4, p. 224. Change "... retreive the cats with mates who's name ..." to "... retrieve the cats with mates whose name ...". Section 16.6, p. 225. Concerning the reference to "enableLike()", it would be useful to state exactly what this does, instead of just "use like for string comparisons". Logic tells me that it would do "like '%value%'", but it would be useful to confirm that. Section 17.1.4.1, table 17.1, change "The id of an collection" to "The id of a collection". Similarly, on the next page in the same table, change "The element of an collection" to "The element of a collection". Section 20.1.7, p. 258, change "... fetch profile wull be ..." to "... fetch profile will be ...". Section 20.1.7, p. 259, change "... but they plan is ..." to "... but the plan is ...". Section 20.4.1, p. 265, change "... For this reaso, ..." to "... For this reason, ...". Section 20.5.4, p. 268. Change "... then add thee ..." to "...then add these ...". Section 22.2, p. 280, change "... the link (the foreign key parent_id) from p to c ..." to "... the link (the foreign key parent_id) from c to p ...". Chapter 25, p. 305, change "... but his approach ..." to "... but this approach ...". p. 306, in 'explicitly disable eager fetching using lazy="false"', change it to "disable lazy" or "enable eager". Section 26.4, change "targtetting" to "targeting" and change "entitiy" to "entity". In the second "Note" change "enhancedgenerators" to "enhanced generators". Section 26.5, p. 311. Change "Hibernate, provides ..." to "Hibernate provides ...". -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-320) JPATraversableResolver fails if the annotated property does not have a getter

by Hardy Ferentschik (JIRA)

JPATraversableResolver fails if the annotated property does not have a getter ------------------------------------------------------------------------------ Key: HV-320 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-320 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.1.0 Using HV in combination with the latest Entity Manager you seems to get an exception in case your validation is on a property which does not define a getter - see https://forum.hibernate.org/posting.php?mode=reply&f=9&t=1004480 -- 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, 11 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-529) Support NumericField

by Emmanuel Bernard (JIRA)

Support NumericField -------------------- Key: HSEARCH-529 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-529 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.3.0 Maybe via a qualifier annotation (problematic for multiple field mappings per property) {code} @Numeric(precisionStep) {code} OR is there a more generic approach to support further parameterizable fields? -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5241) One-to-many relationship to class with JOINED inheritance causes assertion failure in JoinedSubclassEntityPersister

by Stu White (JIRA)

One-to-many relationship to class with JOINED inheritance causes assertion failure in JoinedSubclassEntityPersister ------------------------------------------------------------------------------------------------------------------- Key: HHH-5241 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5241 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-CR-1 Environment: Hibernate 3.5.0-CR1 (included with JBoss Application Server 6.0.0 M2) SQL Server 2005 Reporter: Stu White Attachments: testcase.zip I've created a JPA mapping for a class that has a one-to-many relationship via a join table to other classes which are using a JOINED inheritance strategy, and I'm getting an odd error which makes me wonder whether I've come across a bug in Hibernate. The particular error I'm getting is: Exception in thread "main" 2010-05-20 10:00:04,783 - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: Table JpaTest.ParentOwnerJoinTable not found at org.hibernate.persister.entity.JoinedSubclassEntityPersister.getTableId(JoinedSubclassEntityPersister.java:497) at org.hibernate.persister.entity.JoinedSubclassEntityPersister.<init>(JoinedSubclassEntityPersister.java:276) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:87) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:272) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1385) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:974) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:850) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:56) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:48) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:32) at com.i2group.jpatest.JpaTestBase.createEntityManager(JpaTestBase.java:51) at com.i2group.jpatest.JpaOwnershipInheritanceTest.writeEntity(JpaOwnershipInheritanceTest.java:28) at com.i2group.jpatest.JpaOwnershipInheritanceTest.main(JpaOwnershipInheritanceTest.java:22) I've attached a zip containing the classes, persistence XML, and SQL Server setup script. The classes are: Owner The owner linked by a one-to-many relationship to Parent/ChildOne/ChildTwo Parent Parent class using a JOINED inheritance strategy ChildOne Child of Parent ChildTwo Child of Parent The error only seems to occur when combining a one-to-many relationship via a join table to a class using inheritance. If I remove the link to Owner and just test the inheritance of Parent/ChildOne/ChildTwo then it works fine. If I remove the inheritance and just test the one-to-many relationship from Owner to Parent then it works fine. If I try to combine the two then I get the error above. I don't think I'm doing anything particularly obscure, which makes me suspicious that this is more likely to be a mistake in my configuration than a bug in Hibernate. However, I've checked the configuration and tested parts of it separately and have been unable to find what (if anything) I'm doing wrong. If there's any further information I can provide to help diagnose this then please let me know. -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-325) Align javadoc styles with the Core javadoc styles

by Hardy Ferentschik (JIRA)

Align javadoc styles with the Core javadoc styles ------------------------------------------------- Key: HV-325 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-325 Project: Hibernate Validator Issue Type: Task Components: documentation Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.2.0 On top of this we could deploy a version of the BV javadocs and link the HV javadocs to it when building the documentation. -- 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, 11 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2645) Synchronization bottleneck in EntityModeToTuplizerMapping

by Erik Bergersjö (JIRA)

Synchronization bottleneck in EntityModeToTuplizerMapping --------------------------------------------------------- Key: HHH-2645 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2645 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.4.sp1, 3.2.4, 3.2.3 Environment: Hibernate 3.2.3 (and later), Sun's JDK 1.4.2_12 (server VM) on SunOS 5.10, Oracle 10g R2 Reporter: Erik Bergersjö Priority: Minor We have had a major performance bottleneck in EntityModeToTuplizerMapping with Hibernate version 3.2.3 and the code for that class in 3.2.4sp1 is unchanged. We have found a solution that solves the issue and would like to get it into the real version. I submitted to the user forum first and was asked to create a JIRA issue. The problematic line is: private final Map tuplizers = Collections.synchronizedMap( new SequencedHashMap() ); We have changed it to (using util.concurrent): private final Map tuplizers = new EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap(); This change alone makes our use cases six times faster. The difference is that ConcurrentReaderHashMap handles concurrent readers much better, they don't have to wait for each other. The problem occurs when a high number of threads try to initialize sets (see mapping below). A thread dump showed a high number of threads waiting for the same monitor, see partial stack trace below. The code runs on Sun's JDK 1.4.2_12 (server VM) on SunOS 5.10 and the kernel spends a lot of time handling mutexes with the original implementation. That time disappears from the radar screen with the fixed version. Example mapping for set: [code] <set name="lines" lazy="true" inverse="true" cascade="all-delete-orphan"> <key> <column name="col1" not-null="true" /> <column name="col2" not-null="true" /> </key> <one-to-many class="LineClass" /> </set> [/code] Stack trace (partial): "Thread-108" prio=5 tid=0x05852e90 nid=0x103 waiting for monitor entry [0x3ed7e000..0x3ed7fc28] at java.util.Collections$SynchronizedMap.get(Collections.java:1942) - waiting to lock <0x89d30788> (a java.util.Collections$SynchronizedMap) at org.hibernate.tuple.EntityModeToTuplizerMapping.getTuplizerOrNull(EntityModeToTuplizerMapping.java:53) at org.hibernate.tuple.EntityModeToTuplizerMapping.getTuplizer(EntityModeToTuplizerMapping.java:66) at org.hibernate.type.ComponentType.getPropertyValues(ComponentType.java:353) at org.hibernate.type.ComponentType.isEqual(ComponentType.java:141) at org.hibernate.engine.CollectionKey.equals(CollectionKey.java:50) at java.util.HashMap.eq(HashMap.java:274) at java.util.HashMap.get(HashMap.java:323) at org.hibernate.engine.loading.CollectionLoadContext.getLocalLoadingCollectionEntry(CollectionLoadContext.java:163) at org.hibernate.engine.loading.CollectionLoadContext.locateLoadingCollectionEntry(CollectionLoadContext.java:150) at org.hibernate.engine.loading.CollectionLoadContext.getLoadingCollection(CollectionLoadContext.java:92) at org.hibernate.loader.Loader.readCollectionElement(Loader.java:1003) at org.hibernate.loader.Loader.readCollectionElements(Loader.java:646) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:591) at org.hibernate.loader.Loader.doQuery(Loader.java:701) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.loadCollection(Loader.java:1994) at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:36) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:565) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1716) at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) at org.hibernate.collection.PersistentSet.iterator(PersistentSet.java:163) -- 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, 11 months

8
28
0 / 0

[Hibernate-JIRA] Created: (HHH-3050) Convert usage of Hibernate's FastHashMap to ConcurrentHashMap (Java 1.5)

by Gail Badner (JIRA)

Convert usage of Hibernate's FastHashMap to ConcurrentHashMap (Java 1.5) ------------------------------------------------------------------------ Key: HHH-3050 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3050 Project: Hibernate3 Issue Type: Improvement Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.3 The performance test attached to HHH-2645 shows that java.util.concurrent.ConcurrentHashMap (introduced in Java 1.5) performs nearly as well as org.hibernate.util.FastHashMap. Hibernate needs to move to Java 1.5 before this can be done. As noted in HHH-2645, it might be worthwhile to convert usages of FastHashMap to ConcurrentHashMap so that FastHashMap does not need to be maintained. -- 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, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5243) Hiberate Second level Cache refresh

by Calvin Ye (JIRA)

Hiberate Second level Cache refresh ----------------------------------- Key: HHH-5243 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5243 Project: Hibernate Core Issue Type: Improvement Environment: Hibernate 3 Reporter: Calvin Ye -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5250) On setting a String-Value for a integer entity-field in a criterion, produces a ClassCastException, see also HHH-5238

by Hannes Havel (JIRA)

On setting a String-Value for a integer entity-field in a criterion, produces a ClassCastException, see also HHH-5238 --------------------------------------------------------------------------------------------------------------------- Key: HHH-5250 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5250 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Reporter: Hannes Havel SEE HHH-5238 Hi Gail, I am not agree you, that this is not a BUG. I am not amused that you switch the issue HHH-5238 to resolved, with out any explanation of your view. Second: your reference, that i should use the forum for help is not on the right place. because i know, what a question is and what a bug report is. (I have 20 year of experiance in software development). ================================================ Explanation of my view: In this case the string consists only numbers and representing a integer number of e.g. "10" and this can be converted to a integer 10 and i am not speaking about to convert a text string to an integer. JDBC an do this easily. Is hibernate so restricted ? How you can establish a generalized query interface where only strings are transported and the provided service has no knowledge about the queried entities and the datatypes of the fields. So i think a automatic conversion of a string representing a number to the nhumber type and so on is a esential funktionality for a data sorage and retrieve interface. For Hibernate the only thing to be changed for the primitive datatype handling is explaind in the following code snipplet: IntegerType.set(PreparedStatement st, Object value, int index) throws SQLException { if (value instanceof String) st.setInt( index, Integer.parseInt((String)value)); else st.setInt( index, ( (Integer) value ).intValue() ); } -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5249) Component.java MappingException needs more detail

by Travis Stevens (JIRA)

Component.java MappingException needs more detail ------------------------------------------------- Key: HHH-5249 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5249 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.2, 3.5.0-Final Environment: Hibernate version: 3.5.0-Final Reporter: Travis Stevens Priority: Trivial Attachments: mrxtravis-component.patch A MappingException is thrown in the Component.java class that looks like such: throw new MappingException("component property not found: " + propertyName); I received this message when the property was 'id' -- and since every component has an 'id', this was not a very useful message. I'm supplying a patch that will add the componentClassName property of Component to the exception as to put the property in a useful context. The fix is : throw new MappingException("component " + componentClassName + " property not found: " + propertyName); See attachment for the patch to 3.5.0-Final -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5247) Schema validator doesn't check indices or unique keys

by Ian Haken (JIRA)

Schema validator doesn't check indices or unique keys ----------------------------------------------------- Key: HHH-5247 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5247 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.x Reporter: Ian Haken Attachments: validation.patch The schema validator currently only checks that the columns in the persistence store exist and have the correct data types. I'm not sure if it's a bug or intended behavior (in which case this would be an enhancement), but the validator doesn't check that indices and unique keys also exist (with the correct names referring to the correct columns). I've attached a patch which would add this to the validation procedure. Comments welcome. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5242) NamingHelper writes credential information to the log

by Yiming Du (JIRA)

NamingHelper writes credential information to the log ----------------------------------------------------- Key: HHH-5242 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5242 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: This should be a general issue across all platform. Reporter: Yiming Du In certain situations, the class NamingHelper will write credential information to the log. To be more specific, in the method getInitialContext() of the class org.hibernate.util.NamingHelper, there're following 2 lines Hashtable hash = getJndiProperties(props); log.info("JNDI InitialContext properties:" + hash); This will result in the clear text of the credential information in the conditions that the credential properties are set and the log level is lower than INFO. In our Websphere scenario, because Websphere is security enabled, we need to set the following properties "hibernate.jndi.java.naming.security.principal" "hibernate.jndi.java.naming.security.credentials" in order to register the SessionFactory to the JNDI tree. (Another thread https://forum.hibernate.org/viewtopic.php?f=1&t=931740&start=0 gives some description about this situation as well). Although it's harmless to functionality, it undermines to some degree the overall security. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1134) subclass tag with discriminator in one to many mapping

by HG (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134?page=c... ] HG commented on HHH-1134: ------------------------- Thanks Gail, Its infact related to HH-4953 A better work around would be somthing like : if (clazz.isInstance(result)) { return result; } return null; And not cathing the ClassCastException In my opinion, It would be best to have cache per concrete class with discriminator value, and not a cache per class hierachy. This would help having CacheKeys characterized by their class names and not root class names, hence making this discriminator concept workable on second level cache. This would ofcourse mean a lot more work while querying caches using a Super classes. But frankly, I dont know the real impact on performance it will cost. > subclass tag with discriminator in one to many mapping > ------------------------------------------------------ > > Key: HHH-1134 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134 > Project: Hibernate Core > Issue Type: Bug > Components: core > Environment: hibernate 3.0.5, Oracle > Reporter: Dilip Ranjith > > Consider the following hbm.xml file > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping > > > <class > name="DCDTO" > table="ACCDC" > dynamic-update="true" > > > <id > name="ID" > type="java.lang.String" > > > <column > name="DCINFOID" > /> > <generator class="sequence"> > <param name="sequence">DSEQ</param> >  > </generator> > </id> > <discriminator > column="accountType" > not-null="true" > type="java.lang.String" > force="true" > insert="true" > /> > <property > name="creditMax" > type="java.lang.Double" > update="true" > insert="true" > column="creditMax" > /> > <subclass > name="CDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="C" > > > </.subclass> > <subclass > name="DDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="D" > > > </.subclass> > </class> > </hibernate-mapping> > DCDTO is the super class while DDTO and CDTO are its child classes > If in a mapped object say TDTO there are a set of CDTOs and a separate set of DDTOs > when we get TDTO the where clause "where accountType='D' " is not there when the query for set of DDTOs are generated. so instead of a set of DDTOs i am getting a set of both DDTO's and CDTO's -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5240) FetchProfile should also support LAZY

by Marc Schipperheyn (JIRA)

FetchProfile should also support LAZY ------------------------------------- Key: HHH-5240 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5240 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.2 Reporter: Marc Schipperheyn Currently initial support for FetchProfile.JOIN is available and SELECT and SUBSELECT are planned. I would like to make the case for including LAZY. Basically JOIN, SELECT and SUBSELECT assume the default setting is lazy and depending on profile a different execution mode is selected. The following example shows why you are sometimes forced to select EAGER and would benefit from resetting to LAZY in some cases. We have an entity User with a collection Roles (e.g. Admin, Editor etc). Some users have multiple roles. User is stored in the session and we frequently access the roles collection so we can't make it lazy. User is also an eager attribute for Order of which there are many, so we need pagination. However, when we select orders, the eager relation with Roles leads to an expansion of the result set. Each Order row get #roles times the number of rows. Very undesirable and not so easy to fix. The ability to set the Fetchprofile for orders to Lazy would be a solution here. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5238) On setting a String-Value for a integer entity-field in a criterion, produces a ClassCastException

by Hannes Havel (JIRA)

On setting a String-Value for a integer entity-field in a criterion, produces a ClassCastException -------------------------------------------------------------------------------------------------- Key: HHH-5238 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5238 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Reporter: Hannes Havel 12:06:40,864 INFO http-8080-2 IntegerType:158 - could not bind value '10' to parameter: 1; java.lang.String cannot be cast to java.lang.Integer 12:06:40,865 DEBUG http-8080-2 ServletServiceContainer:179 - core-exception in service-execution: null java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.daotec.remoting.server.ServiceMethod.invoke(ServiceMethod.java:85) at com.daotec.remoting.server.ServletServiceContainer.doPost(ServletServiceContainer.java:168) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer at org.hibernate.type.IntegerType.set(IntegerType.java:64) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:154) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:136) at org.hibernate.loader.Loader.bindPositionalParameters(Loader.java:1728) at org.hibernate.loader.Loader.bindParameterValues(Loader.java:1699) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1589) at org.hibernate.loader.Loader.doQuery(Loader.java:696) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306) at org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:328) at com.daotec.foundation.hibernate.GenericHibernateDAO.countAll(GenericHibernateDAO.java:147) at com.daotec.remoting.utils.CoreGenericDAOService.list(CoreGenericDAOService.java:108) ... 20 more -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-61) default_schema is not implemented in ShardConfiguration

by Hubert LUCHINI (JIRA)

default_schema is not implemented in ShardConfiguration ------------------------------------------------------- Key: HSHARDS-61 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-61 Project: Hibernate Shards Issue Type: Bug Components: configuration Affects Versions: 3.0.0.Beta2 Environment: hibernate shards. 2 databases DB2 and each database has its own default_schema Reporter: Hubert LUCHINI Assignee: Max Ross Priority: Minor Attachments: ConfigurationToShardConfigurationAdapter.java, ShardConfiguration.java, ShardedConfiguration.java propertie default_schema define in each shard hibernate.cfg.xml is not saved in ShardConfiguration -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5005) Column name not prefixed with table name alias

by Jeremy Hindmarsh (JIRA)

Column name not prefixed with table name alias ---------------------------------------------- Key: HHH-5005 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5005 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5 CR2, Oracle 10g Reporter: Jeremy Hindmarsh If a column name annotation contains a full stop, the column name is not prefixed with the table name alias. Some of our database tables contain Oracle spatial data. One in particular has two columns for longitude and latitude, GEOM.SDO_POINT.X and GEOM.SDO_POINT.Y The problem is that the table alias is not added to the column name due to isIdentifier method in the Template class. This method returns false because the column name contains full stops. This means the renderWhereStringTemplate method doesn't prefix the column name with the table alias placeholder. Fortunately for now I can use the following column definition, in order to get the table alias added. @Column(name = "$PlaceHolder$.GEOM.SDO_POINT.X") -- 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, 11 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5237) Version increment on joined subclass uses incorrect column names

by Ryan Reck (JIRA)

Version increment on joined subclass uses incorrect column names ---------------------------------------------------------------- Key: HHH-5237 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5237 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Reporter: Ryan Reck Attachments: hibernate-3.5.2.patch Forcing an update on a class mapped using table per subclass results in org.hibernate.exception.SQLGrammarException: could not retrieve version: [SubClass] ... -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1853) CREATE SCHEMA inside database-object need to execute before tables are created

by Robert Willian Gil (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853?page=c... ] Robert Willian Gil commented on HHH-1853: ----------------------------------------- this problem was solved? I'm having the same problem, I use spring to inject EntityManager. > CREATE SCHEMA inside database-object need to execute before tables are created > ------------------------------------------------------------------------------ > > Key: HHH-1853 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853 > Project: Hibernate Core > Issue Type: Improvement > Affects Versions: 3.1.3 > Environment: hsqldb 1.8.0 > Reporter: Mattias Jiderhamn > Priority: Minor > Attachments: create-schema.patch, create-schema2.patch > > > In order to have Hibernate create database schemas for hsqldb, you have to insert a <database-object> in your mapping file (http://forums.hibernate.org/viewtopic.php?p=2305138). Problem is, all the database-object statements are executed after the tables are created, so tables in non-default schemas will not be created. To get around this, you have to first use Configuration.generateSchemaCreationScript() to get the schemas, and then Configuration.generateSchemaUpdateScript() to get the tables inside the schemas. > (This is a bit problematic when using Springs LocalSessionFactoryBean) -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-16) Explicit joins on unrelated classes

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-16?page=com... ] Gail Badner commented on HHH-16: -------------------------------- Does that mean this was fixed by HHH-2308? > Explicit joins on unrelated classes > ----------------------------------- > > Key: HHH-16 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-16 > Project: Hibernate Core > Issue Type: New Feature > Components: core > Affects Versions: antlr-rework > Environment: Any > Reporter: David Lloyd > Assignee: Steve Ebersole > Fix For: antlr-rework > > > It would be nice to be able to do explicit joins on unrelated classes with HQL: > (hope this renders correctly) > select empl, phone > from org.example.Employee empl > left outer join org.example.PhoneBook phone > on phone.lastName = empl.lastName > and phone.firstName = empl.firstName > where empl.salaryGrade > 10 > Note that this would also implicity solve HB-1089 because you could list join criteria that match what Hibernate would have chosen anyway (i.e., list a many-to-one relationship as a criteria explicitly). > Syntactically this could be disambiguated from the existing join syntax because the token after "join" is a class name rather than a property name. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1134) subclass tag with discriminator in one to many mapping

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134?page=c... ] Gail Badner commented on HHH-1134: ---------------------------------- Could this be related to HHH-4953? > subclass tag with discriminator in one to many mapping > ------------------------------------------------------ > > Key: HHH-1134 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134 > Project: Hibernate Core > Issue Type: Bug > Components: core > Environment: hibernate 3.0.5, Oracle > Reporter: Dilip Ranjith > > Consider the following hbm.xml file > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping > > > <class > name="DCDTO" > table="ACCDC" > dynamic-update="true" > > > <id > name="ID" > type="java.lang.String" > > > <column > name="DCINFOID" > /> > <generator class="sequence"> > <param name="sequence">DSEQ</param> >  > </generator> > </id> > <discriminator > column="accountType" > not-null="true" > type="java.lang.String" > force="true" > insert="true" > /> > <property > name="creditMax" > type="java.lang.Double" > update="true" > insert="true" > column="creditMax" > /> > <subclass > name="CDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="C" > > > </.subclass> > <subclass > name="DDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="D" > > > </.subclass> > </class> > </hibernate-mapping> > DCDTO is the super class while DDTO and CDTO are its child classes > If in a mapped object say TDTO there are a set of CDTOs and a separate set of DDTOs > when we get TDTO the where clause "where accountType='D' " is not there when the query for set of DDTOs are generated. so instead of a set of DDTOs i am getting a set of both DDTO's and CDTO's -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4786) SerializableType + custom Serializable class + L2 cache causes problems

by Steve Ebersole (JIRA)

SerializableType + custom Serializable class + L2 cache causes problems ----------------------------------------------------------------------- Key: HHH-4786 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4786 Project: Hibernate Core Issue Type: Bug Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Beta-3 The changes done for HHH-2990 cause an issue when users map non-JDK Serializable classes using SerializableType in combination with attempting to cache those values into second level cache. SerializableType reports the classloader to use for deserialization as the classloader of java.io.Serializable (which is generally null indicating the "bootstrap class loader"). However that classloader will (generally) not have visibility into the classloader needed to see these non-JDK classes. -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1134) subclass tag with discriminator in one to many mapping

by HG (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134?page=c... ] HG commented on HHH-1134: ------------------------- Well force="true" will solve the issue, but not if you use second level cache. While fetching the entity from a cache hibernate does not care if the force is true or not, simply because of the fact that discriminator information is not present in the CacheKey used by hibernate. What can we do to have to have the same behaviour as "force='true'" with second level cache :( ??? > subclass tag with discriminator in one to many mapping > ------------------------------------------------------ > > Key: HHH-1134 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134 > Project: Hibernate Core > Issue Type: Bug > Components: core > Environment: hibernate 3.0.5, Oracle > Reporter: Dilip Ranjith > > Consider the following hbm.xml file > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping > > > <class > name="DCDTO" > table="ACCDC" > dynamic-update="true" > > > <id > name="ID" > type="java.lang.String" > > > <column > name="DCINFOID" > /> > <generator class="sequence"> > <param name="sequence">DSEQ</param> >  > </generator> > </id> > <discriminator > column="accountType" > not-null="true" > type="java.lang.String" > force="true" > insert="true" > /> > <property > name="creditMax" > type="java.lang.Double" > update="true" > insert="true" > column="creditMax" > /> > <subclass > name="CDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="C" > > > </.subclass> > <subclass > name="DDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="D" > > > </.subclass> > </class> > </hibernate-mapping> > DCDTO is the super class while DDTO and CDTO are its child classes > If in a mapped object say TDTO there are a set of CDTOs and a separate set of DDTOs > when we get TDTO the where clause "where accountType='D' " is not there when the query for set of DDTOs are generated. so instead of a set of DDTOs i am getting a set of both DDTO's and CDTO's -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-324) Default annotation not executing when group selector activated

by Marc Schipperheyn (JIRA)

Default annotation not executing when group selector activated -------------------------------------------------------------- Key: HV-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-324 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Beta1 Reporter: Marc Schipperheyn Assignee: Hardy Ferentschik Attachments: RegistrationVO.java When you call the validate function with a non-default group selector active, the default constraints do not execute. AFAIC this is unexpected behaviour. Default constraints by their very nature should always execute. Also, since it's very easy to exclude default execution by applying a non-default group selector. If this is in fact a design decision then the documentation should make very, *very* clear (e.g. through one of those "Notes": Default constraints do NOT execute when a group selector is active! If you want the default to be executed, also add Default.class to the set of group selectors you specify) that default constraints do not execute when a group constraint is active. It doesn't at the moment and I was caught by surprise. -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-820) TypeDef does not work when used on @Embeddable or @MappedSuperClass classes.

by Ted Bergeron (JIRA)

TypeDef does not work when used on @Embeddable or @MappedSuperClass classes. ---------------------------------------------------------------------------- Key: ANN-820 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-820 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Environment: Oracle 11, hibernate 3.4.0 GA Reporter: Ted Bergeron @TypeDefs({ @TypeDef( name = "status", typeClass = EnumUserType.class, parameters = {@Parameter(name = "enumClass", value = "com.acme.common.model.Status")} ) }) I declare various @TypeDefs such as this. They all work fine when used in @Entity classes. When used in a @MappedSuperclass, or an @Embeddable, they fail. I see from the docs that these are global and double checked that I do not have any duplicate @TypeDef definitions. -- 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, 11 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5232) Use intern() to reuse strings and reduce memory usage / save 6%

by Yves Galante (JIRA)

Use intern() to reuse strings and reduce memory usage / save 6% ---------------------------------------------------------------- Key: HHH-5232 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5232 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.6 Environment: Hibernate 3.6.0-SNAPSHOT Linux x86_64 Bits Reporter: Yves Galante Priority: Minor Attachments: DuplicateString.patch This patch is an update of JIRRA HHH-3924 for Hibernate 3.6. Testsuite executed without new failures. Resume of the original JIRRA HHH-3924 : >>DefaultEntityAliases suffix and rowIdAliases String fields are not interned as are other fields in the class. This leads to significant >>of memory usage on our application. >>BasicLoader suffixes and QueryLoader sqlAliasSuffixes can also be interned so as to save more memory See the detailed result of this patch : ======================================== Test conditions ======================================== Hibernate version : 3.6.0-SNAPSHOT Yourkit : 8.0 OS : Linux x86_64 Bits. Test case : org.hibernate.test.legacy.ParentChildTest.testReplicate() Time : Memory snapshot is taken at the of the test. ======================================== Result before patch ======================================== SessionFactoryImpl size : 3939 KB Duplicates String example : "0_" : 452 duplicates (32KB) "rowid_0_" : 405 duplicates (32KB) "1_" : 145 duplicates (10KB) "rowid_1_" : 130 duplicates (10KB) ... "fee3_" : 65 duplicates (5KB) "glarch1_" : 55 duplicates (5KB) ... "foo2_2_5" : 46 duplicates (3KB) ... "string" : 28 duplicates (2KB) ======================================== Result after patch ======================================== SessionFactoryImpl size : 3688 KB Save 251 Kb, 6% of the session factory size. -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-323) URL Validator needs to pass on empty Strings

by Marc Schipperheyn (JIRA)

URL Validator needs to pass on empty Strings -------------------------------------------- Key: HV-323 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-323 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 4.1.0.Beta1 Reporter: Marc Schipperheyn Assignee: Hardy Ferentschik Priority: Minor The URL Validator passed on null Strings. However, in some cases the engines we use somestimes treat an empty form input as "" leading to a not null empty String. These should also validate true. -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-4401) @Formula(value="")

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401?page=c... ] Emmanuel Bernard updated HHH-4401: ---------------------------------- Fix Version/s: (was: 3.3.x) > @Formula(value="") > ------------------ > > Key: HHH-4401 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Assignee: Emmanuel Bernard > Priority: Trivial > > Support formula -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-4401) @Formula(value="")

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401?page=c... ] Emmanuel Bernard commented on HHH-4401: --------------------------------------- No it's very likely not. First of it's an annotations version not a core version and second I think it's much older than Annotations 3.4 or 3.3 but I did not do the archeology. At any rate it's very old. > @Formula(value="") > ------------------ > > Key: HHH-4401 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Assignee: Emmanuel Bernard > Priority: Trivial > Fix For: 3.3.x > > > Support formula -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5226) Specify the error instead on general UnsupportedOperationException

by Rincy Rappai (JIRA)

Specify the error instead on general UnsupportedOperationException ------------------------------------------------------------------ Key: HHH-5226 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5226 Project: Hibernate Core Issue Type: New Feature Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, WebSphere 6.1.0.5, Windows XP, RAD 7.0.0.2, Oracle 10g Reporter: Rincy Rappai The API's in the class WebSphereExtendedJTATransactionLookup does not give a meaningful exception if there is an exception and the transaction fails. For any failure with the transaction the "UnsupportedOperationException" is thrown. There has been many links on this exception and a first look shows this as a bug with Hibernate. http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457 http://opensource.atlassian.com/projects/hibernate/browse/HHH-2124 http://opensource.atlassian.com/projects/hibernate/browse/HHH-3111 http://opensource.atlassian.com/projects/hibernate/browse/HHH-1287 Need resolution to identify the error and throw the related exception instead on general UnsupportedOperationException. -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-322) Establish a processor option "verbose"

by Gunnar Morling (JIRA)

Establish a processor option "verbose" -------------------------------------- Key: HV-322 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-322 Project: Hibernate Validator Issue Type: Improvement Components: annotation-processor Reporter: Gunnar Morling Assignee: Gunnar Morling Fix For: 4.1.0 Establish a processor option "verbose" that can be used to activate a verbose way of reporting of processing information, which is useful for debugging purposes. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-298) Add a section on using the annotation processor to the HV reference guide

by Gunnar Morling (JIRA)

Add a section on using the annotation processor to the HV reference guide ------------------------------------------------------------------------- Key: HV-298 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-298 Project: Hibernate Validator Issue Type: Improvement Components: documentation Affects Versions: 4.1.0-Beta-1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik A section describing the annotation processor should be added to the HV reference guide. It should cover the following: * Features of the AP * Options that control the AP's behavior * Integrating the AP into the build process: * Plain javac * Maven/Ant * IDE builds -- 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, 11 months

2
4
0 / 0

[Hibernate-JIRA] Commented: (HHH-16) Explicit joins on unrelated classes

by Douglas Ferguson (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-16?page=com... ] Douglas Ferguson commented on HHH-16: ------------------------------------- Looks like this is what I needed.. http://opensource.atlassian.com/projects/hibernate/browse/HHH-2308 > Explicit joins on unrelated classes > ----------------------------------- > > Key: HHH-16 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-16 > Project: Hibernate Core > Issue Type: New Feature > Components: core > Affects Versions: antlr-rework > Environment: Any > Reporter: David Lloyd > Assignee: Steve Ebersole > Fix For: antlr-rework > > > It would be nice to be able to do explicit joins on unrelated classes with HQL: > (hope this renders correctly) > select empl, phone > from org.example.Employee empl > left outer join org.example.PhoneBook phone > on phone.lastName = empl.lastName > and phone.firstName = empl.firstName > where empl.salaryGrade > 10 > Note that this would also implicity solve HB-1089 because you could list join criteria that match what Hibernate would have chosen anyway (i.e., list a many-to-one relationship as a criteria explicitly). > Syntactically this could be disambiguated from the existing join syntax because the token after "join" is a class name rather than a property name. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-4401) @Formula(value="")

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401?page=c... ] Gail Badner commented on HHH-4401: ---------------------------------- Emmanuel, is the fix version (3.3.x) correct? > @Formula(value="") > ------------------ > > Key: HHH-4401 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Assignee: Emmanuel Bernard > Priority: Trivial > Fix For: 3.3.x > > > Support formula -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5227) Stored Procedure invocation gets 'top 2' embedded by SQLServerDialect

by Eduard Martinescu (JIRA)

Stored Procedure invocation gets 'top 2' embedded by SQLServerDialect --------------------------------------------------------------------- Key: HHH-5227 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5227 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2, 3.3.1 Environment: Hibernate 3.3.2/3.3.1 connection to a SQL Server database Reporter: Eduard Martinescu I have an entity class, annotated with Named Native Queries that invoke stored procedures {code} @Entity @NamedNativeQuery(name = "NetworkServiceElementAlarm_GetById", resultClass=Alarm.class, query = "{call Grock.dbo.NetworkServiceElementAlarm_GetById(:alarmId)}", hints = {@QueryHint(name="org.hibernate.callable",value="true"), @QueryHint(name="org.hibernate.readOnly",value="true")}), public class Alarm implements java.io.Serializable { {code} I then later invoke that named query to retrieve a value from the database {code} return (Alarm) emGrock.createNamedQuery("NetworkServiceElementAlarm_GetById") .setParameter("alarmId", alarmId) .getSingleResult(); {code} However, this query fails with an error returned from the JDBC driver layer, indicating "{" is invalid. Upon further investigation, it turned out that the SQLServerDialect class is injecting "top 2" into the middle of the call, resulting in the following SQL {code} "{call Grock.dbotop 2.NetworkServiceElementAlarm_GetByID(?)}" {code} The problem is in the function 'getLimitString()' within the SQLServerDialect class. It blindly assumes that the incoming SQL has either "select" or "select distinct", and inserts "top " + the current limit count into the SQL string. I've worked around the problem temporarily by creating my own subclass of SQLServerDialect that overrides that method and looks for the presence of "{call", and if it finds it, returns the SQL string back unmodified (thereby not imposing a limit). I'm sure there is probably something better that can be done.... {code} public class SQLServerDialect extends org.hibernate.dialect.SQLServerDialect { @Override public String getLimitString (String querySelect, int offset, int limit) { if (querySelect.indexOf("{call") >= 0) return querySelect; else return super.getLimitString(querySelect, offset, limit); } } {code} -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-16) Explicit joins on unrelated classes

by Douglas Ferguson (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-16?page=com... ] Douglas Ferguson commented on HHH-16: ------------------------------------- Without a major refactor, I am stuck using the Criteria API. Can someone suggest a workaround or point me in the right direct as far as how to patch hibernate. I.E. Where does hibernate actually generate the html? I can't really think of another way of doing this in SQL, or is there a way to include HQL or SQL inside of Criteria? I've seen the sql projection, but this wouldn't work for creating the join... > Explicit joins on unrelated classes > ----------------------------------- > > Key: HHH-16 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-16 > Project: Hibernate Core > Issue Type: New Feature > Components: core > Affects Versions: antlr-rework > Environment: Any > Reporter: David Lloyd > Assignee: Steve Ebersole > Fix For: antlr-rework > > > It would be nice to be able to do explicit joins on unrelated classes with HQL: > (hope this renders correctly) > select empl, phone > from org.example.Employee empl > left outer join org.example.PhoneBook phone > on phone.lastName = empl.lastName > and phone.firstName = empl.firstName > where empl.salaryGrade > 10 > Note that this would also implicity solve HB-1089 because you could list join criteria that match what Hibernate would have chosen anyway (i.e., list a many-to-one relationship as a criteria explicitly). > Syntactically this could be disambiguated from the existing join syntax because the token after "join" is a class name rather than a property name. -- 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, 12 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-321) javax.persistence.PersistenceException when trying to validate an object graphs with a class-level constraint annotation. In addition to the error report HV-266

by Johnny (JIRA)

javax.persistence.PersistenceException when trying to validate an object graphs with a class-level constraint annotation. In addition to the error report HV-266 ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HV-321 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-321 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.1.0.Beta1 Environment: Hibernate 3.5.1-final, PostgreSQL, spring 3.0.2-release, hibernate-jpa-2.0-api-1.0.0.Final, validation-api-1.0.0.GA Reporter: Johnny Assignee: Hardy Ferentschik I use a class-level constraint annotation and object graphs. When I use the construction that you can see below I get the following error: "javax.persistence.PersistenceException: Unable to find field or method: class travel.just.flows.rzd.RzdPassengerInfo#passengersInfo": @MyCustomConstraint public class RzdTicket implements Serializable { @NotEmpty private String number; @Valid private RzdPassengerInfo rzdPassengersInfo; ... setters and getters } @MyCustomConstraint public class RzdPassengerInfo implements Serializable { @NotEmpty private String name; ... setters and getters } @Documented @Constraint(validatedBy = MyCustomConstraintValidator.class) @Target({ ElementType.TYPE }) @Retention(RetentionPolicy.RUNTIME) public @interface MyCustomConstraint { public abstract String message() default ""; public abstract Class<?>[] groups() default {}; java.lang.Class<? extends javax.validation.Payload>[] payload() default {}; } public class MyCustomConstraintValidator implements ConstraintValidator<MyCustomConstraint, Object> { public void initialize(Expression expression) { } public boolean isValid(Object target, ConstraintValidatorContext constraintValidatorContext) { return true; } } Please see below the stack trace of the error I get: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.webflow.execution.ActionExecutionException: Exception thrown executing [AnnotatedAction@26b38c81 targetAction = [RzdFormAction@15223b12 formObjectName = 'rzdTicket', formObjectClass = RzdTicket, formObjectScope = Flow], attributes = map['method' -> 'bindAndValidate']] in state 'rzdStep4PlacesPassengerInfo' of flow 'rzd' -- action execution attributes were 'map['validatorMethod' -> 'validateStep4']' org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:656) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:560) javax.servlet.http.HttpServlet.service(HttpServlet.java:637) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378) org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109) org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.SessionFixationProtectionFilter.doFilterHttp(SessionFixationProtectionFilter.java:67) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.providers.anonymous.AnonymousProcessingFilter.doFilterHttp(AnonymousProcessingFilter.java:105) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:278) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) travel.just.spring.security.ui.webapp.AuthenticationIpFilter.doFilterInternal(AuthenticationIpFilter.java:28) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:89) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:175) org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237) org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167) root cause org.springframework.webflow.execution.ActionExecutionException: Exception thrown executing [AnnotatedAction@26b38c81 targetAction = [RzdFormAction@15223b12 formObjectName = 'rzdTicket', formObjectClass = RzdTicket, formObjectScope = Flow], attributes = map['method' -> 'bindAndValidate']] in state 'rzdStep4PlacesPassengerInfo' of flow 'rzd' -- action execution attributes were 'map['validatorMethod' -> 'validateStep4']' org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:60) org.springframework.webflow.action.EvaluateAction.doExecute(EvaluateAction.java:79) org.springframework.webflow.action.AbstractAction.execute(AbstractAction.java:188) org.springframework.webflow.execution.AnnotatedAction.execute(AnnotatedAction.java:145) org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:51) org.springframework.webflow.engine.support.ActionTransitionCriteria.test(ActionTransitionCriteria.java:82) org.springframework.webflow.engine.support.TransitionCriteriaChain.test(TransitionCriteriaChain.java:71) org.springframework.webflow.engine.Transition.canExecute(Transition.java:195) org.springframework.webflow.engine.Transition.execute(Transition.java:211) org.springframework.webflow.engine.impl.FlowExecutionImpl.execute(FlowExecutionImpl.java:391) org.springframework.webflow.engine.impl.RequestControlContextImpl.execute(RequestControlContextImpl.java:214) org.springframework.webflow.engine.TransitionableState.handleEvent(TransitionableState.java:119) org.springframework.webflow.engine.Flow.handleEvent(Flow.java:555) org.springframework.webflow.engine.impl.FlowExecutionImpl.handleEvent(FlowExecutionImpl.java:386) org.springframework.webflow.engine.impl.RequestControlContextImpl.handleEvent(RequestControlContextImpl.java:210) org.springframework.webflow.engine.ViewState.handleEvent(ViewState.java:230) org.springframework.webflow.engine.ViewState.resume(ViewState.java:196) org.springframework.webflow.engine.Flow.resume(Flow.java:545) org.springframework.webflow.engine.impl.FlowExecutionImpl.resume(FlowExecutionImpl.java:259) org.springframework.webflow.executor.FlowExecutorImpl.resumeExecution(FlowExecutorImpl.java:163) org.springframework.webflow.mvc.servlet.FlowHandlerAdapter.handle(FlowHandlerAdapter.java:183) org.springframework.webflow.mvc.servlet.FlowController.handleRequest(FlowController.java:174) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:771) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:716) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:560) javax.servlet.http.HttpServlet.service(HttpServlet.java:637) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378) org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109) org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.SessionFixationProtectionFilter.doFilterHttp(SessionFixationProtectionFilter.java:67) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.providers.anonymous.AnonymousProcessingFilter.doFilterHttp(AnonymousProcessingFilter.java:105) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:278) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) travel.just.spring.security.ui.webapp.AuthenticationIpFilter.doFilterInternal(AuthenticationIpFilter.java:28) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:89) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:175) org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237) org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167) root cause javax.validation.ValidationException: Call to TraversableResolver.isReachable() threw an exception org.hibernate.validator.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:773) org.hibernate.validator.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:331) org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForNonDefaultGroup(ValidatorImpl.java:312) org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:248) org.hibernate.validator.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:213) org.hibernate.validator.engine.ValidatorImpl.validateCascadedConstraint(ValidatorImpl.java:466) org.hibernate.validator.engine.ValidatorImpl.validateCascadedConstraints(ValidatorImpl.java:372) org.hibernate.validator.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:219) org.hibernate.validator.engine.ValidatorImpl.validate(ValidatorImpl.java:119) travel.just.spring.validation.BeanValidator.validate(BeanValidator.java:30) travel.just.flows.rzd.RzdFormValidator.validateStep4(RzdFormValidator.java:49) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.springframework.webflow.action.DispatchMethodInvoker.invoke(DispatchMethodInvoker.java:98) org.springframework.webflow.action.FormAction.invokeValidatorMethod(FormAction.java:719) org.springframework.webflow.action.FormAction.doValidate(FormAction.java:834) org.springframework.webflow.action.FormAction.bindAndValidate(FormAction.java:491) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.springframework.webflow.action.DispatchMethodInvoker.invoke(DispatchMethodInvoker.java:98) org.springframework.webflow.action.MultiAction.doExecute(MultiAction.java:123) org.springframework.webflow.action.AbstractAction.execute(AbstractAction.java:188) org.springframework.webflow.execution.AnnotatedAction.execute(AnnotatedAction.java:145) org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:51) org.springframework.webflow.action.EvaluateAction.doExecute(EvaluateAction.java:79) org.springframework.webflow.action.AbstractAction.execute(AbstractAction.java:188) org.springframework.webflow.execution.AnnotatedAction.execute(AnnotatedAction.java:145) org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:51) org.springframework.webflow.engine.support.ActionTransitionCriteria.test(ActionTransitionCriteria.java:82) org.springframework.webflow.engine.support.TransitionCriteriaChain.test(TransitionCriteriaChain.java:71) org.springframework.webflow.engine.Transition.canExecute(Transition.java:195) org.springframework.webflow.engine.Transition.execute(Transition.java:211) org.springframework.webflow.engine.impl.FlowExecutionImpl.execute(FlowExecutionImpl.java:391) org.springframework.webflow.engine.impl.RequestControlContextImpl.execute(RequestControlContextImpl.java:214) org.springframework.webflow.engine.TransitionableState.handleEvent(TransitionableState.java:119) org.springframework.webflow.engine.Flow.handleEvent(Flow.java:555) org.springframework.webflow.engine.impl.FlowExecutionImpl.handleEvent(FlowExecutionImpl.java:386) org.springframework.webflow.engine.impl.RequestControlContextImpl.handleEvent(RequestControlContextImpl.java:210) org.springframework.webflow.engine.ViewState.handleEvent(ViewState.java:230) org.springframework.webflow.engine.ViewState.resume(ViewState.java:196) org.springframework.webflow.engine.Flow.resume(Flow.java:545) org.springframework.webflow.engine.impl.FlowExecutionImpl.resume(FlowExecutionImpl.java:259) org.springframework.webflow.executor.FlowExecutorImpl.resumeExecution(FlowExecutorImpl.java:163) org.springframework.webflow.mvc.servlet.FlowHandlerAdapter.handle(FlowHandlerAdapter.java:183) org.springframework.webflow.mvc.servlet.FlowController.handleRequest(FlowController.java:174) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:771) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:716) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:560) javax.servlet.http.HttpServlet.service(HttpServlet.java:637) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378) org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109) org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.SessionFixationProtectionFilter.doFilterHttp(SessionFixationProtectionFilter.java:67) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.providers.anonymous.AnonymousProcessingFilter.doFilterHttp(AnonymousProcessingFilter.java:105) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:278) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) travel.just.spring.security.ui.webapp.AuthenticationIpFilter.doFilterInternal(AuthenticationIpFilter.java:28) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:89) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:175) org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237) org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167) root cause javax.persistence.PersistenceException: Unable to find field or method: class travel.just.flows.rzd.RzdPassengerInfo#passengersInfo org.hibernate.ejb.util.PersistenceUtilHelper.get(PersistenceUtilHelper.java:95) org.hibernate.ejb.util.PersistenceUtilHelper.isLoadedWithReference(PersistenceUtilHelper.java:76) org.hibernate.ejb.HibernatePersistence$1.isLoadedWithReference(HibernatePersistence.java:92) javax.persistence.Persistence$1.isLoaded(Persistence.java:83) org.hibernate.validator.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.java:33) org.hibernate.validator.engine.resolver.DefaultTraversableResolver.isReachable(DefaultTraversableResolver.java:112) org.hibernate.validator.engine.resolver.SingleThreadCachedTraversableResolver.isReachable(SingleThreadCachedTraversableResolver.java:47) org.hibernate.validator.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:764) org.hibernate.validator.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:331) org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForNonDefaultGroup(ValidatorImpl.java:312) org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:248) org.hibernate.validator.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:213) org.hibernate.validator.engine.ValidatorImpl.validateCascadedConstraint(ValidatorImpl.java:466) org.hibernate.validator.engine.ValidatorImpl.validateCascadedConstraints(ValidatorImpl.java:372) org.hibernate.validator.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:219) org.hibernate.validator.engine.ValidatorImpl.validate(ValidatorImpl.java:119) travel.just.spring.validation.BeanValidator.validate(BeanValidator.java:30) travel.just.flows.rzd.RzdFormValidator.validateStep4(RzdFormValidator.java:49) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.springframework.webflow.action.DispatchMethodInvoker.invoke(DispatchMethodInvoker.java:98) org.springframework.webflow.action.FormAction.invokeValidatorMethod(FormAction.java:719) org.springframework.webflow.action.FormAction.doValidate(FormAction.java:834) org.springframework.webflow.action.FormAction.bindAndValidate(FormAction.java:491) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.springframework.webflow.action.DispatchMethodInvoker.invoke(DispatchMethodInvoker.java:98) org.springframework.webflow.action.MultiAction.doExecute(MultiAction.java:123) org.springframework.webflow.action.AbstractAction.execute(AbstractAction.java:188) org.springframework.webflow.execution.AnnotatedAction.execute(AnnotatedAction.java:145) org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:51) org.springframework.webflow.action.EvaluateAction.doExecute(EvaluateAction.java:79) org.springframework.webflow.action.AbstractAction.execute(AbstractAction.java:188) org.springframework.webflow.execution.AnnotatedAction.execute(AnnotatedAction.java:145) org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:51) org.springframework.webflow.engine.support.ActionTransitionCriteria.test(ActionTransitionCriteria.java:82) org.springframework.webflow.engine.support.TransitionCriteriaChain.test(TransitionCriteriaChain.java:71) org.springframework.webflow.engine.Transition.canExecute(Transition.java:195) org.springframework.webflow.engine.Transition.execute(Transition.java:211) org.springframework.webflow.engine.impl.FlowExecutionImpl.execute(FlowExecutionImpl.java:391) org.springframework.webflow.engine.impl.RequestControlContextImpl.execute(RequestControlContextImpl.java:214) org.springframework.webflow.engine.TransitionableState.handleEvent(TransitionableState.java:119) org.springframework.webflow.engine.Flow.handleEvent(Flow.java:555) org.springframework.webflow.engine.impl.FlowExecutionImpl.handleEvent(FlowExecutionImpl.java:386) org.springframework.webflow.engine.impl.RequestControlContextImpl.handleEvent(RequestControlContextImpl.java:210) org.springframework.webflow.engine.ViewState.handleEvent(ViewState.java:230) org.springframework.webflow.engine.ViewState.resume(ViewState.java:196) org.springframework.webflow.engine.Flow.resume(Flow.java:545) org.springframework.webflow.engine.impl.FlowExecutionImpl.resume(FlowExecutionImpl.java:259) org.springframework.webflow.executor.FlowExecutorImpl.resumeExecution(FlowExecutorImpl.java:163) org.springframework.webflow.mvc.servlet.FlowHandlerAdapter.handle(FlowHandlerAdapter.java:183) org.springframework.webflow.mvc.servlet.FlowController.handleRequest(FlowController.java:174) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:771) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:716) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:560) javax.servlet.http.HttpServlet.service(HttpServlet.java:637) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378) org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109) org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.SessionFixationProtectionFilter.doFilterHttp(SessionFixationProtectionFilter.java:67) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.providers.anonymous.AnonymousProcessingFilter.doFilterHttp(AnonymousProcessingFilter.java:105) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:278) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) travel.just.spring.security.ui.webapp.AuthenticationIpFilter.doFilterInternal(AuthenticationIpFilter.java:28) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:89) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390) org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:175) org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237) org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167) -- 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, 12 months

2
3
0 / 0

[Hibernate-JIRA] Resolved: (HHH-4401) @Formula(value="")

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401?page=c... ] Emmanuel Bernard resolved HHH-4401. ----------------------------------- Resolution: Fixed Fix Version/s: 3.3.x > @Formula(value="") > ------------------ > > Key: HHH-4401 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Assignee: Emmanuel Bernard > Priority: Trivial > Fix For: 3.3.x > > > Support formula -- 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, 12 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-168) Add the ability to disable automatic indexing both on a per index level and programmatically

by Eric Winter (JIRA)

Add the ability to disable automatic indexing both on a per index level and programmatically -------------------------------------------------------------------------------------------- Key: HSEARCH-168 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-168 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Eric Winter Priority: Minor It is very resticitive in an application that has multiple indexes to only allow the disabling of automatic indexing on an application wide level (or at least SessionFactory wide...). I can see it being very useful to have auto indexing on a per index basis. Also, it would be nice to be able to turn auto indexing off and on programmatically using something like Search.setAutoIndexing("myIndex", false); //per index and Search.setAutoIndexing(false); //global -- 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, 12 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-525) Application hangs, main thread returns but some other thread spawned keeps application from ending

by ddbattlefield2142 (JIRA)

Application hangs, main thread returns but some other thread spawned keeps application from ending -------------------------------------------------------------------------------------------------- Key: HSEARCH-525 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-525 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.CR1, 3.1.1.GA Environment: Ubuntu 9.10, java version "1.6.0_0" OpenJDK Runtime Environment (IcedTea6 1.6.1) (6b16-1.6.1-3ubuntu3) OpenJDK Server VM (build 14.0-b16, mixed mode), mysql Ver 14.14 Distrib 5.1.37, for debian-linux-gnu (i486) using EditLine wrapper Reporter: ddbattlefield2142 Attachments: HibernateSearchBugReport.tgz Write a class with one main method. Call a method which loads one entity (preexisting data) and tries to index it. The code runs fine and the main thread returns but the application hangs. Some thread spawned by hibernate is keeping the application from exiting. You would need to press control + C to exit the application. Please refer to README in the attachment for a list of dependencies I am using and the running instructions. -- 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, 12 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5221) Support orphanRemoval on @OneToOne in @Embedded

by Anders Wallgren (JIRA)

Support orphanRemoval on @OneToOne in @Embedded ----------------------------------------------- Key: HHH-5221 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5221 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.0-Final Reporter: Anders Wallgren Comment from {{Cascade.cascadeProperty}}: {code} // association defined on component // todo : this is currently unsupported because of the fact that // we do not know the loaded state of this value properly // and doing so would be very difficult given how components and // entities are loaded (and how 'loaded state' is put into the // EntityEntry). Solutions here are to either: // 1) properly account for components as a 2-phase load construct // 2) just assume the association was just now orphaned and // issue the orphan delete. This would require a special // set of SQL statements though since we do not know the // orphaned value, something a delete with a subquery to // match the owner. {code} -- 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, 12 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1480) JOIN precendence rules per SQL-99

by Mark Derricutt (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1480?page=c... ] Mark Derricutt commented on HHH-1480: ------------------------------------- Under PostgreSQL this change causes many problems for us. We were tracking the milestone releases and found that between M1 and M2+ a lot of queries blowing out the server and running for 14+ days before they were noticed. Has anyone on the Hibernate team seem this under PostgreSQL ( 8.3/8.4 ) - we're using the org.hibernate.dialect.PostgreSQLDialect dialect. > JOIN precendence rules per SQL-99 > --------------------------------- > > Key: HHH-1480 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1480 > Project: Hibernate Core > Issue Type: New Feature > Components: query-hql > Affects Versions: 3.1.2 > Reporter: trebor iksrazal > Assignee: Steve Ebersole > Fix For: 3.5.0-Beta-2 > > > In SQL-92 joins performed in the where clause (comma operator in from clause) and joins performed in the from clause (join keyword) had the same precedence. SQL-99 clarified this such that the from clause joins had higher precedence. > Hibernate currently treats these as having the same precedence. > A good explanation comes from the MySQL docs ( http://dev.mysql.com/doc/refman/5.0/en/join.html ) : > # > Previously, the comma operator (,) and JOIN both had the same precedence, so the join expression t1, t2 JOIN t3 was interpreted as ((t1, t2) JOIN t3). Now JOIN has higher precedence, so the expression is interpreted as (t1, (t2 JOIN t3)). This change affects statements that use an ON clause, because that clause can refer only to columns in the operands of the join, and the change in precedence changes interpretation of what those operands are. > Example: > CREATE TABLE t1 (i1 INT, j1 INT); > CREATE TABLE t2 (i2 INT, j2 INT); > CREATE TABLE t3 (i3 INT, j3 INT); > INSERT INTO t1 VALUES(1,1); > INSERT INTO t2 VALUES(1,1); > INSERT INTO t3 VALUES(1,1); > SELECT * FROM t1, t2 JOIN t3 ON (t1.i1 = t3.i3); > Previously, the SELECT was legal due to the implicit grouping of t1,t2 as (t1,t2). Now the JOIN takes precedence, so the operands for the ON clause are t2 and t3. Because t1.i1 is not a column in either of the operands, the result is an Unknown column 't1.i1' in 'on clause' error. To allow the join to be processed, group the first two tables explicitly with parentheses so that the operands for the ON clause are (t1,t2) and t3: > SELECT * FROM (t1, t2) JOIN t3 ON (t1.i1 = t3.i3); > Alternatively, avoid the use of the comma operator and use JOIN instead: > SELECT * FROM t1 JOIN t2 JOIN t3 ON (t1.i1 = t3.i3); > This change also applies to statements that mix the comma operator with INNER JOIN, CROSS JOIN, LEFT JOIN, and RIGHT JOIN, all of which now have higher precedence than the comma operator. -- 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, 12 months

1
0
0 / 0

[Hibernate-JIRA] Assigned: (HHH-4401) @Formula(value="")

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401?page=c... ] Steve Ebersole reassigned HHH-4401: ----------------------------------- Assignee: Emmanuel Bernard Emmanuel, this is done already no? > @Formula(value="") > ------------------ > > Key: HHH-4401 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Assignee: Emmanuel Bernard > Priority: Trivial > > Support formula -- 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, 12 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-846) Infinite loop occurs while doing findById on a Parent domain Object having OneToMany relationship with child domain with composite primary key

by RAMESH BABU NL (JIRA)

Infinite loop occurs while doing findById on a Parent domain Object having OneToMany relationship with child domain with composite primary key ---------------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-846 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-846 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.4.0.GA Environment: Hibernate Annotations 3.4.0.GA, HSqlDB and Oracle Reporter: RAMESH BABU NL Attachments: Organization.java, OrganizationApplications.java, OrganizationApplicationsPK.java We are using Hibernate annotations version 3.4.0.G.A We are establishing a OneToMany relationship using the annotation @OnetoMany for a Parent and Child domain objects where the child domain has a composite primary key. We have two domain objects Organization [Parent] OrganizationApplications [Child] We want to have a OnetoMany relationship between Organization and OrganizationApplications. As shown below OrganizationApplications contains a composite primary key, of two columns(Organization Id, ApplicationId[foreignkey from other table called APPLICATIONS]) Organizations.java ------------------- @OneToMany(targetEntity=gov.osc.enrollment.backend.domain.OrganizationApplications.class, cascade=CascadeType.ALL, fetch = FetchType.EAGER, mappedBy="id.organization") private Set<OrganizationApplications> organizationApps = new HashSet<OrganizationApplications>(); OrganizationApplications.java --------------------------------------------------------------------- public class OrganizationApplications extends EnvelopeInfo implements Serializable { private static final long serialVersionUID = 1L; @EmbeddedId private OrganizationApplicationsPK id; public OrganizationApplicationsPK getId() { return id; } public void setId(OrganizationApplicationsPK id) { this.id = id; } OrganizationApplicationsPK.java --------------------------------------------------------------------- @Embeddable public class OrganizationApplicationsPK implements Serializable { private static final Long serialVersionUID = 1L; public OrganizationApplicationsPK() { super(); } @ManyToOne @JoinColumn(name="APPLICATION_ID",nullable=false) private Applications application; @ManyToOne(targetEntity=gov.osc.enrollment.backend.domain.Organization.class, cascade=CascadeType.ALL) @JoinColumn(name="ORGANIZATION_ID", referencedColumnName="ORGANIZATION_ID", nullable=false, insertable=true, updatable=true) private Organization organization; public Applications getApplication() { return application; } public void setApplication(Applications application) { this.application = application; } public Organization getOrganization() { return organization; } public void setOrganization(Organization organization) { this.organization = organization; } @Override public boolean equals(Object o) { if (o == this) { return true; } if ( ! (o instanceof OrganizationApplicationsPK)) { return false; } OrganizationApplicationsPK other = (OrganizationApplicationsPK) o; return (this.getOrganization().getId() == other.getOrganization().getId()) && (this.getApplication().getId() == other.getApplication().getId()); } @Override public int hashCode() { final int prime = 31; int hash = 17; hash = hash * prime + ((int) (this.getOrganization().getId() ^ (this.getOrganization().getId() >>> 32))); hash = hash * prime + ((int) (this.getApplication().getId() ^ (this.getApplication().getId() >>> 32))); return hash; } } Please see the attached java files for complete code and also the exception stack trace. Questions: 1. When we do a findById query on Organization table the system goes into infinite loop and never gets out . How ever we are able to insert a record in Organization and its child OrganizationApplications. 2. In the Organization.java domain, if you notice we are using mappedby="id.organization". Is this a valid mapping ? If not why does this parameter work for insert and not for a entityManager.findById, doing so leads to infinite loop. -- 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, 12 months

2
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-1907) offload metadata information from ComponentType to SessionFactory

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907?page=c... ] Steve Ebersole updated HHH-1907: -------------------------------- Description: Specifically, we need to move all the code directly dealing with property-access, instantiation, etc out of here. So where do we move it? Well, EntityType for example moves this stuff off to the persisters; the type then just looks up the persister when needed. Not sure we actually need a persister per-se for handling components; perhaps just ComponentMetamodel is enough... Why is this important? Well the way ComponentType is currently structured leads to the need for certain configuration properties to be classloader scoped (static on Environment) instead of SessionFactory scoped. This is painful for two in particular: 1) whether to use reflection optimization and 2) bytecode provider. Also, this change should allow us to cleanup how property accessors are built Long term it would facilitate the ability to have hierarchies of components as well as loading components in a 2-phase-load paradigm like entities and collections. was: Specifically, we need to move all the code directly dealing with property-access, instantiation, etc out of here. So where do we move it? Well, EntityType for example moves this stuff off to the persisters; the type then just looks up the persister when needed. Not sure we actually need a persister per-se for handling components; perhaps just ComponentMetamodel is enough... Why is this important? Well the way ComponentType is currently structured leads to the need for certain configuration properties to be classloader scoped (static on Environment) instead of SessionFactory scoped. This is painful for two in particular: 1) whether to use reflection optimization and 2) bytecode provider. Also, this change should allow us to cleanup how property accessors are built > offload metadata information from ComponentType to SessionFactory > ----------------------------------------------------------------- > > Key: HHH-1907 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: cfg-rework > > > Specifically, we need to move all the code directly dealing with property-access, instantiation, etc out of here. So where do we move it? Well, EntityType for example moves this stuff off to the persisters; the type then just looks up the persister when needed. Not sure we actually need a persister per-se for handling components; perhaps just ComponentMetamodel is enough... > Why is this important? Well the way ComponentType is currently structured leads to the need for certain configuration properties to be classloader scoped (static on Environment) instead of SessionFactory scoped. This is painful for two in particular: 1) whether to use reflection optimization and 2) bytecode provider. > Also, this change should allow us to cleanup how property accessors are built > Long term it would facilitate the ability to have hierarchies of components as well as loading components in a 2-phase-load paradigm like entities and collections. -- 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, 12 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5135) Prefix is missed in HQL query for property mapped to column 'TO_DATE' on Oracle 10g

by Vladimir Ivanov (JIRA)

Prefix is missed in HQL query for property mapped to column 'TO_DATE' on Oracle 10g ----------------------------------------------------------------------------------- Key: HHH-5135 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5135 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.0-Final Environment: Hibernate 3.5.1, Oracle 10.2.0.1.0 Reporter: Vladimir Ivanov Attachments: test_case.zip I have entity 'Period' with property 'toDate' mapped to database column with name 'TO_DATE' (Our database is Oracle 10g). When this entity is queried via HQL, prefix for this entity is missed. Following SQL query is produced: Hibernate: /* from Period p */ select * from ( select period0_.ID as ID44_, period0_.TXN_VER as TXN3_44_, period0_.FROM_DATE as FROM4_44_, TO_DATE as TO5_44_, period0_.POSITION_MONTH as POSITION7_44_, period0_.IS_CLOSE as IS12_44_, period0_.IS_OPEN as IS13_44_, period0_.DISC_TYPE as DISC2_44_ from SOME_SCHEMA.T_PERIOD period0_ ) where rownum <= ? This leads to database error in case of more advanced query (with joins etc). For example, we have following error in production: java.sql.SQLException: ORA-00918: column ambiguously defined Probably the reason of this behaviour is that Hibernate tries to interpret 'TO_DATE' as the name of SQL function. In Hibernate 3.3.2.GA prefix is added correctly. Domain object, DAO, Test and Hibernate configuration are in the attachment. I used Spring framework to configure test. -- 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, 12 months

5
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5063) Projections that have aliases same as the property name result in invalid sql

by Shawn Clowater (JIRA)

Projections that have aliases same as the property name result in invalid sql ----------------------------------------------------------------------------- Key: HHH-5063 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.0-Final Reporter: Shawn Clowater I have a criteria query that is using an AliasToBeanTransformer that I'm using to selectively populate some of the properties. It appears that the transformer requires the alias values to match the properties of your bean so that it can call the setters via reflection. The code snippet is similar to the following return (List<DataProvider>) session.createCriteria(DataProvider.class) .setProjection(Projections.projectionList() .add(Projections.property("dataProviderId), "dataProviderId") .add(Projections.property("uuid"), "uuid") .add(Projections.property("name"), "name") .add(Projections.property("dataProviderGroup"), "dataProviderGroup") .add(Projections.property("verifiedFlg"), "verifiedFlg") ) .setResultTransformer(new AliasToBeanResultTransformer(DataProvider.class)) .addOrder(Order.asc("name")) .list(); And is resulting in the following SQL select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER this_ order by y2_ asc I can assure you that my column names are not y0_, etc. This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If I don't specify the alias or even change the value then it will produce a valid query it just won't populate by bean correctly. i.e. if I append anything to the end of the first alias (i.e. "hi") results in: select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER this_ order by y2_ asc -- 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, 12 months

4
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5219) DATETIME column incorrectly validates against DATE column

by Ian Haken (JIRA)

DATETIME column incorrectly validates against DATE column --------------------------------------------------------- Key: HHH-5219 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5219 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.1 Reporter: Ian Haken Attachments: validation-fix.patch org.hibernate.mapping.Table.validateColumns incorrectly validates if the expected SqlType is DATETIME and the actual SqlType is DATE. This can be reproduced as follows: Create a MySQL table with DATE type for column foo. Create an Entity with java.util.Date member foo, annotated with @Temporal(TemporalType.TIMESTAMP). Initiate a Hibernate session with hibernate.hbm2ddl.auto=validate. An exception should be thrown and is not. Looking at the code in src/main/java/org/hibernate/mapping/Table.java, it is clear why this would occur; the check is: col.getSqlType( dialect, mapping ).toLowerCase().startsWith( columnInfo.getTypeName().toLowerCase() ) I'm not sure if there was a particular reason for using startsWith rather than equals, but I've changed startsWith to equals in the suggested patch (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

15 years, 12 months

2
2
0 / 0

[Hibernate-JIRA] Created: (METAGEN-26) Update readme.txt

by Hardy Ferentschik (JIRA)

Update readme.txt ----------------- Key: METAGEN-26 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-26 Project: Hibernate StaticMetamodel Generator Issue Type: Task Components: documentation Affects Versions: 1.0.0-CR-1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.0.0 -- 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, 12 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-526) Mass Indexer Logs Multiple NullPointerExceptions

by j nadler (JIRA)

Mass Indexer Logs Multiple NullPointerExceptions ------------------------------------------------ Key: HSEARCH-526 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-526 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.Final Environment: Hibernate Core 3.5.1, Hibernate Search 3.2.0.Final Reporter: j nadler We just moved our 'old style' reindex code to the new MassIndexer and gave it a run. It seems to have mostly worked (the index was clearly populated with some records) but a few NPEs in the logs: [2010-05-06 08:22:25.115,105054]ERROR[Hibernate Search: collectionsloader-4](EntityConsumerLuceneworkProducer.java:96) - error during batch indexing: java.lang.NullPointerException at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.index(EntityConsumerLuceneworkProducer.java:139) at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.indexAllQueue(EntityConsumerLuceneworkProducer.java:117) at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.run(EntityConsumerLuceneworkProducer.java:92) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) [2010-05-06 08:22:37.170,117109]ERROR[Hibernate Search: collectionsloader-1](EntityConsumerLuceneworkProducer.java:96) - error during batch indexing: java.lang.NullPointerException at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.index(EntityConsumerLuceneworkProducer.java:139) at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.indexAllQueue(EntityConsumerLuceneworkProducer.java:117) at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.run(EntityConsumerLuceneworkProducer.java:92) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) [2010-05-06 08:22:37.466,117405]ERROR[Hibernate Search: collectionsloader-2](EntityConsumerLuceneworkProducer.java:96) - error during batch indexing: java.lang.NullPointerException at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.index(EntityConsumerLuceneworkProducer.java:139) at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.indexAllQueue(EntityConsumerLuceneworkProducer.java:117) at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.run(EntityConsumerLuceneworkProducer.java:92) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) [2010-05-06 08:22:37.566,117505]ERROR[Hibernate Search: collectionsloader-8](EntityConsumerLuceneworkProducer.java:96) - error during batch indexing: java.lang.NullPointerException at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.index(EntityConsumerLuceneworkProducer.java:139) at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.indexAllQueue(EntityConsumerLuceneworkProducer.java:117) at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.run(EntityConsumerLuceneworkProducer.java:92) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) [2010-05-06 08:22:51.710,131649]WARN [http-8080-7](StatefulPersistenceContext.java:662) - Narrowing proxy to class com.attensa.core.entity.User - this operation breaks == [2010-05-06 08:22:51.738,131677]DEBUG[http-8080-7](BaseArticleListQuery.java:579) - getLatestDateModified: took: 0:00:00.024 -- 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, 12 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3884) NPE with mutable Natuarl Id's

by Michael Kopp (JIRA)

NPE with mutable Natuarl Id's ----------------------------- Key: HHH-3884 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3884 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.2 Reporter: Michael Kopp When saving an entity with a mutable natural id hibernate throws the following NPE. java.lang.NullPointerException at org.hibernate.engine.StatefulPersistenceContext.getNaturalIdSnapshot(StatefulPersistenceContext.java:267) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkNaturalId(DefaultFlushEntityEventListener.java:78) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:162) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:113) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) I checked the code and found the reason: - getNaturalIdSnapshot calls getDatabaseSnapshot and checks the result for NO_ROW but not for null - getDatabaseSnapshot will never return NO_ROW but null if nothing was found hence getNaturalIdSnapshot will produce a NPE if the entity is not in the database already. the fix is simple: change: Object[] entitySnapshot = getDatabaseSnapshot( id, persister ); if ( entitySnapshot == NO_ROW ) { return null; } to Object[] entitySnapshot = getDatabaseSnapshot( id, persister ); if ( entitySnapshot == null ) { return null; } This is still there in trunk as well! -- 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, 12 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5216) Fieled is only set null

by Nima Rad (JIRA)

Fieled is only set null ------------------------ Key: HHH-5216 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5216 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.1 Reporter: Nima Rad Attachments: FetchProfile.java.patch A possible null pointer situation and unused fields removal patch. relating to org.hibernate.engine.profile.Fetchprofile -- 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, 12 months

1
1
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1574) AbstractEntityPersister.getNaturalIdentifierSnapshot doesn't work with many-to-one ids (Alex Burgel)

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1574?page=c... ] Gail Badner resolved HHH-1574. ------------------------------ Resolution: Fixed Fixed in trunk and Branch_3_5. Alex, thanks for the fix and the test case! There may be a similar issue with immutable natural IDs containing a component. If someone runs into that, please open a new issue. > AbstractEntityPersister.getNaturalIdentifierSnapshot doesn't work with many-to-one ids (Alex Burgel) > ---------------------------------------------------------------------------------------------------- > > Key: HHH-1574 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1574 > Project: Hibernate Core > Issue Type: Patch > Affects Versions: 3.1.2 > Reporter: Alex Burgel > Assignee: Gail Badner > Fix For: 3.5.2, 3.6 > > Attachments: resolveentity.patch, resolveentity32.patch, testcase.zip > > > i just upgraded from 3.0.5 to 3.1.2, and i started seeing this problem. i'm not exactly sure where the bug is here, but this is what i'm seeing: > i have a class, Subscription, which has a natural-id of class Subscriber and Edition (excerpts of relevant mapping files below). > when Subscription is unloaded, if i make a change, then commit the session, i see this exception: > HibernateException: immutable natural identifier of an instance of Subscription was altered > this gets thrown from DefaultFlushEntityEventListener.checkNaturalId() line 80. > i traced through that method, this is what happens: > 1. in checkNaturalId, loaded == null , so getNaturalIdSnapshot() is called > 2. this ends up generating some sql that selects the SubscriptionId and EditionId from the Subscription row. > 3. the sql is generated in AbstractEntityPersister.getNaturalIdentifierSnapshot(), which calls hydrate for each returned column of the natural-id, > 4. but hydrate only returns the id, instead of the actual entity > 5. so this array of ids (instead of entities) ends up back in DefaultFlushEntityEventListener.checkNaturalId() as 'loaded', which gets compared to 'current' > the trouble is that 'current' contains the entities, but 'loaded' only contains the ids of those entites, so the natural-id check fails, and i get the exception. > this only happens when 'loaded' is null in checkNaturalId(). > the javadocs for hydrate say you have to call "resolve" afterwards... this isn't being done, so maybe thats the fix. if the natural-id is not just simple properties, then resolve should also be called. > <class name="Subscription" table="Subscriptions" batch-size="10"> > <id name="id" column="Id" type="int"><generator class="native" /></id> > <natural-id> > <many-to-one name="subscriber" class="Subscriber" column="SubscriberId" /> > <many-to-one name="edition" class="Edition" column="EditionId" /> > </natural-id> > .... > </class> > <class name="Subscriber" table="Subscriber"> > <id name="id" column="id" type="int"><generator class="native" /></id> > <map name="subscriptions" inverse="true" cascade="all,delete-orphan" batch-size="10"> > <key column="SubscriberId" /> > <map-key-many-to-many column="EditionId" class="Edition" /> > <one-to-many class="Subscription" /> > </map> > </class> -- 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, 12 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4971) Findbugs Warnings

by Marco Tulio Valente (JIRA)

Findbugs Warnings ----------------- Key: HHH-4971 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4971 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Reporter: Marco Tulio Valente Priority: Minor Dear all, We are conducting a study about the relevance of the warnings reported by the FindBugs tool when executed over several open-source systems. Particularly, in the case of Hibernate, we would like to confirm the relevance of the following warning reported by the tool (for version 3.5.0.beta1): Location: org.hibernate.engine.StatefulPersistenceContext getNaturalIdSnapshot - Line: 298 Warning: Using pointer equality to compare different types. The method uses using pointer equality to compare two references that seem to be of different types. The result of this comparison will always be false at runtime. Since this warning seemed relevant to us, we would like to confirm our classification with Hibernate's developers. Best regards, Marco Tulio Valente Brazil -- 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, 12 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3068) Update of an entity with immutable natural-id and many-to-one relation seems to fail

by Pascal Cohen (JIRA)

Update of an entity with immutable natural-id and many-to-one relation seems to fail ------------------------------------------------------------------------------------ Key: HHH-3068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3068 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Linux Fedora 32bits Postgres 8.2.5 Reporter: Pascal Cohen Priority: Minor I have posted in the forum the following question and someone seems to confirm this might be a bug. http://forum.hibernate.org/viewtopic.php?t=982385&highlight= Thanks in advance for advice -- 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, 12 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2041) Update with unaltered natural-id fails

by Jim Pease (JIRA)

Update with unaltered natural-id fails -------------------------------------- Key: HHH-2041 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2041 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: hibernate-3.1.3, mysql-4.1.12 Reporter: Jim Pease This may be a duplicate of http://opensource.atlassian.com/projects/hibernate/browse/HHH-1574. Getting following error: caused by: org.hibernate.HibernateException: immutable natural identifier of an instance of edu.syr.lsb.gmt.impl.LinkImpl was altered at org.hibernate.event.def.DefaultFlushEntityEventListener.checkNaturalId(DefaultFlushEntityEventListener.java:80) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:155) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:106) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) ... This is occurring without modifications to the natural identifier, which is mapped as follows: <natural-id> <property name="activityRef" column="ACTIVITY_REF" length="255" not-null="true" /> <many-to-one name="goal" class="GoalImpl" column="GOAL_ID" not-null="true" cascade="none" /> </natural-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

15 years, 12 months

2
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-1574) AbstractEntityPersister.getNaturalIdentifierSnapshot doesn't work with many-to-one ids (Alex Burgel)

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1574?page=c... ] Gail Badner updated HHH-1574: ----------------------------- Assignee: Gail Badner Fix Version/s: 3.6 3.5.2 Summary: AbstractEntityPersister.getNaturalIdentifierSnapshot doesn't work with many-to-one ids (Alex Burgel) (was: AbstractEntityPersister.getNaturalIdentifierSnapshot doesn't work with many-to-one ids) > AbstractEntityPersister.getNaturalIdentifierSnapshot doesn't work with many-to-one ids (Alex Burgel) > ---------------------------------------------------------------------------------------------------- > > Key: HHH-1574 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1574 > Project: Hibernate Core > Issue Type: Patch > Affects Versions: 3.1.2 > Reporter: Alex Burgel > Assignee: Gail Badner > Fix For: 3.5.2, 3.6 > > Attachments: resolveentity.patch, resolveentity32.patch, testcase.zip > > > i just upgraded from 3.0.5 to 3.1.2, and i started seeing this problem. i'm not exactly sure where the bug is here, but this is what i'm seeing: > i have a class, Subscription, which has a natural-id of class Subscriber and Edition (excerpts of relevant mapping files below). > when Subscription is unloaded, if i make a change, then commit the session, i see this exception: > HibernateException: immutable natural identifier of an instance of Subscription was altered > this gets thrown from DefaultFlushEntityEventListener.checkNaturalId() line 80. > i traced through that method, this is what happens: > 1. in checkNaturalId, loaded == null , so getNaturalIdSnapshot() is called > 2. this ends up generating some sql that selects the SubscriptionId and EditionId from the Subscription row. > 3. the sql is generated in AbstractEntityPersister.getNaturalIdentifierSnapshot(), which calls hydrate for each returned column of the natural-id, > 4. but hydrate only returns the id, instead of the actual entity > 5. so this array of ids (instead of entities) ends up back in DefaultFlushEntityEventListener.checkNaturalId() as 'loaded', which gets compared to 'current' > the trouble is that 'current' contains the entities, but 'loaded' only contains the ids of those entites, so the natural-id check fails, and i get the exception. > this only happens when 'loaded' is null in checkNaturalId(). > the javadocs for hydrate say you have to call "resolve" afterwards... this isn't being done, so maybe thats the fix. if the natural-id is not just simple properties, then resolve should also be called. > <class name="Subscription" table="Subscriptions" batch-size="10"> > <id name="id" column="Id" type="int"><generator class="native" /></id> > <natural-id> > <many-to-one name="subscriber" class="Subscriber" column="SubscriberId" /> > <many-to-one name="edition" class="Edition" column="EditionId" /> > </natural-id> > .... > </class> > <class name="Subscriber" table="Subscriber"> > <id name="id" column="id" type="int"><generator class="native" /></id> > <map name="subscriptions" inverse="true" cascade="all,delete-orphan" batch-size="10"> > <key column="SubscriberId" /> > <map-key-many-to-many column="EditionId" class="Edition" /> > <one-to-many class="Subscription" /> > </map> > </class> -- 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, 12 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5215) SQLQueryImpl Memory Leak causes OutOfMemoryException

by Pamir Erdem (JIRA)

SQLQueryImpl Memory Leak causes OutOfMemoryException ---------------------------------------------------- Key: HHH-5215 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5215 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.2 Environment: Sun Solaris 10 Sparc Reporter: Pamir Erdem Attachments: nativequeryspec.jpg, Query.jpg, sameQueryOutGoingRef.jpg In one of our batch operations gets OutOfMemoryExcetion. Working on heap dump, it is found out that, same query cached more than once. In the picture below the query is shown. !Query.jpg! After we found out that the root cause of the problem is the QueryPlanCache, the batch was executed under eclipse environment to find what was wrong. Altough the only qery is the query.jpg the query plan cache was so high that it can be seen easly from MAT. !nativequeryspec.jpg! We get the picture below by going outgoing references from MAT. !sameQueryOutGoingRef.jpg! >From debugging view of eclipse, we want to produce the problem step by step to prove the heap dump. The first step was looking at the source code where hashCode was calculated. !! -- 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, 12 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3256) OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart)

by Tom Muldoon (JIRA)

OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart) -------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3256 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3256 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, MySQL 5 Reporter: Tom Muldoon After a JBoss restart, the in-memory hiValue is -1. As such, the callback.getNextValue( ) method is invoked twice. With an increment size of 50 and a current database next_val of 10000, the PooledOptimizer.generate method returns a value of 10000 (as expected) and sets the in memory hiValue to 10050 (also as expected), however, it sets the db next_val to 10100. Shouldn't the db next_val be kept in sync with the in-memory hiValue (i.e. 10050)? -- 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, 12 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5214) Error with temporary tables

by Carlos Pinzon (JIRA)

Error with temporary tables --------------------------- Key: HHH-5214 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5214 Project: Hibernate Core Issue Type: Bug Reporter: Carlos Pinzon Priority: Blocker Hi I'm having this error with hibernate when I try to update a table I create the HT_<TABLE_NAME> table and didn't some body know how to fix this error or exist a way to disable the cleanup functionality MultiTableUpd W org.hibernate.hql.ast.exec.AbstractStatementExecutor dropTemporaryTableIfNecessary unable to cleanup temporary id table after use java.sql.SQLException: ORA-00942: table or view does not exist -- 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, 12 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5053) Duplicate primary keys when using the SEQUENCE strategy due to underlying sequence not being updated when the SequenceGenerator's allocatedSize is greater than 1

by atomicknight (JIRA)

Duplicate primary keys when using the SEQUENCE strategy due to underlying sequence not being updated when the SequenceGenerator's allocatedSize is greater than 1 ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5053 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2 PostgreSQL 8.4.1 (JDBC driver 8.4-701 JDBC4) Glassfish v3 (build 74.2) JDK 1.6.0_18 Reporter: atomicknight Attachments: jpa-test.war, table1.sql When the SequenceGenerator's allocatedSize is greater than 1, the underlying sequence associated with the table doesn't ever seem to be updated by Hibernate except on application startup. The test case uses an allocatedSize of 3, corresponding to an increment value of 3 in the underlying sequence. Here's how to use the test case (requires EJB 3.1): 1) Set up the database using the attached SQL dump, then load the application 2) Access the test page via http://localhost:8080/jpa-test/test. You should see a page with the word "Done!" 3) Undeploy and redeploy the application 4) Access the test page again. You should encounter an error page indicating that the transaction was aborted. Here's what I observed at the database level while following the above steps: 1) Sequence is created with a start value of 1 and increment value of 3. 2) Hibernate increments the sequence to 4. The application then inserts rows with IDs 12-31. 3) No change - the sequence still has a value of 4. 4) Hibernate increments the sequence to 7. The application attempts to insert a row with ID 21, but fails because the ID was already used in step 2. Setting the SequenceGenerator's allocatedSize to 1 as well as changing the increment value of the sequence to 1 gives the correct behavior. -- 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, 12 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-324) @DynamicBoost(BoostStrategy.class)

by Emmanuel Bernard (JIRA)

@DynamicBoost(BoostStrategy.class) ---------------------------------- Key: HSEARCH-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-324 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.1.1, 3.2.0 This sounds like an interesting feature. We could do something very similar to the new AnalyzerDiscriminator approach. The use case is explained http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78... Need some analysis before the jump We can do that in 3.1.1, but no hard pressure. -- 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, 12 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5207) Unexpected exception occurs during refresh of a transient immutable business object.

by James Norton (JIRA)

Unexpected exception occurs during refresh of a transient immutable business object. ------------------------------------------------------------------------------------ Key: HHH-5207 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5207 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.0-Final Environment: Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production, Hibernate 3.5.1, Spring 3.0.2, Struts 1.3.10, J2SE 1.6.0_14 Reporter: James Norton Attachments: TestCase.zip As mentioned in the Hibernate Forums (_[Cannot make an immutable entity modifiable|https://forums.hibernate.org/viewtopic.php?f=1&t=1003756]_), I am dealing with an issue brought to my attention wherein a detached transient business object is being refreshed by the session and returns an exception. The exception(_See Below_) is thrown from within the DefaultRefreshEventListener's onRefresh method at the end of processing just prior to returning the refreshed object. ---- {{{code:title=The Exception} java.lang.IllegalStateException: Cannot make an immutable entity modifiable. at org.hibernate.engine.EntityEntry.setReadOnly(EntityEntry.java:314) at org.hibernate.engine.StatefulPersistenceContext.setEntityReadOnly(StatefulPersistenceContext.java:1388) at org.hibernate.engine.StatefulPersistenceContext.setReadOnly(StatefulPersistenceContext.java:1365) at org.hibernate.impl.SessionImpl.setReadOnly(SessionImpl.java:1982) at org.hibernate.event.def.DefaultRefreshEventListener.onRefresh(DefaultRefreshEventListener.java:155) at org.hibernate.event.def.DefaultRefreshEventListener.onRefresh(DefaultRefreshEventListener.java:62) at org.hibernate.impl.SessionImpl.fireRefresh(SessionImpl.java:1108) at org.hibernate.impl.SessionImpl.refresh(SessionImpl.java:1088) at bug.BugReport.testRefreshTransientImmutable(BugReport.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:168) at org.hibernate.junit.functional.FunctionalTestCase.runTest(FunctionalTestCase.java:125) at junit.framework.TestCase.runBare(TestCase.java:134) at org.hibernate.junit.UnitTestCase.runBare(UnitTestCase.java:63) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.runTest(FunctionalTestClassTestSuite.java:115) at junit.framework.TestSuite.run(TestSuite.java:238) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.run(FunctionalTestClassTestSuite.java:84) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) {code}}} ---- This problem showed up during an update from Hibernate libraries 3.3.2. The issue was proven not to exist in the previous version through the attached test case. It is mine and my coworkers opinion that the issue lies with the DefaultRefreshEventListener attempting to set the read only state of the refreshed object _back_ to the state that it was in prior to refreshing. Being that the object is detached from the current session, and therefore viewed as transient, the previous state of the object cannot be ascertained and the listener tries to set the read only to source default. ---- {{{code:title=DefaultRefreshEventListener lines 152 - 156 \\\\ onRefresh(RefreshEvent event, Map refreshedAlready)} // Keep the same read-only/modifiable setting for the entity that it had before refreshing; // If it was transient, then set it to the default for the source. if ( result != null ) { source.setReadOnly( result, ( e == null ? source.isDefaultReadOnly() : e.isReadOnly() ) ); } {code}}} ---- While this appears to be a fairly straightforward procedure, the object being refreshed is immutable. With the object being transient, the persistence context does not have an entry for the object and the _source_ tries to {{*setReadOnly*}} to {{source.isDefaultReadOnly()}}. This results in the session trying to set an immutable object's state to writable. -- 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, 12 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4065) Incorrect SQL is used for HQL if the number of values for a filter collection parameter is changed

by Nicklas Nordborg (JIRA)

Incorrect SQL is used for HQL if the number of values for a filter collection parameter is changed -------------------------------------------------------------------------------------------------- Key: HHH-4065 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4065 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Environment: Hibernate 3.3.2 Reporter: Nicklas Nordborg Attachments: trace.txt I think that maybe the fix for HHH-530 has introduced a problem with filters that has a collection-type parameter. If the number of parameters in that collection changes during the lifetime of a SessionFactory the SQL that is used becomes incorrect and either has too many or too few parameter placeholders (eg. '?') in the SQL. There was no problem in Hibernate 3.3.1. A typical error message is: java.sql.SQLException: Parameter index out of bounds. 2 is not between valid values of 1 and 1 Below is some pseudo-code that shows what happens when the number of values in a collection is increased from 1 to 2. The 'memberOf' is a simple filter on the `id` column: `id` IN (:items) String hql = "select n from NewsData n"; List idList = new ArrayList(); idList.add(1); Session s = .... // create new session s.enableFilter("memberOf").setParameterList("items", idList); s.createQuery(hql).list(); // SQL: select .... `News` newsdata0_ where newsdata0_.`id` IN (?) s.close(); idList.add(2); s = ... // create new session s.enableFilter("memberOf").setParameterList("items", idList); s.createQuery(hql).list(); // <--- error here with 3.3.2 but works with 3.3.1 // SQL (3.3.2): select .... `News` newsdata0_ where newsdata0_.`id` IN (?) // SQL (3.3.1): select .... `News` newsdata0_ where newsdata0_.`id` IN (?, ?) I am attaching a file with TRACE-level output from both Hibernate 3.3.2 and 3.3.1. The relevant difference seems to be that in Hibernate 3.3.2 the query plan is cached with: [SQL_TOKEN] SqlFragment: 'newsdata0_.`id` IN (?)' but in Hibernate 3.3.1 with: [SQL_TOKEN] SqlFragment: 'newsdata0_.`id` IN (:memberOf.items)' -- 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, 12 months

5
14
0 / 0

[Hibernate-JIRA] Created: (HHH-5211) no need to create a schema first when run this test org.hibernate.test.sql.hand.custom.db2.DB2CustomSQLTest

by Strong Liu (JIRA)

no need to create a schema first when run this test org.hibernate.test.sql.hand.custom.db2.DB2CustomSQLTest ----------------------------------------------------------------------------------------------------------- Key: HHH-5211 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5211 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Strong Liu Fix For: 3.5.2, 3.6 creating a schema in DB2 is not something that applications should do -- 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, 12 months

1
3
0 / 0

[Hibernate-JIRA] Commented: (HBX-633) Reverse engineered VERSION columns cause ClassCastException

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-633?page=co... ] Max Rydahl Andersen commented on HBX-633: ----------------------------------------- as written earlier: " you can work around it via a custom reveng strategy that just returns false for useColumnForOptimisticLock." > Reverse engineered VERSION columns cause ClassCastException > ----------------------------------------------------------- > > Key: HBX-633 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-633 > Project: Hibernate Tools > Issue Type: Bug > Affects Versions: 3.1beta4 > Environment: Oracle 8i, ojdbc14.jar > Reporter: Gabor Kincses > > Exception in thread "main" java.lang.ClassCastException: org.hibernate.type.BigDecimalType > at org.hibernate.tuple.PropertyFactory.buildVersionProperty(PropertyFactory.java:83) > at org.hibernate.tuple.EntityMetamodel.<init>(EntityMetamodel.java:157) > at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:412) > at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:108) > at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) > at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:216) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1176) > at com.paypal.bdo.test.Hibernate101.main(Hibernate101.java:37) > I guess the code tries to cast the type to VersionType. -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5203) JDBCException thrown during schema export (or hbm2dll) should include sql

by Rupesh Kumar (JIRA)

JDBCException thrown during schema export (or hbm2dll) should include sql ------------------------------------------------------------------------- Key: HHH-5203 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5203 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Reporter: Rupesh Kumar The JDBCException thrown during Schema export (SchemaExport.create(), SchemaExport.importScript(), SchemaUpdate.execute()) should include the SQL string. -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Jeff Schnitzer (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Jeff Schnitzer commented on HHH-1501: ------------------------------------- This certainly sounds reasonable; I will keep an eye on HHH-2578. Thanks for the continued development! > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5199) Formula should use aliases in order by

by Stephane Epardaud (JIRA)

Formula should use aliases in order by -------------------------------------- Key: HHH-5199 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5199 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Stephane Epardaud Same bug as HB-958 but filed for hibernate 3. Not every database supports formulas or functions in WHERE clauses, and while we would love to get rid of them, it's not always realistic. It should not be hard to reuse the alias generated for formulas from the SELECT clause. Reminder: - This does not work on every DB: {noformat} SELECT length(id) FROM t ORDER BY length(id); {noformat} - This works on several DBs: {noformat} SELECT length(id) AS l FROM t ORDER BY l; {noformat} If there are any DBs where hibernate is broken because of that, it should be a Dialect feature. In the original bug report, Gavin mentioned trivial workarounds. It would be helpful to show them in the bug report too, since they might not be obvious (I've no clue for instance). -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1853) CREATE SCHEMA inside database-object need to execute before tables are created

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853?page=c... ] Steve Ebersole commented on HHH-1853: ------------------------------------- BTW I do see the benefit of something like <database>. If someone wanted to take that one and attach a patch I'd be willing to apply it (if its well done of course) > CREATE SCHEMA inside database-object need to execute before tables are created > ------------------------------------------------------------------------------ > > Key: HHH-1853 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853 > Project: Hibernate Core > Issue Type: Improvement > Affects Versions: 3.1.3 > Environment: hsqldb 1.8.0 > Reporter: Mattias Jiderhamn > Priority: Minor > Attachments: create-schema.patch, create-schema2.patch > > > In order to have Hibernate create database schemas for hsqldb, you have to insert a <database-object> in your mapping file (http://forums.hibernate.org/viewtopic.php?p=2305138). Problem is, all the database-object statements are executed after the tables are created, so tables in non-default schemas will not be created. To get around this, you have to first use Configuration.generateSchemaCreationScript() to get the schemas, and then Configuration.generateSchemaUpdateScript() to get the tables inside the schemas. > (This is a bit problematic when using Springs LocalSessionFactoryBean) -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1853) CREATE SCHEMA inside database-object need to execute before tables are created

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853?page=c... ] Steve Ebersole commented on HHH-1853: ------------------------------------- Johnathan, actually no thats not all that is necessary. If I understand what you suggest (i.e. Hibernate sees the schema or catalog in your mappings and just creates/drops them on its own) then at the very least we have to add to the dialects the notion of "how do we create a schema or a catalog on this database?". Not to mention what Max pointed out as to why this is extremely undesirable. > CREATE SCHEMA inside database-object need to execute before tables are created > ------------------------------------------------------------------------------ > > Key: HHH-1853 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853 > Project: Hibernate Core > Issue Type: Improvement > Affects Versions: 3.1.3 > Environment: hsqldb 1.8.0 > Reporter: Mattias Jiderhamn > Priority: Minor > Attachments: create-schema.patch, create-schema2.patch > > > In order to have Hibernate create database schemas for hsqldb, you have to insert a <database-object> in your mapping file (http://forums.hibernate.org/viewtopic.php?p=2305138). Problem is, all the database-object statements are executed after the tables are created, so tables in non-default schemas will not be created. To get around this, you have to first use Configuration.generateSchemaCreationScript() to get the schemas, and then Configuration.generateSchemaUpdateScript() to get the tables inside the schemas. > (This is a bit problematic when using Springs LocalSessionFactoryBean) -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1853) CREATE SCHEMA inside database-object need to execute before tables are created

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853?page=c... ] Steve Ebersole commented on HHH-1853: ------------------------------------- I think the only viable solution is a new construct that explicitly identifies the thing to be created first and dropped last. Perhaps <database> as a corollary to <database-object>? So <database> would name the create/drop commands just like with <database-object> but their importance is in ordering. What I certainly do not want is dialects having to know how to generated create/drop DDL for these things. WDYT? > CREATE SCHEMA inside database-object need to execute before tables are created > ------------------------------------------------------------------------------ > > Key: HHH-1853 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853 > Project: Hibernate Core > Issue Type: Improvement > Affects Versions: 3.1.3 > Environment: hsqldb 1.8.0 > Reporter: Mattias Jiderhamn > Priority: Minor > Attachments: create-schema.patch, create-schema2.patch > > > In order to have Hibernate create database schemas for hsqldb, you have to insert a <database-object> in your mapping file (http://forums.hibernate.org/viewtopic.php?p=2305138). Problem is, all the database-object statements are executed after the tables are created, so tables in non-default schemas will not be created. To get around this, you have to first use Configuration.generateSchemaCreationScript() to get the schemas, and then Configuration.generateSchemaUpdateScript() to get the tables inside the schemas. > (This is a bit problematic when using Springs LocalSessionFactoryBean) -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- To be clear, in semi-pseudo code I am talking about something like: {code} Type type = getExplicitType(); if ( type == null ) { // user specified no explicit type in metadata, ask TypeFactory to resolve the type heuristically... // (this part happens today too) type = TypeFactory.heuristicType( getPropertyJavaType() ); if ( type == null ) { throw ...; } } if ( sqlSizesSpecified() ) { // this part would be new type = dialect.remapTypeIfNecessary( type, lenght, ... ); } {code} > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- Hibernate does not take into account the length/scale/precision nor the dialect when determining the Hibernate Type to use for a property which omitted specifying one. What it does is to basically choose a default based solely on the Java type. Using that it performs a lookup via a call to TypeFactory.heuristicType. What we'd need to do here is to inject a process that consults the dialect based on the sql-type (from the resolved Hibernate Type) and length and asks whether it should use an alternate Hibernate Type (aka, instead of StringType[String->VARCHAR] use MaterializeClobType[String->CLOB] because the length exceeded some limit for that dialect. That I'd be OK with. Problem is that the dialect is not known when we are doing this process :( This is something I plan on addressing, but not until 3.7 or later. See HHH-2578 for the details of that > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5196) Deprecate Type methods on org.hibernate.Hibernate

by Steve Ebersole (JIRA)

Deprecate Type methods on org.hibernate.Hibernate ------------------------------------------------- Key: HHH-5196 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5196 Project: Hibernate Core Issue Type: Task Components: core Affects Versions: 3.5.1 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.x Still questionable whether I will remove them in 3.6 or just leave them deprecated and just change them to immediately throw exception. This is related to the "scoping" of non-basic types as per HHH-5182 -- 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

16 years

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5182) Inject SessionFactory into "non-basic" Types

by Steve Ebersole (JIRA)

Inject SessionFactory into "non-basic" Types -------------------------------------------- Key: HHH-5182 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5182 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 This is possible after HHH-5138. Technically we will inject a TypeFactory.TypeScope reference which offers a single method: resolveSessionFactory() -- 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

16 years

1
3
0 / 0

[Hibernate-JIRA] Created: (HV-319) ConstraintPayload not part of javax.validation

by Marc Schipperheyn (JIRA)

ConstraintPayload not part of javax.validation ---------------------------------------------- Key: HV-319 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-319 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.2.GA Reporter: Marc Schipperheyn Assignee: Hardy Ferentschik The documentation describes Constraint Payload as a way to implement marker interfaces for a custom constraint. However, the ConstraintPayload is not part of javax.validation 1.0.0.GA. It was part of 1.0.0.CR4 and subsequently disappeared from the release. Not sure if this was intentional, but as it is, we cannot use that feature and either it should be added to javax.validation 1.0.1, disappear from the documentation or a Hibernate validator specific implementation should be created for 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

16 years

2
5
0 / 0

[Hibernate-JIRA] Commented: (HBX-633) Reverse engineered VERSION columns cause ClassCastException

by Taran Preet Singh Sodhi (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-633?page=co... ] Taran Preet Singh Sodhi commented on HBX-633: --------------------------------------------- I' am facing the same issue in reverse enginering and can't afford to have a manual intervention to control it due to daily build. Can we get a solution > Reverse engineered VERSION columns cause ClassCastException > ----------------------------------------------------------- > > Key: HBX-633 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-633 > Project: Hibernate Tools > Issue Type: Bug > Affects Versions: 3.1beta4 > Environment: Oracle 8i, ojdbc14.jar > Reporter: Gabor Kincses > > Exception in thread "main" java.lang.ClassCastException: org.hibernate.type.BigDecimalType > at org.hibernate.tuple.PropertyFactory.buildVersionProperty(PropertyFactory.java:83) > at org.hibernate.tuple.EntityMetamodel.<init>(EntityMetamodel.java:157) > at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:412) > at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:108) > at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) > at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:216) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1176) > at com.paypal.bdo.test.Hibernate101.main(Hibernate101.java:37) > I guess the code tries to cast the type to VersionType. -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-305) JPATraversableResolver tries to access properties that do not exist

by Stephan Bublava (JIRA)

JPATraversableResolver tries to access properties that do not exist ------------------------------------------------------------------- Key: HV-305 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-305 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.1.0.Beta1 Environment: Hibernate Validator 4.1.0.Beta1, Hibernate 3.5.0-Final Reporter: Stephan Bublava Assignee: Hardy Ferentschik Attachments: validation-test.zip Prerequisites: - two entities that model a bidirectional 1:n relationship - both have class-level constraints - the collection that represent the n-side of the relationship is annotated @Valid - Hibernate 3.5 is in the class path In this case, validation of the entity that represents the 1-side fails, because JPATraversableResolver attempts to access a property that doesn't exist. (It looks for the collection in the wrong entity.) Changing any of the last three conditions makes the problem disappear... I've attached a test-cases that demonstrates this issue 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Jeff Schnitzer (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Jeff Schnitzer commented on HHH-1501: ------------------------------------- I don't have any objection to the choice of efficient default types for unspecified lengths. However, if I specify @Column(length=65536) on a String field, I expect that Hibernate's Derby dialect should be smart enough to make it a CLOB (or whatever type can actually hold a 64k string). Caveat: It was 3.5 years ago that I last considered this issue and I have no idea what Hibernate will do with Derby today. If putting @Column(length=XXXX) on byte[] and String types works properly, you should just close this issue. > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- A compromise I could see would be a new annotation to allow defining the JDBC type explicitly: @SqlType( java.sql.Types.LONGVARCHAR ) we could use that in determining the "hibernate type" > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- {quote} I should be able to declare a byte[] field in Java and Hibernate should figure out how to map that to various databases. {quote} Its not a question of "various databases". Its a question of "various JDBC types". And that part we have done. That is why there is a StringType (String->VARCHAR), a MaterializedClobType (String->CLOB), etc. All you have told Hibernate is "I have a String". Again, short of querying the JDBC metadata for that column (which will not happen, see previous comment) how are you thinking HIbernate is supposed to know that this particular String property is a CLOB while some other property is a VARCHAR? Why is it soooooo unreasonable that you tell it "hey, use your super-duper 'materialized_clob' type for this particular property"? > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- Sergey, attitude like that is not going to get you help. Guys, so look at it like this. Lets take the String case (the byte[] is really the same). So you tell Hibernate to map this property as a String. In the absence of you telling it anything else it needs to determine the proper database type (well techincally the JDBC type). What you both are asking is that it do some form of database look up to make this determination (you may not now it, but that is in fact what you are asking). That is not reasonable, imho, when Hibernate already provides means for y'all to tell it the type (Hibernate type which binds the java and sql type) to use for that property. If thats *really* what you want I'll be happy to add an interface that Hibernate can ask for the Hibernate type it should use for a given property when that property defines no type. Y'all can then do this look up in a custom impl of that interface. Why do I say that that is what you are asking for? Well how else are you expecting it to know what JDBC type to correlate to that java type for that given property? Surely you are not suggesting that we assume the widest possible JDBC data type (aka map all strings to CLOB by default). That would be insane. > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Jeff Schnitzer (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Jeff Schnitzer commented on HHH-1501: ------------------------------------- I'm in agreement with Sergey. I have developed some software that *theoretically* can be deployed on any database. This is one of the promises of ORM, no? In practice, this doesn't really work very well, and this is one of the reasons why. I should be able to declare a byte[] field in Java and Hibernate should figure out how to map that to various databases. You can point at Derby as broken (maybe it is) but the bottom line is that this is something the ORM layer should worry about, not individual developers - or worse - the poor bastards that download my code and try to run it against their obscure XYZ database. I'd like to say that my software works "on any database with a Hibernate dialect" but instead I have to say that my software works "on any database with a *working* Hibernate dialect". > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Sergey Vladimirov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Sergey Vladimirov commented on HHH-1501: ---------------------------------------- Steve, I'm sorry that it looks like i require some inadequate behavior from Hibernate and/or it's developers. It's purely your rule what shall it do and how should it work. The reason of filling this bug is that i feel that Derby dialect has not just a wrong behaviour, but it is incompatible with other dialects because of this bug. Let me explain. I'm considering Hibernate as the most powerfull JPA implementation at this moment. As part of it I considering it as something, that abstracts my application from database vendor-specific details. In a such way, that I can throw out MySQL InnoDB (that is currently used) and use Derby (that is used for testing now) or Oracle or MySQL MyISAM or MS SQL. And, according to my understanding of Hibernate place in application stack, such change shall only require single change in application configuration - just replace the dialect. But the issue, described in this bug, introduces incompatibility between, for example, MySQL and Derby. If I declare some property as LOB String, it can contain up to 2 Gb of data, if MySQL dialect is used. But with Derby dialect it can contain only 32 Kb of data. Thus, we have and incompatibility between dialect, and, i believe, Derby dialect shall be fixed. Or, at least, it shall be described clearly by HIbernate, that 32 Kb is the minimum guarantly of Lob length. Filling this bug was a gesture, not a requirement. We already created our version of MySQL, MS SQL and Derby dialects to enforce some additional compatibility. But I believe that those fixes and such interdialect compatibility shall be part of Hibernate without additional code by user in future versions of Hibernate. If you insist that such changes shall not be made in Hibernate - it's okay. But personally i believe that such a requirement will arise again as soon as someone will need to work with different databases from same application. Thanks for your work and best regards, Sergey Vladimirov > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-672) bug in ComponentType isModified method ClassCastException (dom4j)

by Jason Clawson (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-672?page=co... ] Jason Clawson commented on HHH-672: ----------------------------------- I apologize, I am not sure how to write a unit test for ComponentType. I am not that familiar with how the object graph gets created. If someone could help me out with this, I would appreciate it. > bug in ComponentType isModified method ClassCastException (dom4j) > ----------------------------------------------------------------- > > Key: HHH-672 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-672 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc3 > Environment: Hibernate 3.1 (stream), oracle 9.02 > Reporter: Jessica Marchiori > Attachments: ComponentType.java.patch > > > There is a bug with the EntityMode.DOM4j in class ComponentType method isModified. The association of oldValues causes a ClassCastException > The original code was > public boolean isModified(Object old, Object current, SessionImplementor session) > throws HibernateException { > if ( current == null ) return old != null; > if ( old == null ) return current != null; > Object[] currentValues = getPropertyValues( current, session ); > Object[] oldValues = ( Object[] ) old; > } > > for ( int i = 0; i < currentValues.length; i++ ) { > if ( propertyTypes[i].isModified( oldValues[i], currentValues[i], session ) ) { > return true; > } > } > return false; > } > I have changed the code as below > public boolean isModified(Object old, Object current, SessionImplementor session) > throws HibernateException { > if ( current == null ) return old != null; > if ( old == null ) return current != null; > Object[] currentValues = getPropertyValues( current, session ); > Object[] oldValues = getPropertyValues( old, session ); > > for ( int i = 0; i < currentValues.length; i++ ) { > if ( propertyTypes[i].isModified( oldValues[i], currentValues[i], session ) ) { > return true; > } > } > return false; > } > and it works -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-672) bug in ComponentType isModified method ClassCastException (dom4j)

by Jason Clawson (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-672?page=co... ] Jason Clawson updated HHH-672: ------------------------------ Attachment: ComponentType.java.patch Patch for ComponentType > bug in ComponentType isModified method ClassCastException (dom4j) > ----------------------------------------------------------------- > > Key: HHH-672 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-672 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc3 > Environment: Hibernate 3.1 (stream), oracle 9.02 > Reporter: Jessica Marchiori > Attachments: ComponentType.java.patch > > > There is a bug with the EntityMode.DOM4j in class ComponentType method isModified. The association of oldValues causes a ClassCastException > The original code was > public boolean isModified(Object old, Object current, SessionImplementor session) > throws HibernateException { > if ( current == null ) return old != null; > if ( old == null ) return current != null; > Object[] currentValues = getPropertyValues( current, session ); > Object[] oldValues = ( Object[] ) old; > } > > for ( int i = 0; i < currentValues.length; i++ ) { > if ( propertyTypes[i].isModified( oldValues[i], currentValues[i], session ) ) { > return true; > } > } > return false; > } > I have changed the code as below > public boolean isModified(Object old, Object current, SessionImplementor session) > throws HibernateException { > if ( current == null ) return old != null; > if ( old == null ) return current != null; > Object[] currentValues = getPropertyValues( current, session ); > Object[] oldValues = getPropertyValues( old, session ); > > for ( int i = 0; i < currentValues.length; i++ ) { > if ( propertyTypes[i].isModified( oldValues[i], currentValues[i], session ) ) { > return true; > } > } > return false; > } > and it works -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-672) bug in ComponentType isModified method ClassCastException (dom4j)

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-672?page=co... ] Gail Badner commented on HHH-672: --------------------------------- Please do the following: * svn co http://anonsvn.jboss.org/repos/hibernate/core/trunk/ * update an existing test or add a new test to testsuite/src/test/java/org/hibernate/test/component * attach a patch with the updated/added unit test using svn diff * attach a patch with your fix using svn diff Thanks, Gail > bug in ComponentType isModified method ClassCastException (dom4j) > ----------------------------------------------------------------- > > Key: HHH-672 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-672 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc3 > Environment: Hibernate 3.1 (stream), oracle 9.02 > Reporter: Jessica Marchiori > > There is a bug with the EntityMode.DOM4j in class ComponentType method isModified. The association of oldValues causes a ClassCastException > The original code was > public boolean isModified(Object old, Object current, SessionImplementor session) > throws HibernateException { > if ( current == null ) return old != null; > if ( old == null ) return current != null; > Object[] currentValues = getPropertyValues( current, session ); > Object[] oldValues = ( Object[] ) old; > } > > for ( int i = 0; i < currentValues.length; i++ ) { > if ( propertyTypes[i].isModified( oldValues[i], currentValues[i], session ) ) { > return true; > } > } > return false; > } > I have changed the code as below > public boolean isModified(Object old, Object current, SessionImplementor session) > throws HibernateException { > if ( current == null ) return old != null; > if ( old == null ) return current != null; > Object[] currentValues = getPropertyValues( current, session ); > Object[] oldValues = getPropertyValues( old, session ); > > for ( int i = 0; i < currentValues.length; i++ ) { > if ( propertyTypes[i].isModified( oldValues[i], currentValues[i], session ) ) { > return true; > } > } > return false; > } > and it works -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-672) bug in ComponentType isModified method ClassCastException (dom4j)

by Jason Clawson (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-672?page=co... ] Jason Clawson commented on HHH-672: ----------------------------------- Can someone please fix this issue. It's been 5 years.... 5 YEARS guys, and a patch has been posted. Its a very simple fix... Please fix this. Thank you. > bug in ComponentType isModified method ClassCastException (dom4j) > ----------------------------------------------------------------- > > Key: HHH-672 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-672 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc3 > Environment: Hibernate 3.1 (stream), oracle 9.02 > Reporter: Jessica Marchiori > > There is a bug with the EntityMode.DOM4j in class ComponentType method isModified. The association of oldValues causes a ClassCastException > The original code was > public boolean isModified(Object old, Object current, SessionImplementor session) > throws HibernateException { > if ( current == null ) return old != null; > if ( old == null ) return current != null; > Object[] currentValues = getPropertyValues( current, session ); > Object[] oldValues = ( Object[] ) old; > } > > for ( int i = 0; i < currentValues.length; i++ ) { > if ( propertyTypes[i].isModified( oldValues[i], currentValues[i], session ) ) { > return true; > } > } > return false; > } > I have changed the code as below > public boolean isModified(Object old, Object current, SessionImplementor session) > throws HibernateException { > if ( current == null ) return old != null; > if ( old == null ) return current != null; > Object[] currentValues = getPropertyValues( current, session ); > Object[] oldValues = getPropertyValues( old, session ); > > for ( int i = 0; i < currentValues.length; i++ ) { > if ( propertyTypes[i].isModified( oldValues[i], currentValues[i], session ) ) { > return true; > } > } > return false; > } > and it works -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Gail Badner commented on HHH-1501: ---------------------------------- Steve, I've corrected my comment from http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?focuse.... Thanks for catching that. > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Issue Comment Edited: (HHH-1501) insert long string (more than 32700) fails on derby

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Gail Badner edited comment on HHH-1501 at 5/5/10 3:09 PM: ---------------------------------------------------------- In that case, DerbyDialect (or DBDialect?) would need to be updated to work using the JPA defaults. The Hibernate types "materialized_clob" and "materialized_blob" use CLOB and BLOB. was (Author: gbadner): In that case, DerbyDialect (or DBDialect?) would need to be updated to work using the JPA defaults. The Hibernate types "materialized_clob" and "materialized_blob" use "long varchar" and "long varchar for bit data". > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5198) Generating schema for JoinColumn with SecondaryTable and SingleTable inheritance.

by Yasen Terziivanov (JIRA)

Generating schema for JoinColumn with SecondaryTable and SingleTable inheritance. --------------------------------------------------------------------------------- Key: HHH-5198 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5198 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Yasen Terziivanov Attachments: envers-test-ejbProject-and-client.zip Well basically as described in [here | https://community.jboss.org/thread/151214] when generating db schema if I have a secondary table and a one2one property and I want to specify that the join column should be in the secondary table using @JoinColumn annotation in the generated script the column is missing from the audited table. This is tested with the 1.2.2 version of envers. -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5194) SequenceHiLoGenerator does not update the lo value

by Swen Thümmler (JIRA)

SequenceHiLoGenerator does not update the lo value -------------------------------------------------- Key: HHH-5194 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5194 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Reporter: Swen Thümmler Priority: Critical SequenceHiLoGenerator checks lo > maxLo but never increments lo. This leads to duplicate ids when using the same sequence for multiple tables. This change was made in r18789 -- 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

16 years

2
4
0 / 0

[Hibernate-JIRA] Issue Comment Edited: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole edited comment on HHH-1501 at 5/5/10 9:29 AM: ------------------------------------------------------------- Gail, I see MaterializedClob using CLOB not LONGVARCHAR (which makes sense right?). What am i missing? http://fisheye.jboss.org/browse/Hibernate/core/trunk/core/src/main/java/o... http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/core/s... Similarly for MaterializedBlob, I see BLOB http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/core/s... was (Author: steve): Gail, I see MaterializedClob using CLOB not LONGVARCHAR (which makes sense right?). What am i missing? http://fisheye.jboss.org/browse/Hibernate/core/trunk/core/src/main/java/o... http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/core/s... > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- Gail, I see MaterializedClob using CLOB not LONGVARCHAR (which makes sense right?). What am i missing? http://fisheye.jboss.org/browse/Hibernate/core/trunk/core/src/main/java/o... http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/core/s... > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Steve Ebersole commented on HHH-1501: ------------------------------------- We are not going to remove these sane attempts at limiting the size of columns we create as the default. If you want to increase the storage size you have a number of options: 1) List the column length in the metadata 2) Use an explicit Hibernate Type declaration ('materialized_clob', etc) which does what you want 3) Supply a custom dialect that defines the sizes *you* want. > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5183) Inheritance (single table) and @SecondaryTable

by Nicolas Romanetti (JIRA)

Inheritance (single table) and @SecondaryTable ----------------------------------------------- Key: HHH-5183 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5183 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.2 Environment: Hibernate 3.3.2.GA H2 Database version 1.2.131 Reporter: Nicolas Romanetti When @SecondaryTable is declared (with the same secondary table name) in 2 distinct entities that belong to the same hierarchy (single table inheritance), hibernate considers that the secondary tables are different! Indeed, when persisting the entity, if the properties (using the secondary table) are set in the entity itself and its parent, hibernate does 2 inserts on the secondary table instead of one (one for the 'secondary' property of the parent, and one for the 'secondary' property of the current entity) This triggers a pk violation exception as the same PK is used twice on the secondary table. -- 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

16 years

3
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Gail Badner commented on HHH-1501: ---------------------------------- In that case, DerbyDialect (or DBDialect?) would need to be updated to work using the JPA defaults. The Hibernate types "materialized_clob" and "materialized_blob" use "long varchar" and "long varchar for bit data". > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5030) BaseRegionAdapter shouldn't rely on optional Cache#toMap method

by Adrian Hummel (JIRA)

BaseRegionAdapter shouldn't rely on optional Cache#toMap method --------------------------------------------------------------- Key: HHH-5030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5030 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-CR-2 Environment: hibernate-oscache 3.5.0.Beta-1 Reporter: Adrian Hummel Attachments: bugreport.zip Get an {{UnsupportedOperationException}} when checking the L2 cache if it contains an entity: {code} emf.getCache().contains(MyEntity.class, pk); {code} Result: {code} java.lang.UnsupportedOperationException at org.hibernate.cache.OSCache.toMap(OSCache.java:126) at org.hibernate.cache.impl.bridge.BaseRegionAdapter.contains(BaseRegionAdapter.java:62) at org.hibernate.impl.SessionFactoryImpl$CacheImpl.containsEntity(SessionFactoryImpl.java:967) at org.hibernate.impl.SessionFactoryImpl$CacheImpl.containsEntity(SessionFactoryImpl.java:962) at org.hibernate.ejb.EntityManagerFactoryImpl$JPACache.contains(EntityManagerFactoryImpl.java:164) ... {code} The {{Cache#toMap}} method is optional (according to Javadoc), thus, {{BaseRegionAdapter}} shouldn't rely on this method. -- 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

16 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5189) Same table is mapped twice but different primary keys. Giving error while secondPassCompileForeignKeys.

by Sardar Romender Singh (JIRA)

Same table is mapped twice but different primary keys. Giving error while secondPassCompileForeignKeys. ------------------------------------------------------------------------------------------------------- Key: HHH-5189 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5189 Project: Hibernate Core Issue Type: Bug Environment: OS: Linux DB : Oracle Hibernate Version : 3.2.5 ga Reporter: Sardar Romender Singh Priority: Trivial Two tables are mapped with different primary keys. Example : I have customer table which is mapped to Customer Entity whose primary keys are Customer id and status (which says authorized customer or un authorized customer). I have one more entity mapped to same table CustomerLight which will load only some specific fields of the customer which contains the where clause which specifies to load only authorized customer. There are some more entities which are mapped to customer entity with key-many-to-one relationship. After loading of the mapping file while validation of foriegn key constraints its failing Foreign key constraint failed "must have same number of columns as the referenced primary key" This is happening only in some environments not all. -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5121) Using Oracle analytical functions causes QuerySyntaxException

by Tarek Nabil (JIRA)

Using Oracle analytical functions causes QuerySyntaxException ------------------------------------------------------------- Key: HHH-5121 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5121 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Environment: Hibernate 3.5.0-Final. Oracle 10g. Reporter: Tarek Nabil Attachments: criteria-bug.zip The CriteriaBuilder.function() method allows the creation of an expression which is supported by the target DB such as DB functions. Using this facility to call Oracle 10g (and above) analytical functions such as "COUNT(*) OVER()" produces a QuerySyntaxException. The attached test case illustrates the problem. It's a minimal Maven2 project which contains one domain class and one DAO. The domain class maps to the REGION entity from the Oracle HR schema which ships with any Oracle XE installation. I still included the script needed to create the table incase the schema is not available on the test environment. The DAO has two methods, one selects all the regions and the other attempts to select all the regions and the count of records returned using "COUNT(*) OVER()". A test class is used to test those two methods; the first test works successfully; the second gives the stack trace provided in "stack-trace.txt". I believe this bug is a major one because: 1- To get the total count of records, the only other option is to do two queries which is a lot more expensive. 2- The count is required for pagination of results which is essential for search screens. 3- Search screens which require dynamic queries are the main reason one would use criteria in the first place. I've provided instructions on the changes required to setup the Maven project in order to run the test case, which are minimal, in "readme.txt". -- 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

16 years

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Sergey Vladimirov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Sergey Vladimirov commented on HHH-1501: ---------------------------------------- My goal was to use only JPA annotations without any database-specific commands (like explicit type declaration). This, usage of type="materialized_clob" is not a good solution (just a workaround) > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5170) Used unsaved-value="any" for <composite-id>, Getting exception Object references an unsaved transient instance - save the transient instance before flushing, even though record exist in the DB

by Deepesh Seetharaman (JIRA)

Used unsaved-value="any" for <composite-id>, Getting exception Object references an unsaved transient instance - save the transient instance before flushing, even though record exist in the DB ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-5170 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5170 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: DB2-z Series, Weblogic 10.3 App Server. Reporter: Deepesh Seetharaman Attachments: EventService.hbm.xml, State.hbm.xml, test.zip I have attached the following files. i)EventService.hbm.xml ii)State.hbm.xml While I am trying to persist, EventService, by setting the State object, with only its id fields its giving the folloiwing exception. org.springframework.dao.InvalidDataAccessApiUsageException: object references an unsaved transient instance - save the transient instance before flushing: com.fareis.las.css.sys.rf.domain.State; nested exception is org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: com.fareis.las.css.sys.rf.domain.State Caused by: org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: com.fareis.las.css.sys.rf.domain.State at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:219) at org.hibernate.type.EntityType.getIdentifier(EntityType.java:397) at org.hibernate.type.ManyToOneType.isDirty(ManyToOneType.java:242) at org.hibernate.type.TypeFactory.findDirty(TypeFactory.java:576) at org.hibernate.persister.entity.AbstractEntityPersister.findDirty(AbstractEntityPersister.java:3121) at org.hibernate.event.def.DefaultFlushEntityEventListener.dirtyCheck(DefaultFlushEntityEventListener.java:472) at org.hibernate.event.def.DefaultFlushEntityEventListener.isUpdateNecessary(DefaultFlushEntityEventListener.java:197) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.springframework.orm.hibernate3.HibernateTemplate$29.doInHibernate(HibernateTemplate.java:849) at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:372) at org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:840) at org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:836) at com.fareis.core.pf.repository.hibernate.GenericHibernateRepository.findByProperty(GenericHibernateRepository.java:417) at com.fareis.las.prc.clb.el.repository.hibernate.EventHibernateRepository.findByClientBillingEventKey(EventHibernateRepository.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy1.findByClientBillingEventKey(Unknown Source) at com.fareis.prc.clb.repository.test.BillableEventRepositoryTestCase.testAddEvent(BillableEventRepositoryTestCase.java:83) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at org.springframework.test.ConditionalTestCase.runBare(ConditionalTestCase.java:69) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) I am creating the instance like this. EventService service = new EventService(); State state = new State(); StateId id = new StateId(); id.setStateCode("DAS"); Country country = new Country(); country.setCountryCode("US"); id.setCountryCode(country); state.setId(id); service.setBillingId(10); service.setStatusCode("A"); service.setState(state); service.setClientBillingEventKey(clientBillingEvent); service.setLastUpdateSourceId("TEST"); service.setLastUpdateTimestamp(new java.util.Date()); service.setLastUpdateUserId("sdeepesh"); service.setCorrDate(new Date(System.currentTimeMillis())); service.set ... other not-null fields. State.hbm.xml's <id property is using unsaved-value="any", if you remove that attribute everything works fine, but it will fire a SELECT SQL to the STATE table, to verify the integrity of the <id>. We had explicitly mentioned the unsaved-value="any", in order to prevent the SELECT being fired. Ironicall I found out that when you make unsaved-value="none", everything works perfectly, but then unsaved-value is having this unpredictable behaviour about it's value. We are using unsaved-value attribute for all <id, <composite-id which has <generated-class as "assigned", the values are like below <id unsaved-value="id_value" - id is a String <id unsaved-value="none" - id is a Integer <composite-id unsaved-value="any" For composite-id everywhere we used, unsaved-value="any", the only contradicting place where we found is with State.hbm.xml If possible please provide some guidelines as to use the "unsaved-value", we mainly used that to prevent the SELECT SQLs from executing before performing INSERT. Also while debugging through the hibernate code, I found that it is performing dirtyCheck for EventService instance, where it compares loaded value and current value. I found that loaded value was having State object as null. Please provde your comments. I have also attached the test cases, but you wont able to run it, due to compilation problems, testAddEvent is the one which is failing -- 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

16 years

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Gail Badner commented on HHH-1501: ---------------------------------- Please try using 3.5.1 and map your property as a materialized_clob like: <property name="longString" column="LONG_STR" type="materialized_clob" length="MAX_LENGTH"/> Replace MAX_LENGTH with the actual maximum length for the string. The Hibernate type, "materialized_clob", is new for 3.5 (HHH-3892/HHH-4405) and has not been documented yet. Documentation will added for HHH-4878. (That's on my TODO list...) If "materialized_clob" doesn't work, then please attach a test case that reproduces your issue. You may be able to update a test in https://anonsvn.jboss.org/repos/hibernate/core/trunk/testsuite/src/test/j... to reproduce your issue. If you need to change the Derby dialect to get this to work, please attach a patched version of the Derby dialect as well. Thanks, Gail > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5164) HQL putting quotes around SMALLINT field

by Shawn Kuenzler (JIRA)

HQL putting quotes around SMALLINT field ---------------------------------------- Key: HHH-5164 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5164 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1 using org.hibernate.dialect.DB2Dialect against DB2 v9.1 Reporter: Shawn Kuenzler HQL query generating a WHERE clause with a mapped column of java type "int" and datatype "SMALLINT" in DB2. The generated prepared statement inside of AbstractBatcher.class shows single quotes around the value (i.e. '11'). DB2 complains with a "SQL0401N The data types of the operands for the operation "=" are not compatible." error. Running the query in the DB2 Command Center I see it just needs the quotes removed. I see that in SQLServer 2008, where the same legacy database field has a datatype of "TINYINT", SQLServer is accepting of the single quoted value in the HQL statement. -- 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

16 years

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5193) Can't use date as field name

by Douglas Ferguson (JIRA)

Can't use date as field name ---------------------------- Key: HHH-5193 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5193 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.1 Environment: Hibernate 3.5.1, Mysql Reporter: Douglas Ferguson We just upgrade to 3.5.1-Final and we had to rename several of our columns from date. We trying using @Column(name="\"date\"") as we saw in some forum posts but this did not work. It was complaining about a ambiguous reference to date. -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-518) pom.xml misses pluginrepository

by Marc Schipperheyn (JIRA)

pom.xml misses pluginrepository ------------------------------- Key: HSEARCH-518 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-518 Project: Hibernate Search Issue Type: Bug Components: build Affects Versions: 3.2.0.CR1 Reporter: Marc Schipperheyn Priority: Minor the pom.xml for Hibernate search misses a dependency for the maven-jdocbook-plugin. <pluginRepositories> <pluginRepository> <id>repository.jboss.org</id> <name>JBoss Maven Repository</name> <url>http://repository.jboss.org/maven2</url> <layout>default</layout> </pluginRepository> </pluginRepositories> I also added <repositories> <repository> <id>repository.jboss.org</id> <name>JBoss Maven Repository</name> <url>http://repository.jboss.org/maven2</url> <layout>default</layout> </repository> </repositories> for good measure. Presumably this dependency is supplied by the password protected distributionManagement key. In any case, it doesn't compile out of the box without this addition. -- 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

16 years

4
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-503) Generated archetype broken for any package name with dot (.)

by G Fernandes (JIRA)

Generated archetype broken for any package name with dot (.) ------------------------------------------------------------ Key: HSEARCH-503 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-503 Project: Hibernate Search Issue Type: Patch Components: build Affects Versions: 3.2.0.Beta1 Reporter: G Fernandes Priority: Minor Steps to reproduce: ===================== $ cd hibernate-search-archetype $ mvn archetype:create-from-project -Darchetype.properties=src/main/archetype/archetype.properties ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4 seconds [INFO] Finished at: Sat Apr 10 20:35:58 BST 2010 [INFO] Final Memory: 16M/80M [INFO] ------------------------------------------------------------------------ $ cd target/generate-sources/archetype $ mvn install ... [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 3 seconds [INFO] Finished at: Sat Apr 10 20:36:50 BST 2010 [INFO] Final Memory: 18M/80M [INFO] ------------------------------------------------------------------------ $ cd ~/temp $ mvn archetype:generate -DarchetypeGroupId=org.hibernate -DarchetypeArtifactId=hibernate-search-quickstart -DarchetypeVersion=3.2.0-SNAPSHOT -DgroupId=my.company -DartifactId=quickstart -Dversion=1.0-SNAPSHOT ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5 seconds [INFO] Finished at: Sat Apr 10 20:39:17 BST 2010 [INFO] Final Memory: 13M/79M [INFO] ------------------------------------------------------------------------ $ cd quickstart $ mvn install [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[25,11] ';' expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[37,10] '.' expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[37,11] ';' expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[37,19] class, interface, or enum expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[37,20] class, interface, or enum expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Author.java:[25,11] ';' expected -- 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

16 years

4
21
0 / 0

[Hibernate-JIRA] Created: (HHH-4909) Null Pointer Exception When Usding Spring 3.0 with Hibernate 3.5.0-Beta-x

by Petar Tahchiev (JIRA)

Null Pointer Exception When Usding Spring 3.0 with Hibernate 3.5.0-Beta-x ------------------------------------------------------------------------- Key: HHH-4909 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4909 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1 Environment: Java, 1.6, Spring 3.0.0 (tested also with 3.0.1.SNAPSHOT) Reporter: Petar Tahchiev Priority: Critical Attachments: stacktrace.txt Hi guys, I had an application working fine with OpenJPA, but I decided to migrate to Hibernate and I get a Null pointer exception (see the attached stacktrace). Let me know if you need some other info. My configuration is below: persistence.xml: =========================================== =========================================== <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="frontend-ui"> <class>com.fugsley.beech.betting.db.model.User</class> .........[more here]...................  <properties>    <property name="c3p0.acquire_increment" value="1"/> <property name="c3p0.idle_test_period" value="100"/>  <property name="c3p0.min_size" value="5"/> <property name="c3p0.max_size" value="20"/> <property name="c3p0.timeout" value="1800"/> <property name="c3p0.max_statements" value="50"/>  <property name="hibernate.archive.autodetection" value="class, hbm"/> <property name="hibernate.show_sql" value="false"/> <property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/> <property name="hibernate.connection.password" value="r00tka"/> <property name="hibernate.connection.url" value="jdbc:mysql://localhost:3306/fugsley?useUnicode=true&characterEncoding=UTF-8"/> <property name="hibernate.connection.username" value="fugsley"/> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/> <property name="hibernate.c3p0.min_size" value="5"/> <property name="hibernate.c3p0.max_size" value="20"/> <property name="hibernate.c3p0.timeout" value="300"/> <property name="hibernate.c3p0.max_statements" value="50"/> <property name="hibernate.c3p0.idle_test_period" value="3000"/> </properties> </persistence-unit> </persistence> ===============spring-application-context=========================== <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> <property name="loadTimeWeaver"> <bean class="org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver" /> </property> <property name="dataSource" ref="beechDataSource" /> <property name="jpaVendorAdapter"> <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"> <property name="database" value="Mysql" /> <property name="showSql" value="false" /> </bean> </property> </bean> -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-463) Merging of one-to-many relations not JPA spec compliant for lazy relations

by Dirk (JIRA)

Merging of one-to-many relations not JPA spec compliant for lazy relations -------------------------------------------------------------------------- Key: EJB-463 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-463 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate 3.2.6, Hibernate EntityManager 3.4.0, Hibernate Annotations 3.4.0, Oracle Reporter: Dirk Attachments: CascadeTest.zip Topic has been posted to the Hibernate Forum. See https://forum.hibernate.org/viewtopic.php?f=1&t=999398 Summary: Suppose you have an object Master with one-to-many relation to Detail. @Entity public class Master implements Serializable { @OneToMany(mappedBy = "master", cascade={CascadeType.MERGE, CascadeType.PERSIST}) private List<Detail> details = new ArrayList<Detail>(); ... } Master is loaded without fetching Detail (= lazy) and EntityManager is closed. Master is now in detached state. Merging Master causes Hibernate EntityManager to eagerly load the Detail collection although it is in lazy state. This is not JPA spec compliant. JPA spec states: The persistence provider must not merge fields marked LAZY that have not been fetched: it must ignore such fields when merging. See 3.2.4.1 Merging Detached Entity State, p.51. Tested also with the latest version of EclipseLink. EclipseLink behaves as expected. Testcase attached (Netbeans 6.7). -- 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

16 years

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-333) Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId

by Hardy Ferentschik (JIRA)

Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId ------------------------------------------------------------------------------- Key: HSEARCH-333 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-333 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.1.1 http://forum.hibernate.org/viewtopic.php?t=993097 -- 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

16 years

3
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-486) Review the getting started section's pom and archetype creation

by Emmanuel Bernard (JIRA)

Review the getting started section's pom and archetype creation --------------------------------------------------------------- Key: HSEARCH-486 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-486 Project: Hibernate Search Issue Type: Task Components: documentation Affects Versions: 3.2.0.Beta1 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 3.2.0 HSEARCH-428 has been done but a second polish is likely required. -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-522) Search only compiles against JDK 6 with the current version of JGroups

by Hardy Ferentschik (JIRA)

Search only compiles against JDK 6 with the current version of JGroups ----------------------------------------------------------------------- Key: HSEARCH-522 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-522 Project: Hibernate Search Issue Type: Bug Reporter: Hardy Ferentschik Fix For: 3.2.0 JGroups 2.9.0.GA seems to be compiled only for Java 6. First step is to find out whether this was intentionally. If so we need to decide whether we go Java 6 with Search as well. Given that Core is still Java 5 it seems to be best to align and stay with Java 5 until Core switches as well. A solution to the problem would be in this case to have a jgroups module which uses Java 6 (similar to Core and em) -- 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

16 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-519) Update JGroups dependencies

by Sanne Grinovero (JIRA)

Update JGroups dependencies --------------------------- Key: HSEARCH-519 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-519 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.2.0.CR1, 3.2.0.Beta1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 3.2.0 -- 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

16 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-515) Lucene AlreadyClosedExceptions During Batch Processing With ASYNC Workers

by j nadler (JIRA)

Lucene AlreadyClosedExceptions During Batch Processing With ASYNC Workers ------------------------------------------------------------------------- Key: HSEARCH-515 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-515 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.CR1 Reporter: j nadler We have a batch job that updates 10,000 preexisting User entities in a single transaction; each User has an @IndexedEmbedded UserDetails entity which is also updated during the job run. When run with hibernate.search.worker.execution=sync, life is good. When we run with async, indexing intermittently fails with a Lucene AlreadyClosedException. There is no other exception logged even with TRACE logging enabled. We did not see this issue with 3.1.1GA but Sanne has noted that it is possible the exceptions were occurring and were not being logged in that version; I cannot exclude this possibility. Posted a log file to http://www.attensa.com/download/files/attensa.log the first exception is at timestamp [2010-04-21 11:23:45.992,236829] Associated forum discussion here: https://forum.hibernate.org/viewtopic.php?f=9&t=1004022&p=2429214#p2429214 -- 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

16 years

3
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-506) Suggest dependency to core 3.5.1

by Sanne Grinovero (JIRA)

Suggest dependency to core 3.5.1 -------------------------------- Key: HSEARCH-506 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-506 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0 The release pom should suggest a dependency to core version 3.5.1 , but it would be nice to start defining support for ranges of versions. I'd propose something like {{<version>[3.5.0,3.6.0)</version>}} but have to try to see how this interacts with the {{.FINAL}} postfix -- 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

16 years

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-512) Associate with two open session issue and subsequent hang

by Marc Schipperheyn (JIRA)

Associate with two open session issue and subsequent hang --------------------------------------------------------- Key: HSEARCH-512 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-512 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.CR1 Environment: Hibernate 3.5.1, MySQL 5.1.44, Lucene 2.9.2 Reporter: Marc Schipperheyn I've noticed the issue described in http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-490. It seems to happen sometimes, especially when threads pause for a debugging break and I don't immediately continue them. But I also notice that then the MassIndexer just doesn't finish and hangs with all the threads still in running state. Nothing seems to be happening or completing. I think that HSEARCH-490 has prevented the threads from completing at this point. The system/website then becomes completely unresponsive. -- 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

16 years

2
16
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 May 2010