Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: <leg...@at...> - 2003-09-08 03:34:30
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-316 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-316 Summary: Twp bugs in Criteria API Type: Bug Status: Assigned Priority: Major Project: Hibernate2 Versions: 2.1 beta 3 Assignee: Gavin King Reporter: Gavin King Created: Sun, 7 Sep 2003 10:33 PM Updated: Sun, 7 Sep 2003 10:33 PM Description: (1) navigating many-to-many associations does not work! (2) "nested" createCriteria() does not work, eg. session.createCriteria(Foo.class) .createCriteria("set") .createCriteria("map"); blows up. http://forum.hibernate.org/viewtopic.php?p=1265#1265 --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-09-08 01:46:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 7 Sep 2003 8:45 PM
I implemented this (except for normalized mappings).
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-155
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-155
Summary: Optimistic locking by columns' original values
Type: New Feature
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 final
Versions:
2.0.1
Assignee: Gavin King
Reporter: TURIN ACCOUNT
Created: Tue, 8 Jul 2003 3:36 PM
Updated: Sun, 7 Sep 2003 8:45 PM
Description:
Ability to support optimistic locking by columns' original values. When UPDATE statements
are generated, in addition to the primary key, the WHERE clause includes either all of the
columns' original values, or just the changed columns' original values. This allows
optimistic locking without requiring the datamodel to have a "timestamp" or "version"
column.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-07 07:36:28
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 7 Sep 2003 2:36 AM
Doh! fixed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-315
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-315
Summary: Hibernate.close()
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: Ralph Schaer
Created: Sun, 7 Sep 2003 2:15 AM
Updated: Sun, 7 Sep 2003 2:36 AM
Environment: Windows XP, Java 1.4.2_01
Description:
There is a new close method in Hibernate.java
public void close(Iterator iterator) throws HibernateException {
But it's not possible to call the method because it is not static.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-07 07:16:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-315 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-315 Summary: Hibernate.close() Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Ralph Schaer Created: Sun, 7 Sep 2003 2:15 AM Updated: Sun, 7 Sep 2003 2:15 AM Environment: Windows XP, Java 1.4.2_01 Description: There is a new close method in Hibernate.java public void close(Iterator iterator) throws HibernateException { But it's not possible to call the method because it is not static. --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-09-07 04:55:27
|
The following comment has been added to this issue:
Author: Gavin King
Created: Sat, 6 Sep 2003 11:54 PM
Body:
OK, the implementation is perfect. I just can't seem to decide b/w two possible courses of action:
(1) accept this patch
(2) deprecate PersistentEnum entirely and tell people to _always_ use a UserType, which eliminates domain model dependencies upon Hibernate
The purist approach is definately (2), but PersistentEnum IS kinda convenient...
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-27
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-27
Summary: Persistent String Enum
Type: Patch
Status: Assigned
Priority: Minor
Project: Hibernate2
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:15 AM
Updated: Thu, 15 May 2003 4:38 AM
Description:
Persistent String Enum
PersistentEnum type is a very userfull feature, but in
the legacy data world it happens that some enumerations
are stored in "char" columns instead of integer and, as
far as I understood, I can map a persistent enumeration
only with integer.
Mapping my existing data I found several char(2) fields
that would be nice to map with an enumeration. I tried
to write a patch in order to manage such fields
introducing a new Hibernate type
PersistentStringEnumType and an interface
PersistentStringEnum that one can use as the existing
PersistenEnum interface.
Please, find the modified classes (TypeFactory,
MappingByReflection, Hibernate) and the new one
(PersistentStringEnum, PersistentEnum) in the attached
zip (for Hibernate 1.2)
(BTW: Does someone know a simple way to make a patch
against CVS?)
It also contains a test case for the feature. The test
sources explain how to use it.
http://sourceforge.net/tracker/index.php?func=detail&aid=684810&group_id=40712&atid=428711
The lenght of the field must be declared in the mapping
through the attribute in the <property> tag.
I would be nice if we could set it somewhere in the
class that define the PersistentStringEnum, but I can't
realize if it's possible.
stefano
Add a Comment:
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-06 14:40:34
|
The following comment has been added to this issue:
Author: Gavin King
Created: Sat, 6 Sep 2003 9:40 AM
Body:
Nope. ""!=null in either SQL or Java!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-313
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-313
Summary: CharacterType throws NullpointerException on empty characters
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Assignee:
Reporter: Klaus Zimmermann
Created: Fri, 5 Sep 2003 6:40 AM
Updated: Fri, 5 Sep 2003 7:39 AM
Environment: mysql, mysql-connector-java-2.0.14
Description:
Some databases (i.e. MySql) seem to trim whitespaces under certain conditions. This leads to an empty String in CharacterType.get(ResultSet rs, String name) being provided by the ResultSet which passes the Null check and causes the NullPointer Exception in the str.charAt(0).
Patch attached.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 12:50:28
|
The following comment has been added to this issue:
Author: Klaus Zimmermann
Created: Fri, 5 Sep 2003 7:50 AM
Body:
what else could lead to a empty string?
If it wasn't set at all the result would be null, right?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-313
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-313
Summary: CharacterType throws NullpointerException on empty characters
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Assignee:
Reporter: Klaus Zimmermann
Created: Fri, 5 Sep 2003 6:40 AM
Updated: Fri, 5 Sep 2003 7:39 AM
Environment: mysql, mysql-connector-java-2.0.14
Description:
Some databases (i.e. MySql) seem to trim whitespaces under certain conditions. This leads to an empty String in CharacterType.get(ResultSet rs, String name) being provided by the ResultSet which passes the Null check and causes the NullPointer Exception in the str.charAt(0).
Patch attached.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 12:39:28
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 5 Sep 2003 7:39 AM
I'm rejecting this because it should be correctly considered to be a MySQL bug that is best worked-around using a UserType. It is _quite_ incorrect for Hibernate to interpret the empty string "" as an actual space character " ".
Just use a UserType. Thats what its there for!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-313
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-313
Summary: CharacterType throws NullpointerException on empty characters
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Assignee:
Reporter: Klaus Zimmermann
Created: Fri, 5 Sep 2003 6:40 AM
Updated: Fri, 5 Sep 2003 7:39 AM
Environment: mysql, mysql-connector-java-2.0.14
Description:
Some databases (i.e. MySql) seem to trim whitespaces under certain conditions. This leads to an empty String in CharacterType.get(ResultSet rs, String name) being provided by the ResultSet which passes the Null check and causes the NullPointer Exception in the str.charAt(0).
Patch attached.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 12:33:29
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 5 Sep 2003 7:33 AM
Hibernate uses the rules defined by the JavaBeans specification. This is not a bug. Please use the user forum if you have these kinds of issues.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-314
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-314
Summary: "Could not find a getter for ..."-Exception, if fieldname like "f_zip"
Type: Bug
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Versions:
2.1 beta 2
Assignee:
Reporter: Sven Homburg
Created: Fri, 5 Sep 2003 6:59 AM
Updated: Fri, 5 Sep 2003 7:33 AM
Environment: Windows/2000, Java Sun 1.4, MySQL 4.0.12
Description:
if i want to initialize Hibernate, its stop
with the error :
"Could not find a getter for fZip in class de.hsofttec.avs.model.database.hbm.AvsZscaleEntry"
the hbm.xml looks like :
<property column="f_zip" length="6" name="fZip" type="java.lang.String">
<column length="6" name="f_zip" not-null="false" sql-type="char(6)"/>
</property>
<property column="t_zip" length="6" name="tZip" type="java.lang.String">
<column length="6" name="t_zip" not-null="false" sql-type="char(6)"/>
</property>
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 11:59:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-314 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-314 Summary: "Could not find a getter for ..."-Exception, if fieldname like "f_zip" Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Versions: 2.1 beta 2 Assignee: Reporter: Sven Homburg Created: Fri, 5 Sep 2003 6:59 AM Updated: Fri, 5 Sep 2003 6:59 AM Environment: Windows/2000, Java Sun 1.4, MySQL 4.0.12 Description: if i want to initialize Hibernate, its stop with the error : "Could not find a getter for fZip in class de.hsofttec.avs.model.database.hbm.AvsZscaleEntry" the hbm.xml looks like : <property column="f_zip" length="6" name="fZip" type="java.lang.String"> <column length="6" name="f_zip" not-null="false" sql-type="char(6)"/> </property> <property column="t_zip" length="6" name="tZip" type="java.lang.String"> <column length="6" name="t_zip" not-null="false" sql-type="char(6)"/> </property> --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-09-05 11:42:28
|
The following issue has been updated:
Updater: Klaus Zimmermann (mailto:kla...@xc...)
Date: Fri, 5 Sep 2003 6:40 AM
Comment:
The patch.
Changes:
Attachment changed to Hibernate2_CharacterType.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-313&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-313
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-313
Summary: CharacterType throws NullpointerException on empty characters
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Klaus Zimmermann
Created: Fri, 5 Sep 2003 6:40 AM
Updated: Fri, 5 Sep 2003 6:40 AM
Environment: mysql, mysql-connector-java-2.0.14
Description:
Some databases (i.e. MySql) seem to trim whitespaces under certain conditions. This leads to an empty String in CharacterType.get(ResultSet rs, String name) being provided by the ResultSet which passes the Null check and causes the NullPointer Exception in the str.charAt(0).
Patch attached.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 11:40:30
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-313 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-313 Summary: CharacterType throws NullpointerException on empty characters Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: Klaus Zimmermann Created: Fri, 5 Sep 2003 6:40 AM Updated: Fri, 5 Sep 2003 6:40 AM Environment: mysql, mysql-connector-java-2.0.14 Description: Some databases (i.e. MySql) seem to trim whitespaces under certain conditions. This leads to an empty String in CharacterType.get(ResultSet rs, String name) being provided by the ResultSet which passes the Null check and causes the NullPointer Exception in the str.charAt(0). Patch attached. --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-09-05 11:11:28
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 5 Sep 2003 6:10 AM
Closing this due to nonresponsive user.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-305
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-305
Summary: net.sf.hibernate.Query / Oracle 8 vs 8i / ORDER BY / ORA-00907: missing right parenthesis
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.2
2.0.3
Assignee:
Reporter: W. Muir
Created: Tue, 2 Sep 2003 7:38 PM
Updated: Fri, 5 Sep 2003 6:10 AM
Environment: Oracle 8.0.5 / Oracle 8.1.5
Description:
Using "ORDER BY" in a query string does NOT work on Oracle 8.0.5, but works fine on Oracle 8.1.5.
Exception: ORA-00907: missing right parenthesis
...
Query accountQuery = session.createQuery( "FROM com.something.Account x ORDER BY x.identifier" );
accountQuery.setFirstResult( 10 );
accountQuery.setMaxResults( 100 );
accountQuery.list();
java.sql.SQLException: ORA-00907: missing right parenthesis
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.ja
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Pr
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleS
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(O
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(O
at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImp
at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:5
at net.sf.hibernate.loader.Loader.doFind(Loader.java:140)
at net.sf.hibernate.loader.Loader.find(Loader.java:620)
at net.sf.hibernate.hql.QueryTranslator.find(QueryTranslator
at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1
at net.sf.hibernate.impl.QueryImpl.list(QueryImpl.java:76)
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 11:09:27
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Fri, 5 Sep 2003 6:09 AM
Comment:
This is known and is a _very_ low priority. I won't be addressing this anytime soon. You might like to have a look at creating your own patch, but if it complicates the code significantly, I probably won't accept it.
Changes:
type changed from Bug
priority changed from Critical
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-312&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-312
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-312
Summary: Subclasses using super method not found properly
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee:
Reporter: Jonas Van Poucke
Created: Fri, 5 Sep 2003 4:33 AM
Updated: Fri, 5 Sep 2003 6:09 AM
Description:
Whe have two classes:
--- Base Class ---
public class SuperWithMap {
private Map members;
public void setMembers(Map value) {
this.members = value;
}
public Map getMembers() {
return members;
}
public void addMember(Object member) {
members.put(member, null); // value is a dummy
}
}
--- SubClass ---
public class SubWithSet extends SuperWithMap {
public void setMembers(Set value) {
Iterator iter = value.iterator();
while (iter.hasNext()) {
super.addMember(iter.next());
}
}
}
--- Mapping ---
The subclass should use the super-classes method to set the Map:
<class
name="SuperWithMap"
table="SuperTable">
<joined-subclass
name="SubWithSet"
table="SubTable">
<key column="ref_id"/>
<map
name="members"
table="RefTable"
lazy="false"
cascade="all">
<key column="mem_id"/>
<index-many-to-many column="value_id" class="some-other-class" />
<element column="otherclassvalue" type="double"/>
</map>
</class>
Note: the reference in the map to some-other-table is ommited
--- Problem ---
When trying to load data for the subclass SubWithSet, the attribute "members" is set with the method setMembers(Set value) and not with the super-classes setMembers(Map value).
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 09:34:31
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-312 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-312 Summary: Subclasses using super method not found properly Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: Jonas Van Poucke Created: Fri, 5 Sep 2003 4:33 AM Updated: Fri, 5 Sep 2003 4:33 AM Description: Whe have two classes: --- Base Class --- public class SuperWithMap { private Map members; public void setMembers(Map value) { this.members = value; } public Map getMembers() { return members; } public void addMember(Object member) { members.put(member, null); // value is a dummy } } --- SubClass --- public class SubWithSet extends SuperWithMap { public void setMembers(Set value) { Iterator iter = value.iterator(); while (iter.hasNext()) { super.addMember(iter.next()); } } } --- Mapping --- The subclass should use the super-classes method to set the Map: <class name="SuperWithMap" table="SuperTable"> <joined-subclass name="SubWithSet" table="SubTable"> <key column="ref_id"/> <map name="members" table="RefTable" lazy="false" cascade="all"> <key column="mem_id"/> <index-many-to-many column="value_id" class="some-other-class" /> <element column="otherclassvalue" type="double"/> </map> </class> Note: the reference in the map to some-other-table is ommited --- Problem --- When trying to load data for the subclass SubWithSet, the attribute "members" is set with the method setMembers(Set value) and not with the super-classes setMembers(Map value). --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <maf...@da...> - 2003-09-05 09:26:09
|
confirm 177816 ------------------------------------------------ Marco Antonio Fuentelsaz P=E9rez Dpto. I+D E.P. Desarrollo Agrario y Pesquero. Bergant=EDn 39=20 41012 Sevilla Tel: 95 493 81 00 Ext:8383 maf...@da... ------------------------------------------------ ----------------------------------------------------- Este correo electr=F3nico y, en su caso, cualquier fichero anexo al mismo, contiene informaci=F3n de car=E1cter confidencial exclusivamente dirigida a su destinatario o destinatarios. Queda prohibida su divulgaci=F3n, copia o distribuci=F3n a terceros sin la previa autorizaci=F3n escrita de Dap. En el caso de haber recibido este correo electr=F3nico por error, se ruega notif=EDquese inmediatamente esta circunstancia mediante reenv=EDo a la direcci=F3n electr=F3nica del remitente. ---------------------------------------------------------- The information in this e-mail and in any attachments is confidential and solely for the attention and use of the named addressee(s). You are hereby notified that any dissemination, distribution or copy of this communication is prohibited without the prior written consent=20 of Dap. If you have received this communication in error, please, notify the sender by reply e-mail. ------------------------------------------------------------- |
|
From: <leg...@at...> - 2003-09-05 09:13:33
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 5 Sep 2003 4:12 AM
The test code works fine against my current CVS snapshot. The problem may have already been fixed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-311
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-311
Summary: key-many-to-one in composite-id causes MappingException
Type: Bug
Status: Closed
Priority: Major
Resolution: CANNOT REPRODUCE
Project: Hibernate2
Components:
core
Versions:
2.1 beta 2
Assignee:
Reporter: Greg Barton
Created: Fri, 5 Sep 2003 12:26 AM
Updated: Fri, 5 Sep 2003 4:12 AM
Environment: mapping
Description:
Placing a key-many-to-one element in a composite-id element can cause a MappingException to be thrown when creating a SessionFactory.
NOTE:
See attached tar. Run the and script for a demonstration. The only jar I included was the hibernate-tools.jar, as I compiled it from the latest CVS snapshot.
Versions used:
Hibernate 2.1 beta 2
Hibernate tools from CVS snapshot 2003-09-04
I was able to find one situation where the MappingException was NOT thrown. If you run the com.foo.bar.data.Demonstration class from the command line and do NOT put log4j.jar in the classpath, the SessionFactory is created successfully. (Doing this while running from the Ant script STILL results in a MappingException.)
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 05:27:29
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-311 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-311 Summary: key-many-to-one in composite-id causes MappingException Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 2 Assignee: Reporter: Greg Barton Created: Fri, 5 Sep 2003 12:26 AM Updated: Fri, 5 Sep 2003 12:26 AM Environment: mapping Description: Placing a key-many-to-one element in a composite-id element can cause a MappingException to be thrown when creating a SessionFactory. NOTE: See attached tar. Run the and script for a demonstration. The only jar I included was the hibernate-tools.jar, as I compiled it from the latest CVS snapshot. Versions used: Hibernate 2.1 beta 2 Hibernate tools from CVS snapshot 2003-09-04 I was able to find one situation where the MappingException was NOT thrown. If you run the com.foo.bar.data.Demonstration class from the command line and do NOT put log4j.jar in the classpath, the SessionFactory is created successfully. (Doing this while running from the Ant script STILL results in a MappingException.) --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-09-05 05:27:28
|
The following issue has been updated:
Updater: Greg Barton (mailto:gre...@ya...)
Date: Fri, 5 Sep 2003 12:26 AM
Changes:
Attachment changed to code.tar.gz
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-311&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-311
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-311
Summary: key-many-to-one in composite-id causes MappingException
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 2
Assignee:
Reporter: Greg Barton
Created: Fri, 5 Sep 2003 12:26 AM
Updated: Fri, 5 Sep 2003 12:26 AM
Environment: mapping
Description:
Placing a key-many-to-one element in a composite-id element can cause a MappingException to be thrown when creating a SessionFactory.
NOTE:
See attached tar. Run the and script for a demonstration. The only jar I included was the hibernate-tools.jar, as I compiled it from the latest CVS snapshot.
Versions used:
Hibernate 2.1 beta 2
Hibernate tools from CVS snapshot 2003-09-04
I was able to find one situation where the MappingException was NOT thrown. If you run the com.foo.bar.data.Demonstration class from the command line and do NOT put log4j.jar in the classpath, the SessionFactory is created successfully. (Doing this while running from the Ant script STILL results in a MappingException.)
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 05:14:28
|
The following comment has been added to this issue:
Author: Greg Barton
Created: Fri, 5 Sep 2003 12:13 AM
Body:
This will be especially convenient when static imports are introduced in Java 1.5. :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-29
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-29
Summary: generation of static final String for fields
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:17 AM
Updated: Sat, 10 May 2003 9:49 PM
Description:
generation of static final String for fields
While using Hibernate, we sometimes still call some
direct sql queries that
return resultsets that we process afterwards. We find
easier to use direct sql
than Hibernate in these cases.
Anyway, Hibernate could provide some help: if every
field in each persistent
class had a corresponding constant string, that string
could be used in the
sql statement.
Example:
Given table A_table: varchar fieldone, int fieldtwo...
Something like this woudl be generated:
class Atable
public static final String TABLENAME="A_table"
public static final String FIELDONE ="fieldone"
public static final String FIELDTWO ="fieldtwo"
...
And these constants can be used in the java code:
String sql = "select ..." + A.FIELDONE +" = 'avalue'"...
That way, when the field change in the db (as it
happens very often, at least
in our projects), and code is regenerated, it is easier
to handle, as errors
are catched at compile. We were doing that in our
previous home made persistance
stuff. Also, for the lazy, you get code completion to
work :)
The generation could be set conditionally in the xml or
at command line when
generating the code. It must be quite easy to add to
the current generator,
but maybe is not usefull for other people, I dont know.
http://sourceforge.net/tracker/index.php?func=detail&aid=701428&group_id=40712&atid=428711
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-05 02:32:31
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 4 Sep 2003 9:31 PM
I don't see this as a bug. This is how CharacterType has worked forever.
If you are representing a null, use a SQL null.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-310
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-310
Summary: CharacterType.get(ResultSet rs, String name) on zero length String
Type: Bug
Status: Closed
Priority: Blocker
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.2
2.0.3
Assignee:
Reporter: Tim Schafer
Created: Thu, 4 Sep 2003 11:03 AM
Updated: Thu, 4 Sep 2003 9:31 PM
Environment: Sun JDK 1.4.2
Mysql 4.0.13
Description:
The get method of CharacterType is calling
java.lang.String.charAt(0)
on a String instance that has zero length
This resulted rom trying to load a mapped object from
a Mysql 4.0.13 record that has a blank column
Sep 4, 2003 8:55:27 AM net.sf.hibernate.impl.IteratorImpl next
SEVERE: could not get next result
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
at test.TestHibernate.main(TestHibernate.java:94)
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
at test.TestHibernate.main(TestHibernate.java:94)
rethrown as net.sf.hibernate.LazyInitializationException: Hibernate lazy instantiation problem: String index out of range: 0
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:81)
at test.TestHibernate.main(TestHibernate.java:94)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
... 1 more
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-04 22:49:28
|
The following comment has been added to this issue:
Author: Tim Schafer
Created: Thu, 4 Sep 2003 5:48 PM
Body:
Ok the reason that CharacterType is being used is that the
class being mapped to uses a char for that attribute
Duh!
I created a String attribute in the class to map to and all is well
But there does seems to be a bug here
I created a char column in the database
copied the varchar column to it
and mapped that to the char attribute
If that char column is blank it will trip up the same section
of CharacterType
Mapping a char column from a mysql table to a char attribute
does seem a legitimate use case.
And hibernate shouldn't blow up because that char column is blank
I'm not sure if the blank char should map to a null char
or a ' '
But I think ' ' would preserve the semantics in the case of Mysql
columns
whereas null would imply the column was NULL in the database
This bug's priority can be lowered as far as I'm concerned though
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-310
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-310
Summary: CharacterType.get(ResultSet rs, String name) on zero length String
Type: Bug
Status: Unassigned
Priority: Blocker
Project: Hibernate2
Components:
core
Versions:
2.0.2
2.0.3
Assignee:
Reporter: Tim Schafer
Created: Thu, 4 Sep 2003 11:03 AM
Updated: Thu, 4 Sep 2003 11:03 AM
Environment: Sun JDK 1.4.2
Mysql 4.0.13
Description:
The get method of CharacterType is calling
java.lang.String.charAt(0)
on a String instance that has zero length
This resulted rom trying to load a mapped object from
a Mysql 4.0.13 record that has a blank column
Sep 4, 2003 8:55:27 AM net.sf.hibernate.impl.IteratorImpl next
SEVERE: could not get next result
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
at test.TestHibernate.main(TestHibernate.java:94)
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
at test.TestHibernate.main(TestHibernate.java:94)
rethrown as net.sf.hibernate.LazyInitializationException: Hibernate lazy instantiation problem: String index out of range: 0
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:81)
at test.TestHibernate.main(TestHibernate.java:94)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
... 1 more
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-04 18:15:33
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Thu, 4 Sep 2003 1:15 PM
Fixed in cvs
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-309
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-309
Summary: hbm2java: render default values specified in mapping in default constructor
Type: New Feature
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
toolset
Fix Fors:
2.1
Assignee:
Reporter: Klaus Zimmermann
Created: Thu, 4 Sep 2003 10:12 AM
Updated: Thu, 4 Sep 2003 1:15 PM
Description:
It would be nice to be able to specify default values in the mapping (via a meta-attribute?) which then would be rendered into the default constructor of automatically generated classes.
Suggested syntax:
<class name="foo">
<property name="name" type="string">
<meta attribute="default-value">bar</meta>
</property>
</class>
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-04 17:44:33
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Thu, 4 Sep 2003 12:43 PM
Body:
easy one to do ;)
Guess, i'll just do it as simple as possible and require you to format the value your self - so string's need to be quoted, ok ?
That would allow you to specify whatever you want - even a method call.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-309
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-309
Summary: hbm2java: render default values specified in mapping in default constructor
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
toolset
Assignee:
Reporter: Klaus Zimmermann
Created: Thu, 4 Sep 2003 10:12 AM
Updated: Thu, 4 Sep 2003 10:12 AM
Description:
It would be nice to be able to specify default values in the mapping (via a meta-attribute?) which then would be rendered into the default constructor of automatically generated classes.
Suggested syntax:
<class name="foo">
<property name="name" type="string">
<meta attribute="default-value">bar</meta>
</property>
</class>
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-09-04 17:19:28
|
The following comment has been added to this issue:
Author: Tim Schafer
Created: Thu, 4 Sep 2003 12:18 PM
Body:
Adding the following change
if(str.length() == 0)
return new Character( ' ' );
else
return new Character( str.charAt(0) );
in place of
return new Character( str.charAt(0) );
makes the problem go away
The part I don't understand is why CharacterType was even
being used
The column in the mysql 4.0.13 database is of type varchar(15)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-310
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-310
Summary: CharacterType.get(ResultSet rs, String name) on zero length String
Type: Bug
Status: Unassigned
Priority: Blocker
Project: Hibernate2
Components:
core
Versions:
2.0.2
2.0.3
Assignee:
Reporter: Tim Schafer
Created: Thu, 4 Sep 2003 11:03 AM
Updated: Thu, 4 Sep 2003 11:03 AM
Environment: Sun JDK 1.4.2
Mysql 4.0.13
Description:
The get method of CharacterType is calling
java.lang.String.charAt(0)
on a String instance that has zero length
This resulted rom trying to load a mapped object from
a Mysql 4.0.13 record that has a blank column
Sep 4, 2003 8:55:27 AM net.sf.hibernate.impl.IteratorImpl next
SEVERE: could not get next result
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
at test.TestHibernate.main(TestHibernate.java:94)
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
at test.TestHibernate.main(TestHibernate.java:94)
rethrown as net.sf.hibernate.LazyInitializationException: Hibernate lazy instantiation problem: String index out of range: 0
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:81)
at test.TestHibernate.main(TestHibernate.java:94)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at net.sf.hibernate.type.CharacterType.get(CharacterType.java:19)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:59)
at net.sf.hibernate.type.NullableType.nullSafeGet(NullableType.java:51)
at net.sf.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:139)
at net.sf.hibernate.collection.CollectionPersister.readElement(CollectionPersister.java:377)
at net.sf.hibernate.collection.Set.readFrom(Set.java:242)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:175)
at net.sf.hibernate.loader.Loader.loadCollection(Loader.java:602)
at net.sf.hibernate.loader.CollectionLoader.initialize(CollectionLoader.java:82)
at net.sf.hibernate.impl.SessionImpl.initialize(SessionImpl.java:2897)
at net.sf.hibernate.collection.PersistentCollection.getInitialValue(PersistentCollection.java:128)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:74)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1959)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:109)
at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:57)
at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:70)
... 1 more
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
93 messages has been excluded from this view by a project administrator.
