September 2007 - hibernate-issues

[Hibernate-JIRA] Updated: (HHH-1483) MySQL5: No Dialect mapping for JDBC type: -1

by Christian Bauer (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1483?page=c... ] Christian Bauer updated HHH-1483: --------------------------------- Comment: was deleted > MySQL5: No Dialect mapping for JDBC type: -1 > -------------------------------------------- > > Key: HHH-1483 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1483 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1.2 > Environment: MySQL 5.0.18-nt > Reporter: Sergey Vladimirov > Priority: Minor > > MySQL5: No Dialect mapping for JDBC type: -1 > SELECT answpos,answer FROM votes_answers WHERE question=? ORDER BY answpos > mysql> describe votes_answers; > +----------+---------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +----------+---------+------+-----+---------+-------+ > | question | int(11) | NO | MUL | | | > | answpos | int(11) | NO | | | | > | answer | text | YES | | NULL | | > +----------+---------+------+-----+---------+-------+ > mysql> describe temp; > +---------+---------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +---------+---------+------+-----+---------+-------+ > | answpos | int(11) | NO | | 0 | | > | answer | text | YES | | NULL | | > +---------+---------+------+-----+---------+-------+ > Please, let me know what to add to MySQL5Dialect :) > Will it be ok to add? : > registerColumnType( Types.LONGVARCHAR, "text" ); -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2848) org.hibernate.MappingException: No Dialect mapping for JDBC type: -1

by Raghuveer Rawat (JIRA)

org.hibernate.MappingException: No Dialect mapping for JDBC type: -1 -------------------------------------------------------------------- Key: HHH-2848 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2848 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: MySQL 5.1, Hibernate 3.2.5 Reporter: Raghuveer Rawat Priority: Blocker Create a table Demo in MySQL 5.1 and define a field TestText with Text Data Type. Now write a Native SQL for retriving table columns including this Text Column. Use below mapping in .hbm.xml <property name="testText" type="text"> <column name="TestText" length="16777215" not-null="true"> <comment></comment> </column> </property> Hibernate throws exception on execution... org.hibernate.MappingException: No Dialect mapping for JDBC type: -1 There is a similar long pending bug HHH:1483 with Low Priority but issue is very critical in nature. Looking forward for this fix asap. -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1483) MySQL5: No Dialect mapping for JDBC type: -1

by Raghuveer Rawat (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1483?page=c... ] Raghuveer Rawat commented on HHH-1483: -------------------------------------- I too is facing this issue for MySQL native SQL for Text data type. I am using org.hibernate.dialect.MySQLMyISAMDialect dialect. This is very critical issue for our application. Priority of this bug need to be changed to high. Looking forward for some prompt action from Hibernate Team. > MySQL5: No Dialect mapping for JDBC type: -1 > -------------------------------------------- > > Key: HHH-1483 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1483 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1.2 > Environment: MySQL 5.0.18-nt > Reporter: Sergey Vladimirov > Priority: Minor > > MySQL5: No Dialect mapping for JDBC type: -1 > SELECT answpos,answer FROM votes_answers WHERE question=? ORDER BY answpos > mysql> describe votes_answers; > +----------+---------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +----------+---------+------+-----+---------+-------+ > | question | int(11) | NO | MUL | | | > | answpos | int(11) | NO | | | | > | answer | text | YES | | NULL | | > +----------+---------+------+-----+---------+-------+ > mysql> describe temp; > +---------+---------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +---------+---------+------+-----+---------+-------+ > | answpos | int(11) | NO | | 0 | | > | answer | text | YES | | NULL | | > +---------+---------+------+-----+---------+-------+ > Please, let me know what to add to MySQL5Dialect :) > Will it be ok to add? : > registerColumnType( Types.LONGVARCHAR, "text" ); -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2846) Earlier NullPointerException in AbstractPersistentCollection

by Elliotte Rusty Harold (JIRA)

