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-10-29 23:26:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 29 Oct 2003 5:25 PM
Just use the form of setParameter() which takes an explicit Type. JDBC requires the typecode in setNull().
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-433
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-433
Summary: Allow to bind null parameters to the query
Type: Improvement
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1 beta 1
2.1 beta 2
2.1 final
2.1 beta 4
2.1 beta 5
Assignee:
Reporter: Giedrius Trumpickas
Created: Wed, 29 Oct 2003 12:15 PM
Updated: Wed, 29 Oct 2003 5:25 PM
Description:
SELECT p FROM Person AS p WHERE ((? is null) OR (p.firstname = ?)) AND ((? is null) OR (p.lastname = ?))
This query assumes that person can be searched by firstname, lastname or both. Right now hibernate throws NullPointerException when I'm trying to bind null parameter because it tries to guess parameter type and ...
Maybe in Hibernate we need to introduce NullType for scalar values ?
Reason for such funcionality is to have dynamic searches from UI when user can enter bunch of search parameters and not all parameters are required.
PS:
I know that query above can be expressed by search criteria but this is just an example real query is more complicated and it can not be expressed with Criteria.
---------------------------------------------------------------------
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-10-29 21:25:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-434 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-434 Summary: Have the ability to turn off and on Hibernate constraints Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: John Towell Created: Wed, 29 Oct 2003 3:24 PM Updated: Wed, 29 Oct 2003 3:24 PM Description: In most relational DB's you are able to disable FK constraints and then enable them later. This is helpful when loading the DB with data. It would be beneficial to allow Hibernate to do the same. (i.e) do not throw the net.sf.hibernate.ObjectNotFoundException: No row with the given identifier exists: for a certain amount of time. This would allow the use of Hibernate delete's in the data clean-up before the FK constraints are turned back on. I guess if people wish do disable the Hibernate constraints altogether that would be a possibility as well. Some postings where this is adressed. http://forum.hibernate.org/viewtopic.php?t=219 http://forum.hibernate.org/viewtopic.php?t=925118 --------------------------------------------------------------------- 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-10-29 19:58:14
|
The following comment has been added to this issue:
Author: Giedrius Trumpickas
Created: Wed, 29 Oct 2003 1:58 PM
Body:
Actually there is no need for change in hibernate this situation easy can be solved at application level.
Insead of ((? is null) or (param = ?)) it's possible to use
((? = true) or (param = ?)) where first parameter is set by application if param value is null
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-433
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-433
Summary: Allow to bind null parameters to the query
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 beta 1
2.1 beta 2
2.1 final
2.1 beta 4
2.1 beta 5
Assignee:
Reporter: Giedrius Trumpickas
Created: Wed, 29 Oct 2003 12:15 PM
Updated: Wed, 29 Oct 2003 12:15 PM
Description:
SELECT p FROM Person AS p WHERE ((? is null) OR (p.firstname = ?)) AND ((? is null) OR (p.lastname = ?))
This query assumes that person can be searched by firstname, lastname or both. Right now hibernate throws NullPointerException when I'm trying to bind null parameter because it tries to guess parameter type and ...
Maybe in Hibernate we need to introduce NullType for scalar values ?
Reason for such funcionality is to have dynamic searches from UI when user can enter bunch of search parameters and not all parameters are required.
PS:
I know that query above can be expressed by search criteria but this is just an example real query is more complicated and it can not be expressed with Criteria.
---------------------------------------------------------------------
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-10-29 18:16:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-433 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-433 Summary: Allow to bind null parameters to the query Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 beta 1 2.1 beta 2 2.1 final 2.1 beta 4 2.1 beta 5 Assignee: Reporter: Giedrius Trumpickas Created: Wed, 29 Oct 2003 12:15 PM Updated: Wed, 29 Oct 2003 12:15 PM Description: SELECT p FROM Person AS p WHERE ((? is null) OR (p.firstname = ?)) AND ((? is null) OR (p.lastname = ?)) This query assumes that person can be searched by firstname, lastname or both. Right now hibernate throws NullPointerException when I'm trying to bind null parameter because it tries to guess parameter type and ... Maybe in Hibernate we need to introduce NullType for scalar values ? Reason for such funcionality is to have dynamic searches from UI when user can enter bunch of search parameters and not all parameters are required. PS: I know that query above can be expressed by search criteria but this is just an example real query is more complicated and it can not be expressed with Criteria. --------------------------------------------------------------------- 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-10-29 17:19:21
|
The following comment has been added to this issue:
Author: David Duffy
Created: Wed, 29 Oct 2003 11:18 AM
Body:
I could certainly make great use of a Criteria.count() method for paging results and was hoping there already was one.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-143
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-143
Summary: Criteria.count() and Query.count()
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Assignee:
Reporter: Alexey Kaigorodov
Created: Wed, 18 Jun 2003 10:53 PM
Updated: Sat, 21 Jun 2003 3:26 AM
Description:
Add method count in classes Criteria and Query.
Example:
final int PAGE_SIZE;
int position;
...
Query query = ... // build complex query with many parameters
int pageNum = position / PAGE_SIZE + 1;
int pageCount = query.count() / PAGE_SIZE + 1; // <-- HERE
System.out.println("Page " + pageNum + " from " + pageCount);
query.setFirstResult(position);
query.setMaxResults(PAGE_SIZE);
List page = query.list();
System.out.println(page);
Not necessary will twice create the similar Query or Criteria.
By Criteria always easy build sql count query.
For Query.count() throw exception if create sql count query impossible.
---------------------------------------------------------------------
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-10-29 17:11:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-432 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-432 Summary: SchemaTool a little too verbose Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Assignee: Reporter: Jason Novotny Created: Wed, 29 Oct 2003 11:10 AM Updated: Wed, 29 Oct 2003 11:10 AM Description: SchemExport ant task gives me lots of verbose messsages like: schemaexport] drop table sportletuserattributes [schemaexport] Unsuccessful: Table not found: SPORTLETUSERATTRIBUTES in statement [drop table sportletuserattributes] [schemaexport] drop table authmoduleattributes [schemaexport] Unsuccessful: Table not found: AUTHMODULEATTRIBUTES in statement [drop table authmoduleattributes] [schemaexport] drop table sportletgroup [schemaexport] Unsuccessful: Table not found: SPORTLETGROUP in statement [drop table sportletgroup] [schemaexport] drop table grouprequestimpl [schemaexport] Unsuccessful: Table not found: GROUPREQUESTIMPL in statement [drop table grouprequestimpl] [schemaexport] drop table dbmsuserpassword [schemaexport] Unsuccessful: Table not found: DBMSUSERPASSWORD in statement [drop table dbmsuserpassword] I understand these messages, but unfortunately the users of my software think they are errors! Instead of spelling out in our users guide they are normal-- I'd like to just turn the verbosity off --------------------------------------------------------------------- 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-10-29 16:57:14
|
The following issue has been updated:
Updater: Finn McCann (mailto:mc...@du...)
Date: Wed, 29 Oct 2003 10:56 AM
Comment:
Ignore previous attachment.
informix_patch_to_v2003_II.zip works.
Changes:
Attachment changed to informix_patch_to_v2003_II.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-414&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-414
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-414
Summary: Informix dialect creates syntax errors in IDS 9.4
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Versions:
2.0.2
Assignee: Max Rydahl Andersen
Reporter: Finn McCann
Created: Tue, 21 Oct 2003 11:01 AM
Updated: Wed, 29 Oct 2003 10:56 AM
Environment: Hibernate2 on JDK1.4 on Win2000, talking via Informix JDBC 2.21.JC5 driver to Informix IDS 9.4 on another Windows 2000 box.
Description:
Having tested Informix dialect in Hibernate2 against Informix IDS v9.4, we found a couple of issues:
1. Serial ids:
<id name="id" column="ID" length="32" unsaved-value="null">
<generator class="uuid.hex"/>
</id>
creates a data type:
INT8 SERIAL
instead of:
SERIAL8
The "INT8 SERIAL" causes a syntax error in IDS 9.4.
2. Foreign Key constraint names:
<set name="upliftRates" lazy="true" cascade="all" order-by="EFFECTIVE_DATE desc">
<key column="NETWORK_ID" length="32"/>
<one-to-many class="com.capetechnologies.multinet.domain.UpliftRate"/>
</set>
creates this ALTER TABLE statement:
alter table MULTINET_TAX_RATES add constraint FKE1700D046924EC foreign key (NETWORK_ID) references MULTINET_NETWORK
instead of:
alter table MULTINET_TAX_RATES add constraint foreign key (NETWORK_ID) references MULTINET_NETWORK constraint FKE1700D046924EC
Having "CONSTRAINT <constraint name>" within the statement instead of at the end causes a syntax error.
This also applies to adding UNIQUE CONSTRAINTs.
---------------------------------------------------------------------
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-10-29 14:32:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 29 Oct 2003 8:31 AM
There was a mapping bug in the one-to-one associations.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-431
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-431
Summary: one-to-many association with composite-id
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee:
Reporter: Albini Guillaume
Created: Wed, 29 Oct 2003 8:04 AM
Updated: Wed, 29 Oct 2003 8:31 AM
Environment: Java 1.4 on Solaris 2.7
Description:
Exception on the method
SessionFactory sessions = cfg.buildSessionFactory();
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException
at net.sf.hibernate.sql.OracleJoinFragment.addJoin(OracleJoinFragment.java:25)
at net.sf.hibernate.loader.OuterJoinLoader.outerJoins(OuterJoinLoader.java:424)
at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:47)
at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:34)
at net.sf.hibernate.loader.EntityLoader.<init>(EntityLoader.java:35)
at net.sf.hibernate.persister.EntityPersister.postInstantiate(EntityPersister.java:153)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:223)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:627)
---------------------------------------------------------------------
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-10-29 14:12:14
|
The following issue has been updated:
Updater: Albini Guillaume (mailto:ga...@in...)
Date: Wed, 29 Oct 2003 8:12 AM
Comment:
mapping file and classes
Changes:
Attachment changed to transcryptome.jar.gz
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-431&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-431
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-431
Summary: one-to-many association with composite-id
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0.3
Assignee:
Reporter: Albini Guillaume
Created: Wed, 29 Oct 2003 8:04 AM
Updated: Wed, 29 Oct 2003 8:12 AM
Environment: Java 1.4 on Solaris 2.7
Description:
Exception on the method
SessionFactory sessions = cfg.buildSessionFactory();
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException
at net.sf.hibernate.sql.OracleJoinFragment.addJoin(OracleJoinFragment.java:25)
at net.sf.hibernate.loader.OuterJoinLoader.outerJoins(OuterJoinLoader.java:424)
at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:47)
at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:34)
at net.sf.hibernate.loader.EntityLoader.<init>(EntityLoader.java:35)
at net.sf.hibernate.persister.EntityPersister.postInstantiate(EntityPersister.java:153)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:223)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:627)
---------------------------------------------------------------------
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-10-29 14:04:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-431 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-431 Summary: one-to-many association with composite-id Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0.3 Assignee: Reporter: Albini Guillaume Created: Wed, 29 Oct 2003 8:04 AM Updated: Wed, 29 Oct 2003 8:04 AM Environment: Java 1.4 on Solaris 2.7 Description: Exception on the method SessionFactory sessions = cfg.buildSessionFactory(); Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException at net.sf.hibernate.sql.OracleJoinFragment.addJoin(OracleJoinFragment.java:25) at net.sf.hibernate.loader.OuterJoinLoader.outerJoins(OuterJoinLoader.java:424) at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:47) at net.sf.hibernate.loader.AbstractEntityLoader.renderStatement(AbstractEntityLoader.java:34) at net.sf.hibernate.loader.EntityLoader.<init>(EntityLoader.java:35) at net.sf.hibernate.persister.EntityPersister.postInstantiate(EntityPersister.java:153) at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:223) at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:627) --------------------------------------------------------------------- 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-10-29 02:04:38
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 28 Oct 2003 8:01 PM
Thanks, i applied this patch.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-323
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-323
Summary: Proxool properties specified in hibernate.properties
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 beta 5
Versions:
2.1
Assignee: Gavin King
Reporter: Craig Raw
Created: Thu, 11 Sep 2003 5:09 AM
Updated: Tue, 28 Oct 2003 8:01 PM
Description:
As discussed in the Hibernate foruum:
There is a problem in configuring Proxool from properties specified in hibernate.properties. These are the properties prefixed by hibernate.proxool.*.
In determining which ConnectionProvider to use, ConnectionProviderFactory looks in order for a properties set for hibernate.connection.datasource, hibernate.c3p0.max_size, hibernate.dbcp.maxActive, hibernate.connection.url, and then the Proxool properties. This means that if the hibernate.connection.url property is specified, one cannot obtain a Proxool connection provider.
However, when one sets hibernate.proxool.existing_pool=false and uses the hibernate.proxool.* properties, the hibernate.connection.url is used in ProxoolConnectionProvider to create the pool.
This patch changes the order in ConnectionProviderFactory to look for the Proxool properties before the hibernate.connection.url property.
(BTW, using hibernate.proxool.* properties is useful when configuring pools dynamically, as the external configuration sources for Proxool are more difficult to change.)
---------------------------------------------------------------------
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-10-29 01:58:51
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 28 Oct 2003 7:56 PM
Finally fixed!
:)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-97
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-97
Summary: enhancement to "select new"
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1 beta 5
Versions:
2.0rc2
Assignee: Gavin King
Reporter: Ian Booth
Created: Thu, 22 May 2003 5:47 PM
Updated: Tue, 28 Oct 2003 7:56 PM
Description:
I have implemented an enhancement to the feature of HQL which allows the following types of query:
select new FooDTO(bar.id, foobar.id, bar.name) from Bar as bar join FooBar as foobar
In the case where the construction arguments to FooDTO are numeric (eg assume id atributes above are longs), then the code inside the renderSQL() method of QueryTranslator.java looks for a constructor of the form FooDTO(long barId, long foobarId, String barName).
However, if an outer join is used in the query
ie select new FooDTO(bar.id, foobar.id, bar.name) from Bar as bar left join FooBar as foobar
then foobar.id may be null and the current Hibernate code will fail with a null pointer exception.
I have altered the code inside the renderSQL() method to first look for a constructor taking the proper object types for Numeric arguments and if this one can't be found, then it defaults to the current behavior.
ie in the example above it looks for FooDTO(Long fooId, Long barId, String barName) and if this one can't be found it instead looks for FooDTO(long fooId, long barId, String barName) as before.
The patch is to, the the renderSQL() method of QueryTranslator, replace
<snip>
Class[] classes = new Class[types.length];
for ( int i=0; i<types.length; i++ ) {
if ( types[i]!=null ) classes[i] = (types[i] instanceof PrimitiveType) ?
( (PrimitiveType) types[i] ).getPrimitiveClass() :
types[i].getReturnedClass();
}
try {
if (holderClass!=null) holderConstructor = holderClass.getConstructor(classes);
}
catch (NoSuchMethodException nsme) {
throw new QueryException("could not find constructor for: " + holderClass.getName(), nsme);
}
<snip>
with
<snip>
Class[] primitiveClasses = new Class[types.length];
Class[] classes = new Class[types.length];
for ( int i=0; i<types.length; i++ ) {
if ( types[i]!=null ) primitiveClasses[i] = (types[i] instanceof PrimitiveType) ?
( (PrimitiveType) types[i] ).getPrimitiveClass() :
types[i].getReturnedClass();
if ( types[i]!=null ) classes[i] = types[i].getReturnedClass();
}
try {
if (holderClass!=null) holderConstructor = holderClass.getConstructor(primitiveClasses);
}
catch (NoSuchMethodException nsmex) {
try {
if (holderClass!=null) holderConstructor = holderClass.getConstructor(classes);
}
catch (NoSuchMethodException nsme) {
throw new QueryException("could not find constructor for: " + holderClass.getName(), nsme);
}
}
<snip>
I hope this feature can make it into 2.0 final cause I now rely on this feature quite a bit!
---------------------------------------------------------------------
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-10-29 01:25:35
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 28 Oct 2003 7:21 PM
fixed
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-430
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-430
Summary: bindNamedParamaterList() has braindead parser
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Versions:
2.0rc2
2.1
2.0 final
2.0.1
2.0.2
2.0.3
2.1 beta 1
2.1 beta 2
2.1 beta 3
2.1 final
2.1 beta 4
2.1 beta 5
Assignee: Gavin King
Reporter: Gavin King
Created: Tue, 28 Oct 2003 4:19 PM
Updated: Tue, 28 Oct 2003 7:21 PM
Description:
http://forum.hibernate.org/viewtopic.php?p=2176068#2176068
---------------------------------------------------------------------
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-10-28 22:22:11
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-430 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-430 Summary: bindNamedParamaterList() has braindead parser Type: Bug Status: Assigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0rc2 2.1 2.0 final 2.0.1 2.0.2 2.0.3 2.1 beta 1 2.1 beta 2 2.1 beta 3 2.1 final 2.1 beta 4 2.1 beta 5 Assignee: Gavin King Reporter: Gavin King Created: Tue, 28 Oct 2003 4:19 PM Updated: Tue, 28 Oct 2003 4:19 PM Description: http://forum.hibernate.org/viewtopic.php?p=2176068#2176068 --------------------------------------------------------------------- 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-10-28 22:15:00
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 28 Oct 2003 4:11 PM
Thanks. Fixed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-429
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-429
Summary: Mistyped "line.separator" property name in ExceptionUtils class
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Versions:
2.1 beta 5
Assignee:
Reporter: Roustem Karimov
Created: Tue, 28 Oct 2003 3:52 PM
Updated: Tue, 28 Oct 2003 4:11 PM
Description:
The property name is mistyped as "line.seperator":
private static final String LINE_SEPARATOR = System.getProperty("line.seperator");
This causes a NullPointerException in ExceptionUtils.getStackFrames() method.
---------------------------------------------------------------------
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-10-28 22:03:18
|
The following comment has been added to this issue:
Author: Roustem Karimov
Created: Tue, 28 Oct 2003 4:01 PM
Body:
Here is the list of system properties:
http://java.sun.com/docs/books/tutorial/essential/system/properties.html
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-429
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-429
Summary: Mistyped "line.separator" property name in ExceptionUtils class
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 beta 5
Assignee:
Reporter: Roustem Karimov
Created: Tue, 28 Oct 2003 3:52 PM
Updated: Tue, 28 Oct 2003 3:52 PM
Description:
The property name is mistyped as "line.seperator":
private static final String LINE_SEPARATOR = System.getProperty("line.seperator");
This causes a NullPointerException in ExceptionUtils.getStackFrames() method.
---------------------------------------------------------------------
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-10-28 21:53:32
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-429 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-429 Summary: Mistyped "line.separator" property name in ExceptionUtils class Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 beta 5 Assignee: Reporter: Roustem Karimov Created: Tue, 28 Oct 2003 3:52 PM Updated: Tue, 28 Oct 2003 3:52 PM Description: The property name is mistyped as "line.seperator": private static final String LINE_SEPARATOR = System.getProperty("line.seperator"); This causes a NullPointerException in ExceptionUtils.getStackFrames() method. --------------------------------------------------------------------- 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-10-28 21:49:30
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Tue, 28 Oct 2003 3:48 PM
This was actually by design. But last night a few hours before you submitted this I finally changed my mind and changed it to throw exceptions.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-427
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-427
Summary: HBM.XML Parsing Errors do not throw an Exception
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Urberg
Created: Tue, 28 Oct 2003 7:39 AM
Updated: Tue, 28 Oct 2003 3:48 PM
Environment: JDK 1.4.1_01, Windows 2000
Description:
If the hbm.xml file contains invalid XML, Hibernate is only logging the parsing failure. It does not throw an exception.
It looks as if Configuration.addInputStream() should throw the MappingException which should be passed up from the XMLHelper.ErrorLogger.
A workaround is to add a filter to the Log4j appenders that looks for the log entry for the "Error parsing XML: " entry.
---------------------------------------------------------------------
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-10-28 18:40:33
|
The following issue has been updated:
Updater: Finn McCann (mailto:mc...@du...)
Date: Tue, 28 Oct 2003 12:38 PM
Comment:
Patch file to v2003. Three files affected.
Changes:
Attachment changed to informix_patch_to_v2003.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-414&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-414
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-414
Summary: Informix dialect creates syntax errors in IDS 9.4
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Versions:
2.0.2
Assignee: Max Rydahl Andersen
Reporter: Finn McCann
Created: Tue, 21 Oct 2003 11:01 AM
Updated: Tue, 28 Oct 2003 12:38 PM
Environment: Hibernate2 on JDK1.4 on Win2000, talking via Informix JDBC 2.21.JC5 driver to Informix IDS 9.4 on another Windows 2000 box.
Description:
Having tested Informix dialect in Hibernate2 against Informix IDS v9.4, we found a couple of issues:
1. Serial ids:
<id name="id" column="ID" length="32" unsaved-value="null">
<generator class="uuid.hex"/>
</id>
creates a data type:
INT8 SERIAL
instead of:
SERIAL8
The "INT8 SERIAL" causes a syntax error in IDS 9.4.
2. Foreign Key constraint names:
<set name="upliftRates" lazy="true" cascade="all" order-by="EFFECTIVE_DATE desc">
<key column="NETWORK_ID" length="32"/>
<one-to-many class="com.capetechnologies.multinet.domain.UpliftRate"/>
</set>
creates this ALTER TABLE statement:
alter table MULTINET_TAX_RATES add constraint FKE1700D046924EC foreign key (NETWORK_ID) references MULTINET_NETWORK
instead of:
alter table MULTINET_TAX_RATES add constraint foreign key (NETWORK_ID) references MULTINET_NETWORK constraint FKE1700D046924EC
Having "CONSTRAINT <constraint name>" within the statement instead of at the end causes a syntax error.
This also applies to adding UNIQUE CONSTRAINTs.
---------------------------------------------------------------------
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-10-28 16:17:26
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-428 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-428 Summary: Update OSCache support to support properties Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: Mathias Bogaert Created: Tue, 28 Oct 2003 10:16 AM Updated: Tue, 28 Oct 2003 10:16 AM Description: I've added support for various parameters. Also added a method to clear all cached, this can be used from eg. WebWork action. --------------------------------------------------------------------- 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-10-28 16:17:14
|
The following issue has been updated:
Updater: Mathias Bogaert (mailto:pa...@pa...)
Date: Tue, 28 Oct 2003 10:16 AM
Changes:
Attachment changed to oscache.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-428&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-428
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-428
Summary: Update OSCache support to support properties
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Mathias Bogaert
Created: Tue, 28 Oct 2003 10:16 AM
Updated: Tue, 28 Oct 2003 10:16 AM
Description:
I've added support for various parameters. Also added a method to clear all cached, this can be used from eg. WebWork action.
---------------------------------------------------------------------
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-10-28 13:42:46
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-427 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-427 Summary: HBM.XML Parsing Errors do not throw an Exception Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 4 Assignee: Reporter: John Urberg Created: Tue, 28 Oct 2003 7:39 AM Updated: Tue, 28 Oct 2003 7:39 AM Environment: JDK 1.4.1_01, Windows 2000 Description: If the hbm.xml file contains invalid XML, Hibernate is only logging the parsing failure. It does not throw an exception. It looks as if Configuration.addInputStream() should throw the MappingException which should be passed up from the XMLHelper.ErrorLogger. A workaround is to add a filter to the Log4j appenders that looks for the log entry for the "Error parsing XML: " entry. --------------------------------------------------------------------- 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-10-27 23:46:47
|
The following issue has been updated:
Updater: John Kristian (mailto:jkr...@do...)
Date: Mon, 27 Oct 2003 5:46 PM
Comment:
listener.zip (attached) contains one possible implementation, in the style of JavaBean event handling, with a new event class and listener interface, and a patch (session.diff-u) to pass the session to the listeners.
Changes:
Attachment changed to listener.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-426&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-426
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-426
Summary: Enable observation of StaleObjectStateException
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Kristian
Created: Mon, 27 Oct 2003 11:46 AM
Updated: Mon, 27 Oct 2003 5:46 PM
Description:
Please enable application software to take action whenever optimistic concurrency control fails (for example, whenever a database change fails because the version of an affected row is different from the version last read). As I understand it, whenever Hibernate detects this it throws a StaleObjectStateException, which is helpful. But StaleObjectStateException might propagate from any one of many Hibernate methods, which makes it difficult for an application to observe it.
I'd like one method in my application to be called whenever Hibernate throws a StaleObjectStateException. (In my application, that method will evict stale entries from the global cache, using an algorithm that's too expensive to execute more frequently.)
A related forum thread: http://forum.hibernate.org/viewtopic.php?t=925032
The Observer pattern (from 'Design Patterns') seems applicable here.
---------------------------------------------------------------------
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-10-27 21:27:58
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Mon, 27 Oct 2003 3:23 PM
Fixed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-348
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-348
Summary: Pulling Named Native Sql Queries from an xml file
Type: New Feature
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1 beta 5
Assignee: Max Rydahl Andersen
Reporter: Christopher D Riccio
Created: Fri, 19 Sep 2003 7:09 AM
Updated: Mon, 27 Oct 2003 3:23 PM
Environment: Currently using Hibernate 2.1 B3
Description:
This is my first time doing something like this so please bare with me. I will attach my code after creation of this issue.
I built 2 classes that handle the pulling of named sql queries. I modeled the namedQueries.xml file after the example on the Hibernate Road Map.
I tried to model my code after what was in the Configuration class that was written by Gavin. I also put in all the same versions of configure() that are in Configuration.
Currently I have not actually integrated the code into my version of Hibernate. I noticed that Hibernate's JCASessionImpl class has a getNamedQuery( String ). I'm not sure if this was created for the purpose, but I tried to follow along to what that is then put a "queryManager" Map in where I had my SessionFactory after creation. To load the query I would just do something like this...
NamedQuery nQuery = getNamedQuery( queryName );
Query query = session.createSQLQuery( nQuery.getQuery(), nQuery.getAliases(), nQuery.getClasses() );
There are 2 classes, NamedQuery which after looking at will be pretty self explanatory and NamedQueryConfiguration. When I was looking for code to model after in Hibernate, Configuration was the first thing to come to mind since it also loaded an xml file, so I tried to use all the same naming conventions, and even comments, as it did.
Biggest difference, NamedQueryConfiguration returns a Map. The Map contains key - value pairs of queryName - NamedQuery. This way, after the NamedQueryConfiguration.configure() is called, then the map can just be set in the JCASessionImpl. Then call getNamedQuery and let it do the small code snippet above.
I hope this all makes sense and isn't overkill on the information. Please let me know if there is any code or that needs to be changed based on naming, exception handling and any other coding standards.
Thanx,
Christopher D Riccio
---------------------------------------------------------------------
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-10-27 21:05:42
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Mon, 27 Oct 2003 2:58 PM
closing this ;)
(and just to elaborate - chaining exceptions is A Good Thing ;),
and that is what Nestable exceptions bring to the table - right ?
So, if you need some mechanism for "marking" Exceptions as "wrapping-only" then it should be done via some other stuff - eg. a WrapperOnly Marking interface ...but then again - that also got problems ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-424
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-424
Summary: Exception wrappers should not add a message
Type: Patch
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Kristian
Created: Thu, 23 Oct 2003 7:39 PM
Updated: Mon, 27 Oct 2003 2:58 PM
Description:
The attached patch would be an improvement, from my point of view.
Exception classes that merely wrap another exception should not add anything to the message. One reason is to simplify the implementation of code like this, which aims to remove such wrappers:
if (t instanceof Nestable || t instanceof InvocationTargetException || t instanceof UndeclaredThrowableException) {
cause = t.getCause();
if (cause != null) {
String message = t.getMessage();
if (message != null && message.length() > 0
&& ! message.equals(cause.getMessage()))
{
return t;
}
}
} else if (t instanceof etc...
Such code need not require special cases for Hibernate exceptions, if they refrain from adding to the message (as in the attached patch).
---------------------------------------------------------------------
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.
