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-07 16:12:22
|
The following issue has been updated:
Updater: xfgdf (mailto:sa...@ho...)
Date: Tue, 7 Oct 2003 11:12 AM
Changes:
Attachment changed to Value.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-173
Summary: Access to <meta> with the API
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Assignee:
Reporter: xfgdf
Created: Thu, 10 Jul 2003 7:21 AM
Updated: Tue, 7 Oct 2003 11:12 AM
Description:
It would be great to access to the <meta> elements with the API. Something like :
String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...
May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.
Adrien
---------------------------------------------------------------------
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-07 16:12:20
|
The following issue has been updated:
Updater: xfgdf (mailto:sa...@ho...)
Date: Tue, 7 Oct 2003 11:12 AM
Changes:
Attachment changed to Property.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-173
Summary: Access to <meta> with the API
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Assignee:
Reporter: xfgdf
Created: Thu, 10 Jul 2003 7:21 AM
Updated: Tue, 7 Oct 2003 11:12 AM
Description:
It would be great to access to the <meta> elements with the API. Something like :
String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...
May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.
Adrien
---------------------------------------------------------------------
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-07 16:12:20
|
The following issue has been updated:
Updater: xfgdf (mailto:sa...@ho...)
Date: Tue, 7 Oct 2003 11:11 AM
Changes:
Attachment changed to Binder.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-173
Summary: Access to <meta> with the API
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Assignee:
Reporter: xfgdf
Created: Thu, 10 Jul 2003 7:21 AM
Updated: Tue, 7 Oct 2003 11:11 AM
Description:
It would be great to access to the <meta> elements with the API. Something like :
String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...
May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.
Adrien
---------------------------------------------------------------------
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-07 08:14:21
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Tue, 7 Oct 2003 3:13 AM
No user response - consider it fixed
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-372
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-372
Summary: hbm2java generates two default constructors
Type: Bug
Status: Closed
Priority: Major
Resolution: CANNOT REPRODUCE
Project: Hibernate2
Components:
toolset
Fix Fors:
2.1
Assignee: Max Rydahl Andersen
Reporter: Les Hazlewood
Created: Tue, 30 Sep 2003 1:10 PM
Updated: Tue, 7 Oct 2003 3:13 AM
Environment: Linux, w/ ant 1.5.1
Description:
The following mapping generates a class with two default constructors, and therefore compilation fails:
<hibernate-mapping>
<class name="com.foobar.db.Testing" table="test_test_test">
<id name="id" type="string" unsaved-value="null" >
<column name="CAT_ID" sql-type="char(32)" not-null="true"/>
<generator class="uuid.hex"/>
</id>
<property name="name" type="string" not-null="true">
<column name="NAME" sql-type="varchar(16)"/>
</property>
</class>
</hibernate-mapping>
---------------------------------------------------------------------
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-06 21:30:22
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-382 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-382 Summary: Make Hibernate Friendlier for use of Proxies and Enhanced Classes Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 final Assignee: Reporter: James House Created: Mon, 6 Oct 2003 4:29 PM Updated: Mon, 6 Oct 2003 4:29 PM Description: Hibernate could become friendly to applications that make use of proxies and byte-code enchanced classes in their object models. To do so, only a couple simple new features are needed: 1) Add a construct (new method) to Configuration that lets you relate one class's mappings to another (i.e. tell Hibernate that: if you ever have to persist this class, act as if it is this other class that you already have mappings for). - This will serve to tell Hibernate that the enhanced class (who's class name is only known at run-time) should be persisted using the mappings of the original class. Note that in this case, the enhanced class only has changed behavior - no new properties. 2) Add a construct to relate a "factory" to a class's mappings, from which Hibernate should produce new instances of that class during load() operations. - This will server to tell Hibernate that it should create a new instance of a class (during load()) using the given factory, rather than using the default constructor. This way Hibernate can produce enhanced or proxied or even just sub-classes of objects without being aware of it. This feature would also be useful to other people, who simply need the object to be created a special way. I'd be happy to donate this work if it would be accepted - just let me know (either as a comment to this issue, or via e-mail) that it will be worth my time to do the work. james --------------------------------------------------------------------- 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-06 08:37:23
|
The following comment has been added to this issue:
Author: Andrei Pavlenko
Created: Mon, 6 Oct 2003 3:36 AM
Body:
Still not working.
List list = ses.find("from AttributeValue as attributeValue where attributeValue.elementId = ? and attributeValue.attributeId = ?", new Object[]{new Long(9001), new Long(9001)}, new Type[]{Hibernate.LONG, Hibernate.LONG});
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-374
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-374
Summary: Wrong SQL statement with field "elementId"
Type: Bug
Status: Unassigned
Priority: Blocker
Project: Hibernate2
Versions:
2.0.3
Assignee:
Reporter: Andrei Pavlenko
Created: Wed, 1 Oct 2003 9:32 AM
Updated: Wed, 1 Oct 2003 9:36 AM
Environment: Sybase
Description:
I have "composite-id" with two fields.
I want to create "many-to-one" reference for field "elementId" but generated by Hibernate SQL query is incorrect.
When I change column name to "elementOwnerId" it is generated correctly.
See attached files.
Wrong SQL:
select attribut0_.attributeId as attributeId, attribut0_.elementId as elementId, attribut0_.possibleAttributeValueId as possible3_, attribut0_.attributeValueFreeText as attribut4_, attribut0_.attributeId as attribut1_, attribut0_.elementId as elementId from AttributeValue attribut0_ where (attribut0_.elementId=? )and(attribut0_.attributeId=? )
Error message:
Select expression results in more than one column having same name. Column name 'elementId' is specified more than once
---------------------------------------------------------------------
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-04 14:39:20
|
The following issue has been updated:
Updater: David Morris (mailto:dmm...@ce...)
Date: Sat, 4 Oct 2003 9:38 AM
Comment:
Here is the updated SettingsFactory patch using reflection.
Changes:
Attachment changed to SettingsFactory.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-380
Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:02 AM
Updated: Sat, 4 Oct 2003 9:38 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.
Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.
---------------------------------------------------------------------
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-04 13:50:20
|
The following comment has been added to this issue:
Author: David Morris
Created: Sat, 4 Oct 2003 8:48 AM
Body:
Is there some way to specify database with Hibernate at the mapping level? If not, I wish you would reconsider this. In the past, if I assigned a Schema to MySql it used dot notation, which allowed me to specify a database name for the schema. This change broke that.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-381
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-381
Summary: The Schema/Table seperator for MySql Dialect is not working
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:16 AM
Updated: Sat, 4 Oct 2003 4:01 AM
Environment: MySql 4.0.14 running on Windows with Hibernate 2.1Beta4
Description:
Recently a getSchemaSeperator() method was added to the MySql dialect and it returns an underscore (_) but should return a dot (.).
---------------------------------------------------------------------
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-04 13:40:20
|
The following comment has been added to this issue:
Author: David Morris
Created: Sat, 4 Oct 2003 8:39 AM
Body:
I will change the call to use reflection and resubmit the patch.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-380
Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:02 AM
Updated: Sat, 4 Oct 2003 1:05 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.
Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.
---------------------------------------------------------------------
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-04 09:10:23
|
The following comment has been added to this issue:
Author: Gavin King
Created: Sat, 4 Oct 2003 4:10 AM
Body:
DatabaseMetadata.supportsGetGeneratedKeys()
is not available in JDBC 2.0.
Otherwise the patch looks reasonable (though it appears that some stuff might be able to be refactored up to AbstractEntityPersister, perhaps).
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-380
Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:02 AM
Updated: Sat, 4 Oct 2003 1:05 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.
Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.
---------------------------------------------------------------------
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-04 09:02:20
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sat, 4 Oct 2003 4:01 AM
It works just fine. The whole point of this patch is that MySQL has no schemas. So we "emulate" them
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-381
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-381
Summary: The Schema/Table seperator for MySql Dialect is not working
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:16 AM
Updated: Sat, 4 Oct 2003 4:01 AM
Environment: MySql 4.0.14 running on Windows with Hibernate 2.1Beta4
Description:
Recently a getSchemaSeperator() method was added to the MySql dialect and it returns an underscore (_) but should return a dot (.).
---------------------------------------------------------------------
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-04 06:17:32
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-381 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-381 Summary: The Schema/Table seperator for MySql Dialect is not working Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: David Morris Created: Sat, 4 Oct 2003 1:16 AM Updated: Sat, 4 Oct 2003 1:16 AM Environment: MySql 4.0.14 running on Windows with Hibernate 2.1Beta4 Description: Recently a getSchemaSeperator() method was added to the MySql dialect and it returns an underscore (_) but should return a dot (.). --------------------------------------------------------------------- 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-04 06:06:28
|
The following issue has been updated:
Updater: David Morris (mailto:dmm...@ce...)
Date: Sat, 4 Oct 2003 1:05 AM
Comment:
Patch to add getGeneratedKeys support built over 2.1Beta4 release because SourceForge was experiencing problems.
Changes:
Attachment changed to getGeneratedKeys.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-380
Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:02 AM
Updated: Sat, 4 Oct 2003 1:05 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.
Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.
---------------------------------------------------------------------
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-04 06:02:22
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-380 Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: David Morris Created: Sat, 4 Oct 2003 1:02 AM Updated: Sat, 4 Oct 2003 1:02 AM Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys. Description: Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers. --------------------------------------------------------------------- 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-03 20:53:23
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-379 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-379 Summary: IN clause in an HQL query confuses the preprocessor. Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: Bulent Erdemir Created: Fri, 3 Oct 2003 3:52 PM Updated: Fri, 3 Oct 2003 3:52 PM Description: check the related forum postings for detailed information at: http://forum.hibernate.org/viewtopic.php?p=2173569&sid=298fed84e2b015aff203a1f1bd83ab80#2173569 For queries having an IN clause, this confuses the preprocessor and causes hibernate to call getImportedClass() in QueryTranslator.concreteQueries() for each token in the query. This also causes long parsing time especially noticeable when running hibernate code under Jboss in which a different classloader is used. --------------------------------------------------------------------- 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-03 18:14:22
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@in...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-291 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-291 Summary: support for select for update request for oracle on queries Type: New Feature Status: Assigned Priority: Major Project: Hibernate2 Components: core Assignee: Gavin King Reporter: luc Created: Tue, 26 Aug 2003 2:38 AM Updated: Fri, 3 Oct 2003 1:13 PM Description: See the following post: http://sourceforge.net/forum/forum.php?thread_id=922434&forum_id=128638 Thanks a lot --------------------------------------------------------------------- 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-03 17:56:19
|
The following comment has been added to this issue:
Author: tekno
Created: Fri, 3 Oct 2003 12:56 PM
Body:
I just tried out beta4 and the assertion exception is gone. However, eventhough the test code works now, my code doesn't and throws a LazyInitializationException. I imagine if you modified the classes to have a set relationship you will find this but I have not tested it ( maybe after the weekend)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-377
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-377
Summary: Hibernate 2.1 appears to break jcs caching
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: tekno
Created: Thu, 2 Oct 2003 4:34 AM
Updated: Thu, 2 Oct 2003 4:34 AM
Environment: Development Windows 2000 SP3, JSDK 4.1.2
Deployment Solaris 9
Database Postgresql 7.3
Description:
I am getting an AssertionFailure - cannot cache a reference to an object with a null id when I try to do an update. Here is the sample code -
NB: This has been working fine for me in hibernate versions 2.0 - 2.03
I have the following two mappings
<class name="Customer" table="customers" polymorphism="explicit">
<cache usage="read-write"/>
<id name="id" unsaved-value="0">
<generator class="sequence">
<param name="sequence">customers_id_seq</param>
</generator>
</id>
<property name="postcode"/>
<many-to-one name="csOwner" class="Employee" column="cs_owner" />
</class>
and
<class name="Employee" table="staff">
<id name="id">
<generator class="sequence">
<param name="sequence">staff_id_seq</param>
</generator>
</id>
<property name="name"/>
</class>
the following main() throws the exception
Session session = null;
Customer customer = null;
SessionFactory factory = null;
try {
// build factory
factory = new Configuration().configure().buildSessionFactory();
System.out.println("Starting first session");
// first session gets customer instance
session = factory.openSession();
customer = (Customer) session.load(Customer.class, new Long(1275));
System.out.println("Loaded customer " + customer.getId() + " has owner " + customer.getCsOwner().getId());
session.flush();
session.connection().commit();
session.close();
System.out.println("Updating address field");
// update a field
customer.setPostcode("TESTING");
System.out.println("Starting second session");
// second session persists update
session = factory.openSession();
session.update(customer);
session.flush();
session.connection().commit();
session.close();
System.out.println("Finished");
factory.close();
} catch (Exception ex){
ex.printStackTrace();
} finally {
if(session!=null)session.close();
if(factory!=null)factory.close();
System.exit(0);
}
If i remove the cache entry in the customer mapping everything is OK, but other wise i get
net.sf.hibernate.AssertionFailure: cannot cache a reference to an object with a null id
at net.sf.hibernate.type.EntityType.disassemble(EntityType.java:89)
at net.sf.hibernate.impl.CacheEntry.disassemble(CacheEntry.java:36)
at net.sf.hibernate.impl.CacheEntry.<init>(CacheEntry.java:27)
at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:42)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2278)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2235)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2178)
at com.lab.model.HibBug.main(HibBug.java:46)
---------------------------------------------------------------------
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-03 14:52:21
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-378 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-378 Summary: error generate SQL from a HQL who use LEFT JOIN(on more levels) Type: Bug Status: Unassigned Priority: Blocker 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 Assignee: Reporter: Adrian Minciuna Created: Fri, 3 Oct 2003 9:51 AM Updated: Fri, 3 Oct 2003 9:51 AM Environment: Windows 2000 sp4, JDK 1.4.1_02 Description: Bug: i have 2 classes DACPerson and DACDepartment DACPerson has an inner object manager with DACPerson , and an object department with type DACDepartment. Thus, has 2 relations <many-to-one> I need an hql like this 1) using left join select als.name, als0.name, als1.name, als2.name from DACPerson as als left join als.manager as als0 left join als.manager.manager as als1 left join als.manager.department as als2 where als.pkid=als.hcod In this case hibernate generate a wrong SQL : select tstdacpe0_.PKID as x0_0_,tstdacde3_.NAME as x1_0_, tstdacpe2_.NAME as x2_0_, tstdacpe0_.NAME as x3_0_,tstdacpe1_.NAME as x4_0_ from PERSON2 tstdacpe0_ left outer join PERSON2 tstdacpe1_ on tstdacpe0_.MGR_ID=tstdacpe1_.PKID left outer join PERSON2 tstdacpe2_ on tstdacpe1_.MGR_ID=tstdacpe2_.PKID left outer join DEPT tstdacde3_ on tstdacpe1_.Dept_id=tstdacde3_.PKID where and and ((tstdacpe0_.PKID=tstdacpe0_.HCOD )) java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Incorrect syntax near the keyword 'and'. at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source) at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)..... ------------------------------------------- Obs. if i try a HQL,a little bit simple ex: select als.name, als0.name, als1.name from DACPerson as als left join als.manager as als0 left join als.manager.department as als1 where als.pkid=als.hcod i get following error FINE: net.sf.hibernate.hql.QueryTranslator.compile() - unexpected query compilation problem java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1480) at java.lang.String.substring(String.java:1447) at net.sf.hibernate.sql.QuerySelect.toQueryString(QuerySelect.java:109) at net.sf.hibernate.hql.QueryTranslator.renderSQL(QueryTranslator.java:515) at net.sf.hibernate.hql.QueryTranslator.compile(QueryTranslator.java:151) --------------------------------------------------------- 3) If i modify hql like this : select als.name, als0.name, als1.name, als2.name from DACPerson as als left join als.manager as als0 left join als0.manager as als1 left join als0.department as als2 where als.pkid=als.hcod and IT'S WORK fine --------------------------------------------------- Obs: i tested also on Hibern8 IDE --------------------------------------------------------------------- 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-03 11:06:46
|
The following comment has been added to this issue:
Author: tekno
Created: Fri, 3 Oct 2003 6:06 AM
Body:
The main method i use is
public static void main(String[] args) throws Exception {
Properties props = new Properties();
props.setProperty("hibernate.connection.driver_class", "org.postgresql.Driver");
props.setProperty("hibernate.connection.url", "jdbc:postgresql://lab-dev/LABDEV2");
props.setProperty("hibernate.connection.username", "postgres");
props.setProperty("hibernate.show_sql", "true");
Session session = null;
Customer customer = null;
SessionFactory factory = null;
try {
// build factory
Configuration cfg =
new Configuration().addClass(Customer.class).addClass(Employee.class).setProperties(props);
factory = cfg.buildSessionFactory();
System.out.println("Starting first session");// first session gets customer instance
session = factory.openSession();
customer = (Customer) session.load(Customer.class, new Long(1275));
System.out.println("Loaded customer " + customer.getId());
session.flush();
session.connection().commit();
session.close();
// update the title field
System.out.println("Updating field");
customer.setTitle("MR");
System.out.println("Starting second session");// second session persists update
session = factory.openSession();
session.update(customer);
session.flush();
session.connection().commit();
session.close();
System.out.println("Finished");
factory.close();
} catch (Exception ex) {
ex.printStackTrace();
} finally {
if (session != null)
session.close();
if (factory != null)
factory.close();
System.exit(0);
}
}
The Customer class is
public class Customer {
private long id;
private String title;
private Employee created;
public Customer() {
}
public void setId(long id) {
this.id = id;
}
public String getTitle() {
return title;
}
public void setTitle(String title) {
this.title = title;
}
public long getId() {
return id;
}
public Employee getCreated() {
return created;
}
public void setCreated(Employee employee) {
created = employee;
}
}
with mapping
<hibernate-mapping>
<class name="Customer" table="customers">
<jcs-cache usage="read-write"/>
<id name="id" unsaved-value="0">
<generator class="assigned"/>
</id>
<property name="title"/>
<many-to-one name="created" class="Employee" column="created_by"/>
</class>
</hibernate-mapping>
and the employee class is
public class Employee {
private long id;
private String name;
public Employee() {
}
public long getId() {
return id;
}
public String getName() {
return name;
}
public void setId(long id) {
this.id = id;
}
public void setName(String name) {
this.name = name;
}
}
with mapping
<hibernate-mapping>
<class name="Employee" table="staff">
<id name="id">
<generator class="assigned"/>
</id>
<property name="name"/>
</class>
</hibernate-mapping>
the ccf file i am using
jcs.default=DC
jcs.default.cacheattributes=org.apache.jcs.engine.CompositeCacheAttributes
jcs.default.cacheattributes.MaxObjects=2000
jcs.default.cacheattributes.MemoryCacheName=org.apache.jcs.engine.memory.lru.LRUMemoryCache
jcs.default.elementattributes=org.apache.jcs.engine.ElementAttributes
jcs.default.elementattributes.IsEternal=false
jcs.default.elementattributes.MaxLifeSeconds=24000
jcs.default.elementattributes.IdleTime=180000
jcs.default.elementattributes.IsSpool=false
jcs.default.elementattributes.IsRemote=false
jcs.default.elementattributes.IsLateral=false
The database tables I think are pretty obvious
customers with id,tile,created_by and staff with id, name
created_by is a foreign key joining customers to staff
I initialize the db with
insert into staff(id,name) values(1,'test');
insert into customers(id,title,created_by) values(1,'test',1);
what else do you need?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-377
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-377
Summary: Hibernate 2.1 appears to break jcs caching
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: tekno
Created: Thu, 2 Oct 2003 4:34 AM
Updated: Thu, 2 Oct 2003 4:34 AM
Environment: Development Windows 2000 SP3, JSDK 4.1.2
Deployment Solaris 9
Database Postgresql 7.3
Description:
I am getting an AssertionFailure - cannot cache a reference to an object with a null id when I try to do an update. Here is the sample code -
NB: This has been working fine for me in hibernate versions 2.0 - 2.03
I have the following two mappings
<class name="Customer" table="customers" polymorphism="explicit">
<cache usage="read-write"/>
<id name="id" unsaved-value="0">
<generator class="sequence">
<param name="sequence">customers_id_seq</param>
</generator>
</id>
<property name="postcode"/>
<many-to-one name="csOwner" class="Employee" column="cs_owner" />
</class>
and
<class name="Employee" table="staff">
<id name="id">
<generator class="sequence">
<param name="sequence">staff_id_seq</param>
</generator>
</id>
<property name="name"/>
</class>
the following main() throws the exception
Session session = null;
Customer customer = null;
SessionFactory factory = null;
try {
// build factory
factory = new Configuration().configure().buildSessionFactory();
System.out.println("Starting first session");
// first session gets customer instance
session = factory.openSession();
customer = (Customer) session.load(Customer.class, new Long(1275));
System.out.println("Loaded customer " + customer.getId() + " has owner " + customer.getCsOwner().getId());
session.flush();
session.connection().commit();
session.close();
System.out.println("Updating address field");
// update a field
customer.setPostcode("TESTING");
System.out.println("Starting second session");
// second session persists update
session = factory.openSession();
session.update(customer);
session.flush();
session.connection().commit();
session.close();
System.out.println("Finished");
factory.close();
} catch (Exception ex){
ex.printStackTrace();
} finally {
if(session!=null)session.close();
if(factory!=null)factory.close();
System.exit(0);
}
If i remove the cache entry in the customer mapping everything is OK, but other wise i get
net.sf.hibernate.AssertionFailure: cannot cache a reference to an object with a null id
at net.sf.hibernate.type.EntityType.disassemble(EntityType.java:89)
at net.sf.hibernate.impl.CacheEntry.disassemble(CacheEntry.java:36)
at net.sf.hibernate.impl.CacheEntry.<init>(CacheEntry.java:27)
at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:42)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2278)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2235)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2178)
at com.lab.model.HibBug.main(HibBug.java:46)
---------------------------------------------------------------------
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-03 10:10:25
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 3 Oct 2003 5:08 AM
Thanks Daniel!
OK, I have committed this to the 2.1 branch. Would you guys please re-test my committed code. TIA.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-365
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-365
Summary: TransactionManagerLookup for WebSphere 5.0
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 beta 4
Versions:
2.1
2.0.3
Assignee: Daniel Bradby
Reporter: Ralf Taugerbeck
Created: Fri, 26 Sep 2003 5:08 AM
Updated: Fri, 3 Oct 2003 5:08 AM
Environment: WebSphere 5.0
Description:
The TransactionManagerLookup issue on WebSphere 5.0 was already resolved in HB-240 but IMO the code should look as shown in the attached Patch.
BTW, there is no class "com.ibm.ejcs.jts.jta.JTSXA" in WAS 5.0
---------------------------------------------------------------------
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-03 09:56:30
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-371 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-371 Summary: Commit in SchemaUpdate Type: Bug Status: Closed Priority: Major Resolution: FIXED Project: Hibernate2 Components: toolset Fix Fors: 2.1 beta 4 Versions: 2.1 beta 3 Assignee: Reporter: xfgdf Created: Tue, 30 Sep 2003 10:29 AM Updated: Fri, 3 Oct 2003 4:55 AM Environment: JBoss 3.2 EJB stateless with container managed transaction. Oracle 8i with JdbcOdbc sun driver. Description: There is a call to commit() in Schema Update that throws an : java.sql.SQLException: You cannot commit with autocommit set! at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.jdbcCommit(BaseWrapperManagedConnection.java:494) at org.jboss.resource.adapter.jdbc.WrappedConnection.commit(WrappedConnection.java:465) at net.sf.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:99) If, for some reasons, this commit is necessary to access Metadata, Hibernate should call setAutocommit(false) before. Thanks... Adrien --------------------------------------------------------------------- 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-03 02:00:20
|
The following comment has been added to this issue:
Author: Daniel Bradby
Created: Thu, 2 Oct 2003 9:00 PM
Body:
I applied the patch and it now works fine in WAS 5.
Note the WAS 5 no longer supports the UserTransaction name of "jta/usertransaction" for Applications J2EE 1.3 and above, but is now using the default "java:comp/UserTransaction". Have we got somewhere that we could make this clear to the user?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-365
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-365
Summary: TransactionManagerLookup for WebSphere 5.0
Type: Patch
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1
2.0.3
Assignee: Daniel Bradby
Reporter: Ralf Taugerbeck
Created: Fri, 26 Sep 2003 5:08 AM
Updated: Sat, 27 Sep 2003 6:21 AM
Environment: WebSphere 5.0
Description:
The TransactionManagerLookup issue on WebSphere 5.0 was already resolved in HB-240 but IMO the code should look as shown in the attached Patch.
BTW, there is no class "com.ibm.ejcs.jts.jta.JTSXA" in WAS 5.0
---------------------------------------------------------------------
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-02 19:19:24
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 2 Oct 2003 2:18 PM
Body:
Would you please test against tomorrow morning's CVS snapshot. I have made a change that -should- fix this, but I'm not certain, since you didn't tell me exactly what you were -doing- that generated this SQL.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-374
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-374
Summary: Wrong SQL statement with field "elementId"
Type: Bug
Status: Unassigned
Priority: Blocker
Project: Hibernate2
Versions:
2.0.3
Assignee:
Reporter: Andrei Pavlenko
Created: Wed, 1 Oct 2003 9:32 AM
Updated: Wed, 1 Oct 2003 9:36 AM
Environment: Sybase
Description:
I have "composite-id" with two fields.
I want to create "many-to-one" reference for field "elementId" but generated by Hibernate SQL query is incorrect.
When I change column name to "elementOwnerId" it is generated correctly.
See attached files.
Wrong SQL:
select attribut0_.attributeId as attributeId, attribut0_.elementId as elementId, attribut0_.possibleAttributeValueId as possible3_, attribut0_.attributeValueFreeText as attribut4_, attribut0_.attributeId as attribut1_, attribut0_.elementId as elementId from AttributeValue attribut0_ where (attribut0_.elementId=? )and(attribut0_.attributeId=? )
Error message:
Select expression results in more than one column having same name. Column name 'elementId' is specified more than once
---------------------------------------------------------------------
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-02 19:19:23
|
The following issue has been updated:
Updater: Jason Carreira (mailto:jas...@no...)
Date: Thu, 2 Oct 2003 2:18 PM
Comment:
SwarmCache which works with SwarmCache 1.0RC2
Changes:
Attachment changed to SwarmCache.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-47
Summary: Clustered Read/Write Caching
Type: Patch
Status: Assigned
Priority: Critical
Project: Hibernate2
Fix Fors:
2.1
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:30 AM
Updated: Thu, 2 Oct 2003 2:18 PM
Description:
Clustered Read/Write Caching
This patch adds the ability to do read-write caching in
a clustered environment. This is accomplished by way of
the SwarmCache caching engine. It in turn uses
Javagroups to implement efficient, multicast-based
cache communication. You can read a detailed
description of SwarmCache at http://swarmcache.sf.net.
Included in the patch is a readme that explains how it
works and how to apply it.
John Watkinson
http://sourceforge.net/tracker/index.php?func=detail&aid=722039&group_id=40712&atid=428710
---------------------------------------------------------------------
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-02 19:19:22
|
The following issue has been updated:
Updater: Jason Carreira (mailto:jas...@no...)
Date: Thu, 2 Oct 2003 2:18 PM
Comment:
SwarmCacheProvider which works with SwarmCache 1.0RC2
Changes:
Attachment changed to SwarmCacheProvider.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-47
Summary: Clustered Read/Write Caching
Type: Patch
Status: Assigned
Priority: Critical
Project: Hibernate2
Fix Fors:
2.1
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:30 AM
Updated: Thu, 2 Oct 2003 2:18 PM
Description:
Clustered Read/Write Caching
This patch adds the ability to do read-write caching in
a clustered environment. This is accomplished by way of
the SwarmCache caching engine. It in turn uses
Javagroups to implement efficient, multicast-based
cache communication. You can read a detailed
description of SwarmCache at http://swarmcache.sf.net.
Included in the patch is a readme that explains how it
works and how to apply it.
John Watkinson
http://sourceforge.net/tracker/index.php?func=detail&aid=722039&group_id=40712&atid=428710
---------------------------------------------------------------------
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.
