February 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4635) Oracle ORA-24816 inserting and updating data for entities containg LOB attributes

by Clay Atkins (JIRA)

Oracle ORA-24816 inserting and updating data for entities containg LOB attributes --------------------------------------------------------------------------------- Key: HHH-4635 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4635 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Clay Atkins Priority: Critical Inserting or updating an entity with LOB results in the following error from oracle: {noformat} Caused by: java.sql.SQLException: ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column {noformat} Fairly confident that the ordering of the LOB attributes is not putting them at the end of the insert or the update. Oracle requires all LOB columns to be the last in the 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

12 years, 3 months

9
23
0 / 0

[Hibernate-JIRA] Created: (HBX-978) unique=true attribute of primary key in generated class prevents the schema to be regenerated

by Ali Sadik Kumlali (JIRA)

unique=true attribute of primary key in generated class prevents the schema to be regenerated --------------------------------------------------------------------------------------------- Key: HBX-978 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-978 Project: Hibernate Tools Issue Type: Bug Environment: OS: Windows Vista 6.0,x86 Database: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc. Eclipse Europa: Version: 3.3.0 Build id: I20070621-1340 HibernateTools-3.2.0.beta10 Reporter: Ali Sadik Kumlali Priority: Minor Hi, When I reverse engineer against Oracle, unique=true attribute is added to @Column annotation of primary key column. But, when I generate schema from these generated files, Oracle throws "ORA-02261: such unique or primary key already exists in the table" error. I first ran into this situation while trying Seam and posted the problem to Seam's forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116478. After I got the response, decided to try it without Seam. Then, downloaded the latest HibernateTools & Eclipse Europa and reverse engineered the schema. I saw that generated classes have unique=true attribute which clearly showed that the problem was related with HibernateTools, not with Seam. Here is the DDL of the table against which I made my test: CREATE TABLE PEOPLE ("ID" NUMBER NOT NULL, "SURNAME" VARCHAR2(50 BYTE), "NAME" VARCHAR2(25 BYTE), CONSTRAINT "PEOPLE_PK" PRIMARY KEY ("ID")); Regards, Ali Sadik Kumlali -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3135) SQL Server Dialect maps BIGINT to NUMERIC(19,0)

by Dominik Enkelmann (JIRA)

SQL Server Dialect maps BIGINT to NUMERIC(19,0) ----------------------------------------------- Key: HHH-3135 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3135 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: MS SQL Server Reporter: Dominik Enkelmann Priority: Trivial The SQLServerDialect.java maps the Hibernate BIGINT type to a NUMERIC(19,0) colum. The result is, that all Long fields in persisten classes map to hibernate-bigints which generate numeric(19,0) database column. Longs are typically used for surrogate primary keys and should be implemented as native SQL BIGINTs where possible. SQL Server supports SQL BIGINT since version 2000. There is a similar issue with the SQL BIT type that should be implemented as a native BIT column in SQL Server. A possible solution could be a pre-.SQL Server 2000 dialect and an updated SQL Server dialect. I filed a more detailed description with workaround in the user forum http://forum.hibernate.org/viewtopic.php?p=2377674#2377674 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2942) Improve support for PostgreSQL

by Diego Pires Plentz (JIRA)

Improve support for PostgreSQL ------------------------------ Key: HHH-2942 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2942 Project: Hibernate3 Issue Type: Improvement Components: metamodel Reporter: Diego Pires Plentz Assignee: Diego Pires Plentz Priority: Minor Improve support for features in PostgreSQL 7.x and 8.x. I will probably create a new one for 8.x series. I asked for help of postgresql hackers. http://archives.postgresql.org/pgsql-hackers/2007-11/threads.php#00462 Docs index: http://www.postgresql.org/docs/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
5
0 / 0

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

by Max Rydahl Andersen (JIRA)

H2MetaDataDialect for identity detection ---------------------------------------- Key: HBX-935 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-935 Project: Hibernate Tools Issue Type: Sub-task Components: reverse-engineer Affects Versions: 3.2beta9 Reporter: Max Rydahl Andersen Fix For: 3.2beta10 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
15
0 / 0

[Hibernate-JIRA] Created: (HHH-4751) Fix for @embeddedid error: Type not supported: org.hibernate.type.ManyToOneType

by David Coleman (JIRA)

Fix for @embeddedid error: Type not supported: org.hibernate.type.ManyToOneType -------------------------------------------------------------------------------- Key: HHH-4751 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4751 Project: Hibernate Core Issue Type: Improvement Components: envers Reporter: David Coleman Priority: Minor Attachments: IDMetadataGenerator_patch.txt Hi, After creating hibernate entities from the legacy database with envers hibernate tool, I noticed the following error occurred on creating an audit tables that has an @EmbeddedId attribute (related to ENVERS-76]: Caused by: org.hibernate.MappingException: Type not supported: org.hibernate.type.ManyToOneType .. I found out by looking at the source that the reason it failed was that the property type was not an instance of ImmutableType (not mutable); which was true as the embedded id was a combination of an int and a mutable java data object. I switched the mutable java date object to a immutable joda datetime object using the joda date time hibernate user type to fix the immutable problem. I also patched IdMetadataGenerator locally to the one attached as hibernate usertypes do not implement the ImmutableType interface; using the method 'isMutable()' should be suffice. Let me know if this is okay so I can submit the patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

7
29
0 / 0

[Hibernate-JIRA] Created: (HHH-4468) Exception when using hibernate as JPA provider: "Found two representations of same collection"

by Håvard Nesvold (JIRA)

