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-12-10 22:39:16
|
The following comment has been added to this issue:
Author: Tim McCune
Created: Wed, 10 Dec 2003 4:39 PM
Body:
Then can this issue be changed from a patch to a bug and make SchemaExport inspect the database metadata to get the correct constraint names?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-540
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-540
Summary: SchemaExport drop fails if constraint names change
Type: Patch
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
toolset
Versions:
2.1 rc1
Assignee:
Reporter: Tim McCune
Created: Wed, 10 Dec 2003 1:06 PM
Updated: Wed, 10 Dec 2003 4:39 PM
Environment: Linux, JDK 1.4, Postgres
Description:
Hibernate doesn't use a cascading drop to drop tables. Instead, it tries to remove constraints and then drop the table. However, it seems to be getting the wrong constraint names. Maybe it's trying to drop the constraints with the name that it's about to generate instead of inspecting the database meta data to get the list of existing constraint names?
I have table foo with foreign key constraint fk124fae0f5c6729a (hibernate-generated).
Running schema export produces this:
alter table foo drop constraint FK124FAE0F5C6729A;
drop table foo;
drop sequence hibernate_sequence;
create table Foo (
id INT8 not null,
bar VARCHAR(255) not null,
primary key (id)
);
ERROR - Unsuccessful: create table Foo (id INT8 not null, bar VARCHAR(255) not null, primary key (id))
ERROR - ERROR: Relation 'foo' already exists
Notice that the constraint name that SchemaExport is trying to drop doesn't even exist. SchemaExport should either get the constraint names from the database metadata or just do a cascading drop. I'm attaching a patch to do the cascade, which is what I'm using locally.
---------------------------------------------------------------------
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-12-10 22:35:17
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 10 Dec 2003 4:35 PM
We can't apply this patch since older versions of Postgres don't support the cascade syntax.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-540
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-540
Summary: SchemaExport drop fails if constraint names change
Type: Patch
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
toolset
Versions:
2.1 rc1
Assignee:
Reporter: Tim McCune
Created: Wed, 10 Dec 2003 1:06 PM
Updated: Wed, 10 Dec 2003 4:35 PM
Environment: Linux, JDK 1.4, Postgres
Description:
Hibernate doesn't use a cascading drop to drop tables. Instead, it tries to remove constraints and then drop the table. However, it seems to be getting the wrong constraint names. Maybe it's trying to drop the constraints with the name that it's about to generate instead of inspecting the database meta data to get the list of existing constraint names?
I have table foo with foreign key constraint fk124fae0f5c6729a (hibernate-generated).
Running schema export produces this:
alter table foo drop constraint FK124FAE0F5C6729A;
drop table foo;
drop sequence hibernate_sequence;
create table Foo (
id INT8 not null,
bar VARCHAR(255) not null,
primary key (id)
);
ERROR - Unsuccessful: create table Foo (id INT8 not null, bar VARCHAR(255) not null, primary key (id))
ERROR - ERROR: Relation 'foo' already exists
Notice that the constraint name that SchemaExport is trying to drop doesn't even exist. SchemaExport should either get the constraint names from the database metadata or just do a cascading drop. I'm attaching a patch to do the cascade, which is what I'm using locally.
---------------------------------------------------------------------
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-12-10 22:31:17
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-539 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-539 Summary: Schema Type: Patch Status: Closed Priority: Major Resolution: INCOMPLETE Project: Hibernate2 Assignee: Reporter: Tim McCune Created: Wed, 10 Dec 2003 12:59 PM Updated: Wed, 10 Dec 2003 4:30 PM Description: --------------------------------------------------------------------- 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-12-10 19:12:19
|
The following comment has been added to this issue:
Author: Tim McCune
Created: Wed, 10 Dec 2003 1:11 PM
Body:
Sorry, I just noticed that in my description, the constraint names were the same. :) That was a copy/paste error. The names it is using really are different.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-540
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-540
Summary: SchemaExport drop fails if constraint names change
Type: Patch
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.1 rc1
Assignee:
Reporter: Tim McCune
Created: Wed, 10 Dec 2003 1:06 PM
Updated: Wed, 10 Dec 2003 1:11 PM
Environment: Linux, JDK 1.4, Postgres
Description:
Hibernate doesn't use a cascading drop to drop tables. Instead, it tries to remove constraints and then drop the table. However, it seems to be getting the wrong constraint names. Maybe it's trying to drop the constraints with the name that it's about to generate instead of inspecting the database meta data to get the list of existing constraint names?
I have table foo with foreign key constraint fk124fae0f5c6729a (hibernate-generated).
Running schema export produces this:
alter table foo drop constraint FK124FAE0F5C6729A;
drop table foo;
drop sequence hibernate_sequence;
create table Foo (
id INT8 not null,
bar VARCHAR(255) not null,
primary key (id)
);
ERROR - Unsuccessful: create table Foo (id INT8 not null, bar VARCHAR(255) not null, primary key (id))
ERROR - ERROR: Relation 'foo' already exists
Notice that the constraint name that SchemaExport is trying to drop doesn't even exist. SchemaExport should either get the constraint names from the database metadata or just do a cascading drop. I'm attaching a patch to do the cascade, which is what I'm using locally.
---------------------------------------------------------------------
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-12-10 19:09:17
|
The following issue has been updated:
Updater: Tim McCune (mailto:tm...@hm...)
Date: Wed, 10 Dec 2003 1:08 PM
Comment:
Patch
Changes:
Attachment changed to diff
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-540&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-540
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-540
Summary: SchemaExport drop fails if constraint names change
Type: Patch
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.1 rc1
Assignee:
Reporter: Tim McCune
Created: Wed, 10 Dec 2003 1:06 PM
Updated: Wed, 10 Dec 2003 1:08 PM
Environment: Linux, JDK 1.4, Postgres
Description:
Hibernate doesn't use a cascading drop to drop tables. Instead, it tries to remove constraints and then drop the table. However, it seems to be getting the wrong constraint names. Maybe it's trying to drop the constraints with the name that it's about to generate instead of inspecting the database meta data to get the list of existing constraint names?
I have table foo with foreign key constraint fk124fae0f5c6729a (hibernate-generated).
Running schema export produces this:
alter table foo drop constraint FK124FAE0F5C6729A;
drop table foo;
drop sequence hibernate_sequence;
create table Foo (
id INT8 not null,
bar VARCHAR(255) not null,
primary key (id)
);
ERROR - Unsuccessful: create table Foo (id INT8 not null, bar VARCHAR(255) not null, primary key (id))
ERROR - ERROR: Relation 'foo' already exists
Notice that the constraint name that SchemaExport is trying to drop doesn't even exist. SchemaExport should either get the constraint names from the database metadata or just do a cascading drop. I'm attaching a patch to do the cascade, which is what I'm using locally.
---------------------------------------------------------------------
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-12-10 19:07:18
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-540 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-540 Summary: SchemaExport drop fails if constraint names change Type: Patch Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.1 rc1 Assignee: Reporter: Tim McCune Created: Wed, 10 Dec 2003 1:06 PM Updated: Wed, 10 Dec 2003 1:06 PM Environment: Linux, JDK 1.4, Postgres Description: Hibernate doesn't use a cascading drop to drop tables. Instead, it tries to remove constraints and then drop the table. However, it seems to be getting the wrong constraint names. Maybe it's trying to drop the constraints with the name that it's about to generate instead of inspecting the database meta data to get the list of existing constraint names? I have table foo with foreign key constraint fk124fae0f5c6729a (hibernate-generated). Running schema export produces this: alter table foo drop constraint FK124FAE0F5C6729A; drop table foo; drop sequence hibernate_sequence; create table Foo ( id INT8 not null, bar VARCHAR(255) not null, primary key (id) ); ERROR - Unsuccessful: create table Foo (id INT8 not null, bar VARCHAR(255) not null, primary key (id)) ERROR - ERROR: Relation 'foo' already exists Notice that the constraint name that SchemaExport is trying to drop doesn't even exist. SchemaExport should either get the constraint names from the database metadata or just do a cascading drop. I'm attaching a patch to do the cascade, which is what I'm using locally. --------------------------------------------------------------------- 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-12-10 18:59:18
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-539 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-539 Summary: Schema Type: Patch Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Tim McCune Created: Wed, 10 Dec 2003 12:59 PM Updated: Wed, 10 Dec 2003 12:59 PM Description: --------------------------------------------------------------------- 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-12-10 15:02:17
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-538 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-538 Summary: Documentation incorrect for xDoclet jbossservice subtask Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Versions: 2.1 Assignee: Reporter: Roland Chan Created: Wed, 10 Dec 2003 9:01 AM Updated: Wed, 10 Dec 2003 9:01 AM Environment: Hibernate 2.1, w/ xDoclet 1.2b4 and CVS Head, and Maven RC1 Description: The document, http://www.hibernate.org/66.html, describes that with the release of 2.1 final there will be a need to add additional mbean properties to the jboss-service.xml that are not supported by hibernatedoclet. The method it uses to describe this is to create a merge file and add your elements there. This is incorrect and misleading since the new elements will be put outside the targeted mbean which is undesired since most users will want the elements to be part of the hibernate factory mbean. Hopefully fixing this doc will save someone else some time. Moreover, there is support for an additional <depends> element, however, I have yet to get this to work correctly. --------------------------------------------------------------------- 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-12-10 12:41:17
|
The following comment has been added to this issue:
Author: David R Robison
Created: Wed, 10 Dec 2003 6:39 AM
Body:
The problem turned out to be that I had a compound key that referenced a row in another table that also had a compound key. however, the individual columns making up the key were not in a consistent order. In the referenced table the compound primary key was columns A and B, but in the referencing table, the compound primary key was column C, B, and A. The fact that the A and B columns were reversed in order seemed to be the problem.
I hope this makes sence.
David Robison
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-526
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-526
Summary: Problem finding records with compound primary keys
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1 rc1
Assignee:
Reporter: David R Robison
Created: Fri, 5 Dec 2003 7:53 AM
Updated: Wed, 10 Dec 2003 6:39 AM
Environment: postgresql on W2K
Description:
I'm trying to find a record with a compound key. The following is my session.find call:
Session hbSession = HibernateSession.currentSession();
types = hbSession.find("from com.orci.ITSAM.hibernate.SegmentType sgType " +
"where sgType.comp_id.siteDatabase.comp_id.site = ? " +
"and sgType.comp_id.siteDatabase.comp_id.dbId = ? ",
new Object[] {
SiteDatabaseServices.MyDbSiteCode(context),
SiteDatabaseServices.MyDbId(context) },
new Type[] {
Hibernate.INTEGER,
Hibernate.INTEGER });
I'v set show_sql to true. When this line is executed, the following SQL statement prints:
select segmenttyp0_.sg_type_code as sg_type_1_, segmenttyp0_.sg_db_site as sg_db_site, segmenttyp0_.sg_db_id as sg_db_id, segmenttyp0_.name as name, segmenttyp0_.default_mnemonic as default_5_, segmenttyp0_.gmt_last_updated as gmt_last6_, segmenttyp0_.rstat_type_code as rstat_ty7_, segmenttyp0_.last_upd_db_site as last_upd8_, segmenttyp0_.last_upd_db_id as last_upd9_ from segment_type segmenttyp0_ where (segmenttyp0_.sg_db_id=? )and(segmenttyp0_.sg_db_site=? )
What is interesting is that the WHERE clause checks the site first and then the dbId but in the printed SQL statement, the WHERE clause is db_id first and then site. This causes problems with the parameters passed into the find call. Any ideas why the SQL WHERE clause is being rearanged?
Thanks,
David Robison
---------------------------------------------------------------------
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-12-10 12:15:16
|
The following comment has been added to this issue:
Author: Panagiotis Louridas
Created: Wed, 10 Dec 2003 6:14 AM
Body:
Would it help to add that comment in Section 12.1 of the reference documentation?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-537
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-537
Summary: Proxy Problem with overloaded functions
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee: Gavin King
Reporter: Panagiotis Louridas
Created: Wed, 10 Dec 2003 5:50 AM
Updated: Wed, 10 Dec 2003 6:14 AM
Environment: linux, Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28), hibernate 2.0.3, postgres.
Description:
Suppose we have class A and two subclasses A<-B, A<-C. Suppose now that B has methods Foo getFoo() and void setFoo(Foo), while C has methods Bar getFoo() and void setFoo(Bar).
I get strange proxy behaviour when working with objects of classes A, B, C. Specifically, when querying on B, C and then on A, I get
SEVERE: CGLIB Enhancement failed
java.lang.IllegalArgumentException: Can't implement:
InterestPayment
and
TaxPayment
(where InterestPayment = B and TaxPayment = C).
Everything works fine when querying on A and then on B and C, though.
---------------------------------------------------------------------
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-12-10 12:07:16
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 10 Dec 2003 6:06 AM
Body:
Yes. interface proxies are castable to the subclass type. but this won't work if you have two methods with conflicting return types on diff subclasses.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-537
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-537
Summary: Proxy Problem with overloaded functions
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee: Gavin King
Reporter: Panagiotis Louridas
Created: Wed, 10 Dec 2003 5:50 AM
Updated: Wed, 10 Dec 2003 6:06 AM
Environment: linux, Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28), hibernate 2.0.3, postgres.
Description:
Suppose we have class A and two subclasses A<-B, A<-C. Suppose now that B has methods Foo getFoo() and void setFoo(Foo), while C has methods Bar getFoo() and void setFoo(Bar).
I get strange proxy behaviour when working with objects of classes A, B, C. Specifically, when querying on B, C and then on A, I get
SEVERE: CGLIB Enhancement failed
java.lang.IllegalArgumentException: Can't implement:
InterestPayment
and
TaxPayment
(where InterestPayment = B and TaxPayment = C).
Everything works fine when querying on A and then on B and C, though.
---------------------------------------------------------------------
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-12-10 12:05:16
|
The following comment has been added to this issue:
Author: Panagiotis Louridas
Created: Wed, 10 Dec 2003 6:05 AM
Body:
Does this mean this is a feature?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-537
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-537
Summary: Proxy Problem with overloaded functions
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee: Gavin King
Reporter: Panagiotis Louridas
Created: Wed, 10 Dec 2003 5:50 AM
Updated: Wed, 10 Dec 2003 6:05 AM
Environment: linux, Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28), hibernate 2.0.3, postgres.
Description:
Suppose we have class A and two subclasses A<-B, A<-C. Suppose now that B has methods Foo getFoo() and void setFoo(Foo), while C has methods Bar getFoo() and void setFoo(Bar).
I get strange proxy behaviour when working with objects of classes A, B, C. Specifically, when querying on B, C and then on A, I get
SEVERE: CGLIB Enhancement failed
java.lang.IllegalArgumentException: Can't implement:
InterestPayment
and
TaxPayment
(where InterestPayment = B and TaxPayment = C).
Everything works fine when querying on A and then on B and C, though.
---------------------------------------------------------------------
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-12-10 12:00:17
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 10 Dec 2003 5:59 AM
Don't use interface proxies if you have this. Use the actual concrete classes as the proxy class.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-537
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-537
Summary: Proxy Problem with overloaded functions
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee: Gavin King
Reporter: Panagiotis Louridas
Created: Wed, 10 Dec 2003 5:50 AM
Updated: Wed, 10 Dec 2003 5:59 AM
Environment: linux, Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28), hibernate 2.0.3, postgres.
Description:
Suppose we have class A and two subclasses A<-B, A<-C. Suppose now that B has methods Foo getFoo() and void setFoo(Foo), while C has methods Bar getFoo() and void setFoo(Bar).
I get strange proxy behaviour when working with objects of classes A, B, C. Specifically, when querying on B, C and then on A, I get
SEVERE: CGLIB Enhancement failed
java.lang.IllegalArgumentException: Can't implement:
InterestPayment
and
TaxPayment
(where InterestPayment = B and TaxPayment = C).
Everything works fine when querying on A and then on B and C, though.
---------------------------------------------------------------------
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-12-10 11:54:17
|
The following issue has been updated:
Updater: Panagiotis Louridas (mailto:plo...@ya...)
Date: Wed, 10 Dec 2003 5:54 AM
Comment:
I attach two test cases showing the problem.
ant create-db; ant -Dtest.case=QueryProxyParentChildren test
succeeds, whereas
ant create-db; ant -Dtest.case=QueryProxyChildrenParent test
fails.
Changes:
Attachment changed to hibernate_report4.tar.gz
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-537&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-537
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-537
Summary: Proxy Problem with overloaded functions
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0.3
Assignee:
Reporter: Panagiotis Louridas
Created: Wed, 10 Dec 2003 5:50 AM
Updated: Wed, 10 Dec 2003 5:54 AM
Environment: linux, Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28), hibernate 2.0.3, postgres.
Description:
Suppose we have class A and two subclasses A<-B, A<-C. Suppose now that B has methods Foo getFoo() and void setFoo(Foo), while C has methods Bar getFoo() and void setFoo(Bar).
I get strange proxy behaviour when working with objects of classes A, B, C. Specifically, when querying on B, C and then on A, I get
SEVERE: CGLIB Enhancement failed
java.lang.IllegalArgumentException: Can't implement:
InterestPayment
and
TaxPayment
(where InterestPayment = B and TaxPayment = C).
Everything works fine when querying on A and then on B and C, though.
---------------------------------------------------------------------
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-12-10 11:51:16
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-537 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-537 Summary: Proxy Problem with overloaded functions Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0.3 Assignee: Reporter: Panagiotis Louridas Created: Wed, 10 Dec 2003 5:50 AM Updated: Wed, 10 Dec 2003 5:50 AM Environment: linux, Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28), hibernate 2.0.3, postgres. Description: Suppose we have class A and two subclasses A<-B, A<-C. Suppose now that B has methods Foo getFoo() and void setFoo(Foo), while C has methods Bar getFoo() and void setFoo(Bar). I get strange proxy behaviour when working with objects of classes A, B, C. Specifically, when querying on B, C and then on A, I get SEVERE: CGLIB Enhancement failed java.lang.IllegalArgumentException: Can't implement: InterestPayment and TaxPayment (where InterestPayment = B and TaxPayment = C). Everything works fine when querying on A and then on B and C, though. --------------------------------------------------------------------- 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-12-10 09:51:16
|
The following comment has been added to this issue:
Author: Konstantin Sharenkov
Created: Wed, 10 Dec 2003 3:50 AM
Body:
Thanks for help.
Currently i've replaced setters calling with direct assigns.
All works fine.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-535
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-535
Summary: 2.1 rc1 CGLIB2 Proxy Problems.
Type: Bug
Status: Open
Priority: Major
Project: Hibernate2
Versions:
2.1 rc1
Assignee: Gavin King
Reporter: Konstantin Sharenkov
Created: Tue, 9 Dec 2003 11:49 PM
Updated: Wed, 10 Dec 2003 3:50 AM
Environment: WinXP tomcat 4.1.27, jdk 1.4.1,
Description:
After i moved to 2.1 RC1 form 2.1 beta 3 i have following issue
if class is lazy
<class .... lazy="true">
and I obtain instance
obj = sess.load( XXX.class, ID )
if instance is proxy
1. obj.getId() always returns 0
2. getter for other persistent obj.getPersistent() always returns null
3. getter for persistent enum obj.getEnum() always return value for constant Enum.fromInt(0)
if i set lazy="false" ol works correct
if i use previous verison library all correct too.
the sample for id and Persistent Enum included
see User.getType, User.getId() and Screenshoots
---------------------------------------------------------------------
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-12-10 08:26:16
|
The following issue has been updated:
Updater: xfgdf (mailto:sa...@ho...)
Date: Wed, 10 Dec 2003 2:24 AM
Comment:
Second part of the correction.
Adrien
Changes:
Attachment changed to TableMetadata.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-534&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-534
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-534
Summary: Table schema use in DatabaseMetadata
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: xfgdf
Created: Tue, 9 Dec 2003 10:55 AM
Updated: Wed, 10 Dec 2003 2:24 AM
Environment: Hibernate 2.1 beta 4, Oracle 8i
Description:
When using SchemaUpdate, the DatabaseMetaData.getTableMetadata() looks for a table with the correct table name in any database schema and it take the first one it found. This behavior is uncorrect if I have a table existing in different schemas.
The correct behavior would be to first look in the schema with the login name and after in any schema.
user1.article
user2.article
I connected whith user2, DatabaseMetaData should first look for user2.article, then if not found to %.article.
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-12-10 07:46:17
|
The following issue has been updated:
Updater: Tim McCune (mailto:tm...@hm...)
Date: Wed, 10 Dec 2003 1:45 AM
Comment:
Here's the patch to fix it.
Changes:
Attachment changed to diff
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-536&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-536
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-536
Summary: SchemaExport is broken for jar files
Type: Patch
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.1 rc1
Assignee:
Reporter: Tim McCune
Created: Wed, 10 Dec 2003 1:45 AM
Updated: Wed, 10 Dec 2003 1:45 AM
Environment: Linux, JDK 1.4
Description:
<ant:schemaExport properties="${basedir}/project.properties" quiet="no" text="no" drop="no" delimiter=";">
<ant:fileset dir=".">
<ant:include name="foo.jar"/>
</ant:fileset>
</ant:schemaExport>
yields:
java.lang.NullPointerException
at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:322)
at net.sf.hibernate.tool.hbm2ddl.SchemaExportTask.getConfiguration(SchemaExportTask.java:182)
at net.sf.hibernate.tool.hbm2ddl.SchemaExportTask.execute(SchemaExportTask.java:131)
---------------------------------------------------------------------
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-12-10 07:46:17
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-536 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-536 Summary: SchemaExport is broken for jar files Type: Patch Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.1 rc1 Assignee: Reporter: Tim McCune Created: Wed, 10 Dec 2003 1:45 AM Updated: Wed, 10 Dec 2003 1:45 AM Environment: Linux, JDK 1.4 Description: <ant:schemaExport properties="${basedir}/project.properties" quiet="no" text="no" drop="no" delimiter=";"> <ant:fileset dir="."> <ant:include name="foo.jar"/> </ant:fileset> </ant:schemaExport> yields: java.lang.NullPointerException at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:322) at net.sf.hibernate.tool.hbm2ddl.SchemaExportTask.getConfiguration(SchemaExportTask.java:182) at net.sf.hibernate.tool.hbm2ddl.SchemaExportTask.execute(SchemaExportTask.java:131) --------------------------------------------------------------------- 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-12-10 07:25:17
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 10 Dec 2003 1:23 AM
Body:
This occurs because you call a method from the constructor, causing proxy initialization, and then re-initializing the value after Hibernate sets it.
I've asked the CGLIB guys if there is a change in how enhanced objects are initialized.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-535
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-535
Summary: 2.1 rc1 CGLIB2 Proxy Problems.
Type: Bug
Status: Open
Priority: Major
Project: Hibernate2
Versions:
2.1 rc1
Assignee: Gavin King
Reporter: Konstantin Sharenkov
Created: Tue, 9 Dec 2003 11:49 PM
Updated: Wed, 10 Dec 2003 1:23 AM
Environment: WinXP tomcat 4.1.27, jdk 1.4.1,
Description:
After i moved to 2.1 RC1 form 2.1 beta 3 i have following issue
if class is lazy
<class .... lazy="true">
and I obtain instance
obj = sess.load( XXX.class, ID )
if instance is proxy
1. obj.getId() always returns 0
2. getter for other persistent obj.getPersistent() always returns null
3. getter for persistent enum obj.getEnum() always return value for constant Enum.fromInt(0)
if i set lazy="false" ol works correct
if i use previous verison library all correct too.
the sample for id and Persistent Enum included
see User.getType, User.getId() and Screenshoots
---------------------------------------------------------------------
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-12-10 07:23:17
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@hi...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-535 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-535 Summary: 2.1 rc1 CGLIB2 Proxy Problems. Type: Bug Status: Open Priority: Major Project: Hibernate2 Versions: 2.1 rc1 Assignee: Gavin King Reporter: Konstantin Sharenkov Created: Tue, 9 Dec 2003 11:49 PM Updated: Wed, 10 Dec 2003 1:22 AM Environment: WinXP tomcat 4.1.27, jdk 1.4.1, Description: After i moved to 2.1 RC1 form 2.1 beta 3 i have following issue if class is lazy <class .... lazy="true"> and I obtain instance obj = sess.load( XXX.class, ID ) if instance is proxy 1. obj.getId() always returns 0 2. getter for other persistent obj.getPersistent() always returns null 3. getter for persistent enum obj.getEnum() always return value for constant Enum.fromInt(0) if i set lazy="false" ol works correct if i use previous verison library all correct too. the sample for id and Persistent Enum included see User.getType, User.getId() and Screenshoots --------------------------------------------------------------------- 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-12-10 06:47:16
|
The following issue has been updated:
Updater: Konstantin Sharenkov (mailto:kon...@en...)
Date: Wed, 10 Dec 2003 12:46 AM
Comment:
See screen without final
Changes:
Attachment changed to screen2.gif
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-535&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-535
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-535
Summary: 2.1 rc1 CGLIB2 Proxy Problems.
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 rc1
Assignee:
Reporter: Konstantin Sharenkov
Created: Tue, 9 Dec 2003 11:49 PM
Updated: Wed, 10 Dec 2003 12:46 AM
Environment: WinXP tomcat 4.1.27, jdk 1.4.1,
Description:
After i moved to 2.1 RC1 form 2.1 beta 3 i have following issue
if class is lazy
<class .... lazy="true">
and I obtain instance
obj = sess.load( XXX.class, ID )
if instance is proxy
1. obj.getId() always returns 0
2. getter for other persistent obj.getPersistent() always returns null
3. getter for persistent enum obj.getEnum() always return value for constant Enum.fromInt(0)
if i set lazy="false" ol works correct
if i use previous verison library all correct too.
the sample for id and Persistent Enum included
see User.getType, User.getId() and Screenshoots
---------------------------------------------------------------------
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-12-10 06:45:18
|
The following comment has been added to this issue:
Author: Konstantin Sharenkov
Created: Wed, 10 Dec 2003 12:44 AM
Body:
Sorry
without final
id - correct
PersistentEnum not correct
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-535
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-535
Summary: 2.1 rc1 CGLIB2 Proxy Problems.
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 rc1
Assignee:
Reporter: Konstantin Sharenkov
Created: Tue, 9 Dec 2003 11:49 PM
Updated: Wed, 10 Dec 2003 12:44 AM
Environment: WinXP tomcat 4.1.27, jdk 1.4.1,
Description:
After i moved to 2.1 RC1 form 2.1 beta 3 i have following issue
if class is lazy
<class .... lazy="true">
and I obtain instance
obj = sess.load( XXX.class, ID )
if instance is proxy
1. obj.getId() always returns 0
2. getter for other persistent obj.getPersistent() always returns null
3. getter for persistent enum obj.getEnum() always return value for constant Enum.fromInt(0)
if i set lazy="false" ol works correct
if i use previous verison library all correct too.
the sample for id and Persistent Enum included
see User.getType, User.getId() and Screenshoots
---------------------------------------------------------------------
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-12-10 06:40:17
|
The following comment has been added to this issue:
Author: Konstantin Sharenkov
Created: Wed, 10 Dec 2003 12:39 AM
Body:
I've applied 'final' when I tryed to resolve this issue.
Without 'final' modificator, the behavior of system is absolutey the same.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-535
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-535
Summary: 2.1 rc1 CGLIB2 Proxy Problems.
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 rc1
Assignee:
Reporter: Konstantin Sharenkov
Created: Tue, 9 Dec 2003 11:49 PM
Updated: Wed, 10 Dec 2003 12:39 AM
Environment: WinXP tomcat 4.1.27, jdk 1.4.1,
Description:
After i moved to 2.1 RC1 form 2.1 beta 3 i have following issue
if class is lazy
<class .... lazy="true">
and I obtain instance
obj = sess.load( XXX.class, ID )
if instance is proxy
1. obj.getId() always returns 0
2. getter for other persistent obj.getPersistent() always returns null
3. getter for persistent enum obj.getEnum() always return value for constant Enum.fromInt(0)
if i set lazy="false" ol works correct
if i use previous verison library all correct too.
the sample for id and Persistent Enum included
see User.getType, User.getId() and Screenshoots
---------------------------------------------------------------------
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-12-10 06:34:16
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 10 Dec 2003 12:33 AM
Body:
You have declared getId() final!
CGLIB is not able to proxy a final method correctly, as per the Hibernate documentation (this has always been the case).
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-535
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-535
Summary: 2.1 rc1 CGLIB2 Proxy Problems.
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 rc1
Assignee:
Reporter: Konstantin Sharenkov
Created: Tue, 9 Dec 2003 11:49 PM
Updated: Wed, 10 Dec 2003 12:33 AM
Environment: WinXP tomcat 4.1.27, jdk 1.4.1,
Description:
After i moved to 2.1 RC1 form 2.1 beta 3 i have following issue
if class is lazy
<class .... lazy="true">
and I obtain instance
obj = sess.load( XXX.class, ID )
if instance is proxy
1. obj.getId() always returns 0
2. getter for other persistent obj.getPersistent() always returns null
3. getter for persistent enum obj.getEnum() always return value for constant Enum.fromInt(0)
if i set lazy="false" ol works correct
if i use previous verison library all correct too.
the sample for id and Persistent Enum included
see User.getType, User.getId() and Screenshoots
---------------------------------------------------------------------
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.