Earlier NullPointerException in AbstractPersistentCollection ------------------------------------------------------------ Key: HHH-2846 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2846 Project: Hibernate3 Issue Type: Improvement Components: core Environment: 3.2.5+ Reporter: Elliotte Rusty Harold Priority: Minor I'm currently tracking down a bug in either my code or Hibernate (don't know which yet) that seems to relate to null sessions in org.hibernate.collection.AbstractPersistentCollection. It would be helpful if this class threw the exception earlier when the session is first set to null rather than at some later point. In particular, I would like to see a null check in the constructor and setCurrentSession. Something like this: public final boolean setCurrentSession(SessionImplementor session) throws HibernateException { if (session==this.session) { return false; } else if (session == null) { throw new NullPointerException("null session"); } ... Possibly it should throw a HibernateException instead of NullPointerException, but I'd definitely like the exception to come up sooner rather than later. Browsing the code, I don't think a null session is ever legal here. The one place there is a check is in forceInitialization which is where my code is throwing its exception: public final void forceInitialization() throws HibernateException { if (!initialized) { if (initializing) { throw new AssertionFailure("force initialize loading collection"); } if (session==null) { throw new HibernateException("collection is not associated with any session"); } However it seems that at this point the real bug has already happened. This is just a symptom. -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-29) Hibernate Commons Annotations source seems to have no dependency to hibernate-core and persistence-api but the readme.txt and the maven-pom claims this dependencies are required

by Chris W. (JIRA)

Hibernate Commons Annotations source seems to have no dependency to hibernate-core and persistence-api but the readme.txt and the maven-pom claims this dependencies are required --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HV-29 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-29 Project: Hibernate Validator Issue Type: Bug Affects Versions: 3.0.0.ga Reporter: Chris W. Hibernate Commons Annotations source seems to have no dependency to hibernate-core and persistence-api but the readme.txt and the maven-pom claims this dependencies are required. I have analyzed the source code and found no dependencies to either hibernate-core or persistence-api. Readme.txt in hibernate-validator-3.0.0.GA.zip\hibernate-validator-3.0.0.GA\lib: Hibernate Commons Annotations dependencies ========================================== Core ==== hibernate-commons-annotations.jar: required hibernate3.jar: required hibernate core dependencies: required (see Hibernate Core for more information) ejb3-persistence.jar: optional (needed for Java Persistence integration) Test ==== hibernate-annotations.jar: required hibernate-entitymanager.jar: required Maven POM at http://repo1.maven.org/maven2/org/hibernate/hibernate-commons-annotations...: <dependencies> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate</artifactId> <version>3.2.1.ga</version> </dependency> <dependency> <groupId>javax.persistence</groupId> <artifactId>persistence-api</artifactId> <version>1.0</version> </dependency> </dependencies> -- 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

18 years, 3 months

4
7
0 / 0

[Hibernate-JIRA] Created: (EJB-314) Duplicate object in persistent bag - regression in 3.3.1 EM

by Vincent Sevel (JIRA)

Duplicate object in persistent bag - regression in 3.3.1 EM ----------------------------------------------------------- Key: EJB-314 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-314 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA, 3.2.1 Environment: Hibernate version: 3.2.2 Hibernate annotations version: 3.3.0 Hibernate em version: 3.3.1 hsqldb 1.8.0 Reporter: Vincent Sevel Attachments: sources.txt, test_code_between_open_close.txt Doing a persist on a new object that has been added to an unitialized persistent bag, with lead to this collection containing 2 times the same new instance. However, if the collection is forced to be initialized before the persist, then it behaves correctly. This was working in 3.2.1, not anymore in 3.3.1. Look at the method findOrCreateCustodianAccount in test_code_between_open_close.txt and the XXX comments. -- 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

18 years, 3 months

2
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-1050) HQL Unions

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050?page=c... ] Diego Pires Plentz commented on HHH-1050: ----------------------------------------- If you take more 2 seconds reading this issue, you see that "Status =Open" ;-) > HQL Unions > ---------- > > Key: HHH-1050 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050 > Project: Hibernate3 > Issue Type: New Feature > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > > Add the ability to define unions in HQL. Support will be initially limited to only: > 1) scalar queries : select id from Animal union select id from Car > 2) the same entity : from Animal where ... union from Animal where ... > Support both UNION and UNION 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2834) java.lang.NullPointerException regression between 3.2.2 and 3.2.3 (related to HHH-252)

by Vincent Sevel (JIRA)

java.lang.NullPointerException regression between 3.2.2 and 3.2.3 (related to HHH-252) --------------------------------------------------------------------------------------- Key: HHH-2834 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2834 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3, 3.2.2 Environment: Hibernate version:3.2.3 Hibernate annotations version:3.3.0 Hibernate entity manager version:3.3.1 Hsqldb 1.8.0 Reporter: Vincent Sevel Attachments: sources.txt, test_code_and_exception.txt Code that was working in 3.2.2, now throws a null pointer in 3.2.3 after bug HHH-252 was fixed. In the stack trace belowe, a FixedLoanDepositInstrumentEty instance is created and merged. The embedded contractRef is null. When the new code in TypeFactory.replaceAssociations() gets executed, there is an attempt to get field values from the null component, which leads eventually to the exception. -- 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