Exception when using hibernate as JPA provider: "Found two representations of same collection" ---------------------------------------------------------------------------------------------- Key: HHH-4468 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4468 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.3.2 Environment: 3.3.2.GA Reporter: Håvard Nesvold I have a J2SE application where I use JPA with Hibernate as persistence provider. The versions of the required hibernate jars that I use are: hibernate3.jar (3.3.2.GA) hibernate-annotations.jar (3.4.0.GA) hibernate-commons-annotations.jar (3.1.0.GA) hibernate-entitymanager.jar (3.4.0.GA) I have an entity where i have a bidirectional One-To-Many mapping. This is initialized to an empty list, something that clearly is allowed according to the JPA 1.0 spec. i.e. I have: in class Parent: @OneToMany(mappedBy="parent", cascade = CascadeType.ALL) private List<Child> children = ArrayList<Child>(); class Child: @ManyToOne @JoinColumn(name="PARENT_ID") private Parent parent; A certain sequence of actions result in a HibernateException being thrown (wrapped by JPA in a RollbackException): * Obtain a new EntityManager * Begin a transaction * Fetch a Parent entity from the entity manager (this exists in the db), call this e. * Apply an EntityManager.remove() on e * Commit the transaction * Begin a transaction * Apply an EntityManager.persist() on e * Commit the transaction The exception is thrown on the last commit(): Code: Caused by: org.hibernate.HibernateException: Found two representations of same collection: Parent.children at org.hibernate.engine.Collections.processReachableCollection(Collections.java:176) at org.hibernate.event.def.FlushVisitor.processCollection(FlushVisitor.java:60) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:124) ... I have tried to flush(), clear(), and pretty much everything on the entity manager (event fetching the Hibernate Sesssion and clearing this) - the only thing that helps is creating a new one before attempting the last transaction. Moreover, after some investigation, the persisted entity actually seems to be persisted correctly - despite the exception (this also seems to hold true for any cascaded persists), perhaps the only erroneous thing here is the fact that an exception is thrown when it really should not? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
7
0 / 0

[Hibernate-JIRA] Created: (ANN-808) @Enumerated(ORDINAL) does not work on VARCHAR columns

by Eduardo Costa (JIRA)

@Enumerated(ORDINAL) does not work on VARCHAR columns ----------------------------------------------------- Key: ANN-808 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-808 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Tested on Postgres, but the problem should be reproductible on any DB vendor Reporter: Eduardo Costa Copied from http://forum.hibernate.org/viewtopic.php?t=995698: ========== Suppose I have this enum: public enum Status { OK, NOK, NOT_APPLICABLE } And this property: @Column(name = "status") @Enumerated(EnumType.ORDINAL) private Status status; And this table (legacy, CANNOT be changed): CREATE TABLE tb_xxx ( id bigint NOT NULL, status character varying(1) NOT NULL, ) It leads to this exception: java.lang.IllegalArgumentException: No enum const class mypkg.Status.1 java.lang.Enum.valueOf(Enum.java:196) org.hibernate.type.EnumType.nullSafeGet(EnumType.java:110) Taking a look at EnumType.java, it is clear that Hibernate imposes ordinal stored as number and name stored as varchar. ========= IMHO, this is a "specification gap": JPA does not consider what to do if I'm trying to map a legacy enumerated value. Since I'm defining @Enumerated as "ordinal" and I have "0", "1", "2" on my database, I believe Hibernate should consider what I'm defining, not what an ancient DBA defined. Otherwise, I can't map this using only Hibernate Annotations/JPA (BTW, this code works with TopLink, only changing JPA provider on persistence.xml) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3809) Improve Memory Management when Post Commit Listeners are enabled

by Shawn Clowater (JIRA)

Improve Memory Management when Post Commit Listeners are enabled ---------------------------------------------------------------- Key: HHH-3809 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3809 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.1 Environment: N/A Reporter: Shawn Clowater This is somewhat related to the QueryCache behavior reported under http://opensource.atlassian.com/projects/hibernate/browse/HHH-3028 In this particular case however, it is the fact that when the session factory is configured to have post commit listeners it prevents the garbage collection of any entity that is modified during the session due to the fact that it is referenced in the executions list in the ActionQueue class. This makes any type of memory management by flushing/clearing the session ineffective if you're in the middle of a large batch that is inserting or updating a large amount of data. i.e in our case we have 4 entities out of possibly 300 or so that we want to notify external systems if they change. However, by simply having the listeners defined they essentially block the remaining entities in the executions. A potential workaround I guess might be to keep 2 session factories around with a different set of listeners but that seems a bit dirty. There are 2.5 potential ways that I can think of that might address this. 1 - Have some sort of flag on the session to disable the post commit listeners. The onus would be on the user of the session to disable the listeners in the case where they know they aren't modifying anything that will need post commit handling. 2 - Add the ability to configure the post commit listeners by entity a)With polymorphism - i.e. you could add a listener based on Object.class and it would apply to all entities and would behave much like it does now. You could also configure to Animal.class and would include Cat and Dog. b)Without polymorphism - you could add a listener based on a specific entity class and it would only apply to that particular one. You would have an option to specify a null entity and it would default to what is there today. In my miind, 2a is probably the best albeit slightly more complex to implement but I think would be a good value add. I don't mind submitting a patch assuming that I'm not so far in left field that I should be committed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
20
0 / 0

[Hibernate-JIRA] Created: (HHH-2770) Action observers for event listeners

by Christian Bauer (JIRA)

Action observers for event listeners ------------------------------------ Key: HHH-2770 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2770 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Christian Bauer Priority: Minor Talked to Steve about a feature he calls "action observers", which would allow the following use case: - Write a FlushEventListener - Observer for what has been deleted, inserted, updated (action queues) This removes some of the pain that comes from missing communication between listeners. For example, you can easily move code you would traditionally write in an Interceptor into a FlushEventListener if you only need inserted/deleted/udpated records. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2010