February 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-336) When defining a many-to-many relationship with an association table , SchemaExport does not create a composite primary key (or unique key) on the columns that make up the association.

by Gulshan (JIRA)

When defining a many-to-many relationship with an association table , SchemaExport does not create a composite primary key (or unique key) on the columns that make up the association. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EJB-336 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-336 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.2.0.ga Environment: tomcat 5.5 Reporter: Gulshan When defining a many-to-many relationship with an association table (see example below), SchemaExport does not create a composite primary key (or unique key) on the columns that make up the association. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-144) add option to keep indexer running till finished.

by Jason Eacott (JIRA)

add option to keep indexer running till finished. ------------------------------------------------- Key: HSEARCH-144 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-144 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Jason Eacott Hi all, I've just installed and got running hibernate search - very cool! But a very minor enancement would help a lot I think, for those of us still in testing mode and not using the jms option yet. It would be very handy if there was a config option for the async executorService to stay up and complete its tasks after the app itself has been shutdown. In BatchedQueueingProcessor finalize just need to add something like this line after the executorService.shutdown();( if its set to wait in the config somewhere of course), or even better replace the params here with user defined entries from config. executorService.awaitTermination(Long.MAX_VALUE, TimeUnit.SECONDS ); The only other feature I'd like is the capability to use Spring jms instead of the jboss one out of the box. :) Great product. Cheers Jason. -- 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, 10 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-127) Wrong prefix for worker configurations.

by Jay Bose (JIRA)

Wrong prefix for worker configurations. --------------------------------------- Key: HSEARCH-127 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-127 Project: Hibernate Search Issue Type: Improvement Components: documentation Affects Versions: 3.0.0.GA Environment: online here - http://www.hibernate.org/hib_docs/search/reference/en/html/search-configu... Reporter: Jay Bose Priority: Minor In Table 3.2. worker configurations are all prefixed with "org.hibernate.", when it should be "hibernate.search." -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Deleted: (HHH-3103) move to java.util.ConcurrentHashMap for EntityModeToTuplizerMapping with move to JDK5

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3103?page=c... ] Steve Ebersole deleted HHH-3103: -------------------------------- > move to java.util.ConcurrentHashMap for EntityModeToTuplizerMapping with move to JDK5 > ------------------------------------------------------------------------------------- > > Key: HHH-3103 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3103 > Project: Hibernate3 > Issue Type: Sub-task > Reporter: Steve Ebersole > Assignee: Steve Ebersole > > See HHH-2645 for the discussion -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-52) Hibernate Shards not applying setMaxResults as a SQL LIMIT

by Max Ross (JIRA)

Hibernate Shards not applying setMaxResults as a SQL LIMIT ---------------------------------------------------------- Key: HSHARDS-52 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-52 Project: Hibernate Shards Issue Type: Bug Components: engine Reporter: Max Ross Assignee: Max Ross Fix For: 3.0.0 http://forum.hibernate.org/viewtopic.php?p=2374359&sid=b337277456949beac5... -- 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, 10 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3100) Hibernate Fails on More Than One VARCHAR2(4000) Property

by James Carman (JIRA)