18 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1283) ScrollableResults JoinFetch don't set child collection correctly　after the second parent object

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1283?page=c... ] Diego Pires Plentz commented on HHH-1283: ----------------------------------------- HHH-1751 is a dup, btw, has more info. > ScrollableResults JoinFetch don't set child collection correctly　after the second parent object > ----------------------------------------------------------------------------------------------- > > Key: HHH-1283 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1283 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1 > Environment: Hibernate 3.1 > Oracle10gR2 > Oracle JDBC Driver 10.2.0.1.0 > Sun JDK 1.5.0_06 > Spring 1.2.6 > Reporter: Masahiro Hirashima > Attachments: ScrollableCollectionFetchingTest.java, ScrollableResults.zip > > > ScrollableResults JoinFetch set child collection correctly at first parent object. > but after the second parent object, It set only the first element of a child collection. > I made the following tables. > CREATE TABLE owners ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > first_name VARCHAR(30), > last_name VARCHAR(30), > address VARCHAR(255), > city VARCHAR(80), > telephone VARCHAR(20), > version NUMBER(36, 0) DEFAULT 0 > ); > CREATE TABLE types ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > name VARCHAR(80), > version NUMBER(36, 0) DEFAULT 0 > ); > CREATE TABLE pets ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > name VARCHAR(30), > birth_date DATE, > type_id NUMBER(36, 0), > owner_id NUMBER(36, 0), > version NUMBER(36, 0) DEFAULT 0 > ); > and inserted the following data. > INSERT INTO owners VALUES (1, 'Betty', 'Davis', '638 Cardinal Ave.', 'Sun Prairie', '6085551749', 0); > INSERT INTO owners VALUES (2, 'Eduardo', 'Rodriquez', '2693 Commerce St.', 'McFarland', '6085558763', 0); > INSERT INTO pets VALUES (1, 'Leo', '2000-09-07', 1, 1, 0); > INSERT INTO pets VALUES (2, 'Basil', '2002-08-06', 2, 1, 0); > INSERT INTO pets VALUES (3, 'Rosy', '2001-04-17', 3, 2, 0); > INSERT INTO pets VALUES (4, 'Jewel', '2000-03-07', 4, 2, 0); > INSERT INTO pets VALUES (5, 'Iggy', '2000-11-30', 5, 2, 0); > INSERT INTO types VALUES (1, 'cat', 0); > INSERT INTO types VALUES (2, 'dog', 0); > INSERT INTO types VALUES (3, 'lizard', 0); > INSERT INTO types VALUES (4, 'snake', 0); > INSERT INTO types VALUES (5, 'bird', 0); > and I execute following code. > String hqlJoinFetchTest = > "from Owner owner " + > "left outer join fetch owner.pets as pets " + > "left outer join fetch pets.type " + > "order by owner.firstName, owner.lastName"; > Query query = session.createQuery(hqlJoinFetchTest); > ScrollableResults cursor = query.scroll(); > while ( cursor.next() ) { > Owner owner = (Owner)cursor.get(0); > System.out.println(owner); > } > result of this code is following. > petclinic.domain.Owner@15d616e[id=1,version=0,firstName=Betty,lastName=Davis, > petclinic.domain.Pet@136d9d8[id=2,version=0,name=Basil,birthDate=2002-08-06, > petclinic.domain.PetType@1be2893[id=2,version=0,name=dog] > petclinic.domain.Pet@14a75bb[id=1,version=0,name=Leo,birthDate=2000-09-07, > petclinic.domain.PetType@17779e3[id=1,version=0,name=cat] > petclinic.domain.Owner@e3570c[id=2,version=0,firstName=Eduardo,lastName=Rodriquez > petclinic.domain.Pet@167e3a5[id=4,version=0,name=Jewel,birthDate=2000-03-07, > petclinic.domain.PetType@1926e90[id=4,version=0,name=snake] > First owner object set collection collectly. > but second owner object don't set second pet object(id=5) and third pet object(id=6). -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1751) Collection corruptly loaded when join fetching and scrolling (org.hibernate.impl.FetchingScrollableResultsImpl)

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1751?page=c... ] Diego Pires Plentz resolved HHH-1751. ------------------------------------- Assignee: Diego Pires Plentz Resolution: Duplicate > Collection corruptly loaded when join fetching and scrolling (org.hibernate.impl.FetchingScrollableResultsImpl) > --------------------------------------------------------------------------------------------------------------- > > Key: HHH-1751 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1751 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.2.0.cr2 > Reporter: Maarten Winkels > Assignee: Diego Pires Plentz > Attachments: Child.java, HQLScrollFetchTest.java, Parent.java, ParentChild.hbm.xml, scroll-fetch-collection.patch > > > When scrolling a query that has a jon fetch on a collection (set), the collection is not loaded correctly. It appears that only the first item in the collection is correctly loaded. > Th attached tests show this behaviour, as well as a number of orderings in the query to show how the collection is corruptly loaded. -- 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

18 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2007