Hibernate Fails on More Than One VARCHAR2(4000) Property -------------------------------------------------------- Key: HHH-3100 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3100 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Java Version: java version "1.5.0_14" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03) Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode, sharing) Hibernate Version: 3.2.5.ga Oracle Database Version: Oracle, version: Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.4.0 - Production Oracle Driver Version: Oracle JDBC driver, version: 10.2.0.3.0 Reporter: James Carman If I have more than one long string (mapped to a varchar2(4000) column) within my entity class, Hibernate fails with: "java.sql.BatchUpdateException: ORA-01461: can bind a LONG value only for insert into a LONG column" My class looks like (Entity is a superclass that defines the id, equals, hashCode): public class TwoString extends Entity { private String string1; private String string2; public TwoString() { } public TwoString( String string1, String string2 ) { this.string1 = string1; this.string2 = string2; } // Getters and setters here... } My mapping document looks like: <hibernate-mapping> <class name="com.carmanconsulting.hibernate.bug.TwoString" table="HHH_BUG_TWO_STRING"> <id name="id"> <generator class="assigned" /> </id> <property name="string1" length="4000" /> <property name="string2" length="4000" /> </class> </hibernate-mapping> My code looks like: Configuration cfg = new Configuration(); SessionFactory sf = cfg.configure().buildSessionFactory(); Session s = sf.openSession(); try { Transaction tx = s.beginTransaction(); s.save(new TwoString(repeat('Y', 3999), repeat('Z', 3999))); tx.commit(); } finally { s.close(); sf.close(); } -- 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, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3106) Provide Common Superinterface for Query and Criteria

by James Carman (JIRA)

Provide Common Superinterface for Query and Criteria ---------------------------------------------------- Key: HHH-3106 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3106 Project: Hibernate3 Issue Type: Improvement Reporter: James Carman Priority: Minor It would be nice if the Query and Criteria interfaces both extended a common superinterface that looked something like this (I don't know about the name, but you get the idea): public interface QueryResultsProvider { List list(); ScrollableResult scroll(); ScrollableResult scroll(ScrollMode mode); Object uniqueResult(); } This way, if I wanted to write a framework that does something with Hibernate query results, I don't have to write two flavors of it. Does this sound reasonable? -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3105) Unable to use TYPE element under INDEX element

by Michael Fork (JIRA)

Unable to use TYPE element under INDEX element ---------------------------------------------- Key: HHH-3105 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3105 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: Hibernate-Version: 3.2.6.ga Reporter: Michael Fork Similar to HHH-1470 except on the INDEX element: i.e. change <!ELEMENT index (column*) > to <!ELEMENT index ((column*), type?)> When making that change in the DTD and rebuilding the JAR file, everything appears to work fine. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1296) Non lazy loaded List updates done in wrong order, cause exception

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1296?page=c... ] Gail Badner commented on HHH-1296: ---------------------------------- The original issue here does not duplicate HHH-1268. It involves a column other than the parent ID and position that is *required* to be part of the primary key or have a unique constraint. Using a SortedSet is the appropriate collection type (http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#collection...) for this requirement. The rest of the comments describe the same issue as in HHH-1268. > Non lazy loaded List updates done in wrong order, cause exception > ----------------------------------------------------------------- > > Key: HHH-1296 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1296 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5 - any database (checked postgres 7/8, mysql 4 & 5, db2 v8) > NOT using lazy loading - the tx's are wrapped by session beans, so lazy loading is not allowed. > Reporter: David Birch > Assignee: Diego Pires Plentz > Priority: Critical > Attachments: listupdate_patch.txt, listupdate_patch.txt, listupdate_testcase.zip > > > The logic behind list updates is not quite right, nor was it in v2 (only now i have a DBA who won't let up...) > The scenario is: > a bean with list property, and the list has a number of items in it (say 4, index 0-3), an item is then removed (say item at index 2), and the bean is requested to be saved. > From what i can see in the SQL traces, the same statements are issues whe lazy loading is on or off, they are: > [18/12/05 19:48:50:766 EST] 00000036 SystemOut O Hibernate: delete from TGE_CLIENT_POLICY where CLIENT_ID=? and POSITION=? > [18/12/05 19:48:50:766 EST] 00000036 SystemOut O Hibernate: update TGE_CLIENT_POLICY set POLICY_NK=? where CLIENT_ID=? and POSITION=? > So, i can only assume (as when this fails, the row with index 1 above the removed row is nuked!), hibernate removes the item at index 3, and then copies the value of the item at index 3 onto the row for item at index 2. Fair enough but... > When i have lazy loading off, i get DB exceptions like > Duplicate key or integrity constraint violation message from server: "Duplicate entry '1-999999' for key 1" > so, there is some nasty in there, which is not updating the correct row - this has happened since 2.1.8 that i know of :( > i will try & look @ the source, but won't get a chance until after xmas... -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-1041) Hibernate Plugin for Eclipse does not work

by Timur Shakirov (JIRA)

Hibernate Plugin for Eclipse does not work ------------------------------------------ Key: HBX-1041 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1041 Project: Hibernate Tools Issue Type: Bug Components: eclipse Affects Versions: 3.2.0.GA Environment: Win2000, Eclipse SDK Version: 3.3.1.1 Build id: M20071023-1652 Reporter: Timur Shakirov I tried to use Hibernate-Tools with the Eclipse 3.3.1. I downloaded the current release of Eclipse 3.3.1.1 and installed Hibernate-Tools 3.2.0.GA. After starting Eclipse I noticed that no Eclipse-Views of Hibernate-Tools are available, but the Hibernate plugin is visible under the 'Product Configuration' window. This is exactly the same problem as it was reported in the issue HBX-960 (and even reported as closed in 3.2beta10). The only difference is that I use now EclipseTools version 3.2.0 GA from JBossTools 2.0.0.GA (2007-12-10 23:33) and Eclipse 3.3.1.1 This is the output of the osgi console: -----------------8<---------------------------- osgi> start org.hibernate.eclipse.mapper org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Mi ssing Constraint: Require-Bundle: org.eclipse.wst.xml.core; bundle-version="0.0. 0" at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:260) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:252) at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st art(FrameworkCommandProvider.java:260) 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 org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter. execute(FrameworkCommandInterpreter.java:150) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F rameworkConsole.java:291) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra meworkConsole.java:276) at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo rkConsole.java:218) at java.lang.Thread.run(Unknown Source) osgi> -----------------8<---------------------------- Should I still have WTP package installed to use HibernateTools on Eclipse? -- 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, 10 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2008