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-11-28 03:17:16
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Thu, 27 Nov 2003 9:16 PM
Closed sesame! ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-244
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-244
Summary: Hibernate creates alias identifiers that are too long
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 rc1
Versions:
2.0.2
Assignee:
Reporter: Mark Woon
Created: Mon, 11 Aug 2003 1:17 AM
Updated: Thu, 27 Nov 2003 9:16 PM
Environment: Oracle 9.0.2.
Description:
After switching to Hibernate 2 I find that Hibernate is still creating alias identifiers that are too long.
The HQL query that's causing it:
select freqInSs, freqInRae, freqInSs.allele
from DbVariantPosition as varPos,
DbVariantAllele as varAl,
DbAlleleFrequencyInSampleSet as freqInSs,
DbAlleleFrequencyInRaceAndEthnicity as freqInRae
where varPos.goldenPathPosition = ?
and varPos.id != ?
order by freqInSs, freqInRae
The SQL query that gets generated:
select dballele2_.alleleFreqInSampleSetsId as alleleFreqInSampleSetsId0_, dballele3_.alleleFreqInSSRaceEthnicityId as alleleFreqInSSRaceEthnicityId1_, dballele2_.variantPositionId as variantP2_0_, dballele2_.sampleSetId as sampleSe3_0_, dballele2_.allele as allele0_, dballele2_.totalObserved as totalObs5_0_, dballele2_.frequency as frequency0_, dballele3_.alleleFreqInSampleSetId as alleleFr2_1_, dballele3_.racialClassId as racialCl3_1_, dballele3_.ethnicClassId as ethnicCl4_1_, dballele3_.totalObserved as totalObs5_1_, dballele3_.frequency as frequency1_, dballele2_.alleleFreqInSampleSetsId as x0_0_, dballele3_.alleleFreqInSSRaceEthnicityId as x1_0_, dballele2_.allele as x2_0_ from VariantPositions dbvarian0_, VariantAlleles dbvarian1_, AlleleFreqInSampleSets dballele2_, AlleleFreqInSSRaceEthnicity dballele3_ where (dbvarian0_.goldenPathPosition=? )and(dbvarian0_.variantPositionId!=? ) order by dballele2_.alleleFreqInSampleSetsId , dballele3_.alleleFreqInSSRaceEthnicityId
The offending alias identifier is "alleleFreqInSSRaceEthnicityId1_" which is 31 characters long -- one more that Oracle's max identifier length.
Is this a known problem? I can attach my mappings if it will help...
---------------------------------------------------------------------
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-11-27 23:43:16
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Thu, 27 Nov 2003 5:42 PM
Body:
note - I am not confident the patch is complete with respect on joins on these long names....but I am confident that the patch is a step in the right direction! We just need to find those boundary cases where this can brake up....
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-244
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-244
Summary: Hibernate creates alias identifiers that are too long
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.2
Assignee:
Reporter: Mark Woon
Created: Mon, 11 Aug 2003 1:17 AM
Updated: Thu, 27 Nov 2003 5:42 PM
Environment: Oracle 9.0.2.
Description:
After switching to Hibernate 2 I find that Hibernate is still creating alias identifiers that are too long.
The HQL query that's causing it:
select freqInSs, freqInRae, freqInSs.allele
from DbVariantPosition as varPos,
DbVariantAllele as varAl,
DbAlleleFrequencyInSampleSet as freqInSs,
DbAlleleFrequencyInRaceAndEthnicity as freqInRae
where varPos.goldenPathPosition = ?
and varPos.id != ?
order by freqInSs, freqInRae
The SQL query that gets generated:
select dballele2_.alleleFreqInSampleSetsId as alleleFreqInSampleSetsId0_, dballele3_.alleleFreqInSSRaceEthnicityId as alleleFreqInSSRaceEthnicityId1_, dballele2_.variantPositionId as variantP2_0_, dballele2_.sampleSetId as sampleSe3_0_, dballele2_.allele as allele0_, dballele2_.totalObserved as totalObs5_0_, dballele2_.frequency as frequency0_, dballele3_.alleleFreqInSampleSetId as alleleFr2_1_, dballele3_.racialClassId as racialCl3_1_, dballele3_.ethnicClassId as ethnicCl4_1_, dballele3_.totalObserved as totalObs5_1_, dballele3_.frequency as frequency1_, dballele2_.alleleFreqInSampleSetsId as x0_0_, dballele3_.alleleFreqInSSRaceEthnicityId as x1_0_, dballele2_.allele as x2_0_ from VariantPositions dbvarian0_, VariantAlleles dbvarian1_, AlleleFreqInSampleSets dballele2_, AlleleFreqInSSRaceEthnicity dballele3_ where (dbvarian0_.goldenPathPosition=? )and(dbvarian0_.variantPositionId!=? ) order by dballele2_.alleleFreqInSampleSetsId , dballele3_.alleleFreqInSSRaceEthnicityId
The offending alias identifier is "alleleFreqInSSRaceEthnicityId1_" which is 31 characters long -- one more that Oracle's max identifier length.
Is this a known problem? I can attach my mappings if it will help...
---------------------------------------------------------------------
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-11-27 23:35:16
|
The following issue has been updated:
Updater: Max Rydahl Andersen (mailto:xa...@xa...)
Date: Thu, 27 Nov 2003 5:35 PM
Comment:
I don't know if it was possible because of my current sickness - but
somehow I succeded in making persisters (at least EntityPersister and NormalizedEntityPersister) generate short aliases for id's and discriminators!
The patch basically just fill in the blanks of the current impl.
There were no aliases generated for ids and discriminators as there are for all other properties - now there are.
I don't feel like committing this one before someone else have verified the sanity of it even though FooBarTest still runs fine ;)
Changes:
Attachment changed to aliasidstuff.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-244&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-244
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-244
Summary: Hibernate creates alias identifiers that are too long
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.2
Assignee:
Reporter: Mark Woon
Created: Mon, 11 Aug 2003 1:17 AM
Updated: Thu, 27 Nov 2003 5:35 PM
Environment: Oracle 9.0.2.
Description:
After switching to Hibernate 2 I find that Hibernate is still creating alias identifiers that are too long.
The HQL query that's causing it:
select freqInSs, freqInRae, freqInSs.allele
from DbVariantPosition as varPos,
DbVariantAllele as varAl,
DbAlleleFrequencyInSampleSet as freqInSs,
DbAlleleFrequencyInRaceAndEthnicity as freqInRae
where varPos.goldenPathPosition = ?
and varPos.id != ?
order by freqInSs, freqInRae
The SQL query that gets generated:
select dballele2_.alleleFreqInSampleSetsId as alleleFreqInSampleSetsId0_, dballele3_.alleleFreqInSSRaceEthnicityId as alleleFreqInSSRaceEthnicityId1_, dballele2_.variantPositionId as variantP2_0_, dballele2_.sampleSetId as sampleSe3_0_, dballele2_.allele as allele0_, dballele2_.totalObserved as totalObs5_0_, dballele2_.frequency as frequency0_, dballele3_.alleleFreqInSampleSetId as alleleFr2_1_, dballele3_.racialClassId as racialCl3_1_, dballele3_.ethnicClassId as ethnicCl4_1_, dballele3_.totalObserved as totalObs5_1_, dballele3_.frequency as frequency1_, dballele2_.alleleFreqInSampleSetsId as x0_0_, dballele3_.alleleFreqInSSRaceEthnicityId as x1_0_, dballele2_.allele as x2_0_ from VariantPositions dbvarian0_, VariantAlleles dbvarian1_, AlleleFreqInSampleSets dballele2_, AlleleFreqInSSRaceEthnicity dballele3_ where (dbvarian0_.goldenPathPosition=? )and(dbvarian0_.variantPositionId!=? ) order by dballele2_.alleleFreqInSampleSetsId , dballele3_.alleleFreqInSSRaceEthnicityId
The offending alias identifier is "alleleFreqInSSRaceEthnicityId1_" which is 31 characters long -- one more that Oracle's max identifier length.
Is this a known problem? I can attach my mappings if it will help...
---------------------------------------------------------------------
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-11-27 21:25:16
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Thu, 27 Nov 2003 3:24 PM
Body:
Great!
Just discovered that the previous unittests was really bad!
Passed on wrong assumptions, wrong hql syntax and more ;(
I've fixed all that plus added test for the fix Steve made (and yes - it passes ;)
While doing that I came to the thought that maybe we should introduce a InvalidParameterQueryException or something - now that we have
started adding other more specific exceptions stuff....what'da'ya say ?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-495
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-495
Summary: Intermedia search problems begining 2.1 version
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 rc1
Versions:
2.1 beta 2
2.1 beta 3
2.1 beta 4
2.1 beta 5
2.1 beta 6
Assignee: Steve Ebersole
Reporter: Irakli Nadareishvili
Created: Mon, 24 Nov 2003 3:38 PM
Updated: Thu, 27 Nov 2003 3:24 PM
Environment: Hibernate 2.1 beta4 and beta6. Oracle 9i
Description:
Hi,
Oracle Intermedia queries that have a "?" fails with Hibernate 2.1.
The following OQL fails with a message : net.sf.hibernate.QueryException: Not all positional parameters have been set
select cpv.id , message.message , cpv.indent from cpv in class org.digijava.module.eproc.dbentity.CPV , from message in class org.digijava.kernel.entity.Message where contains(message.message,'?asd', 1) > 0 and ( message.key = 'cpv:'||cpv8 and message.locale = 'en' ) order by cpv.id
Hibernate 2.0 was ignoring the '?' within the contains clause, while 2.1 thinks it is a replacement parameter. We experience this problem on 2.1 beta4, 2.1 beta6. No such issues with 2.0 or 2.1beta1
Please, advise.
Stack Trace:
net.sf.hibernate.QueryException: Not all positional parameters have been set [se
lect cpv.id , message.message , cpv.indent from cpv in class org.digijava.modul
e.eproc.dbentity.CPV , from message in class org.digijava.kernel.entity.Message
where contains(message.message,'?asd', 1) > 0 and ( message.key = 'cpv:'||cpv8
and message.locale = 'en' ) order by cpv.id]
at net.sf.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQuer
yImpl.java:88)
at net.sf.hibernate.impl.QueryImpl.list(QueryImpl.java:43)
at app.HBTest.main(HBTest.java:280)
---------------------------------------------------------------------
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-11-27 17:56:16
|
Message:
The following issue has been closed.
Resolver: Steve Ebersole
Date: Thu, 27 Nov 2003 11:55 AM
added fix to the Alias class to replace '$' characters during alias string generation
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-499
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-499
Summary: Wrong alias with a class with $s name
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 rc1
Versions:
2.1 beta 6
Assignee: Steve Ebersole
Reporter: Alfonso da Silva
Created: Tue, 25 Nov 2003 9:59 AM
Updated: Thu, 27 Nov 2003 11:55 AM
Environment: Hibernate 2.1 beta 6, PostgreSQL 7.2
Description:
I have a class (generated with gclib) with this name:
persistent.core.DAO$$EnhancedByCGLIB$$0
When I want to load an object, Hibernate generates this SQL sentence:
select dao$$enh0_.IDO as IDO0_, dao$$enh0_.nom as nom0_, dao$$enh0_.edat as edat0_ from alumne1 dao$$enh0_ where dao$$enh0_.IDO=?
and the JDBC driver crashes:
java.sql.SQLException: ERROR: parser: parse error at or near "$$"
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:94)
at org.postgresql.Connection.ExecSQL(Connection.java:398)
at org.postgresql.jdbc2.Statement.execute(Statement.java:130)
at org.postgresql.jdbc2.Statement.executeQuery(Statement.java:54)
at org.postgresql.jdbc2.PreparedStatement.executeQuery(PreparedStatement.java:99)
at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:83)
at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:631)
at net.sf.hibernate.loader.Loader.doResultSet(Loader.java:166)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:111)
I think that the class alias generation would have to replace '$' by '_' (or another inoffensive character ;) ).
The class alias generation takes place in net.sf.hibernate.loader.OuterJoinLoader (lines 517-528) and uses net.sf.hibernate.sql.Alias.
Thankx.
Kutlax.
---------------------------------------------------------------------
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-11-27 16:46:16
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 27 Nov 2003 10:46 AM
Body:
Guys, the problem is not table names. It is identifier (+discriminator) column names ONLY.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-244
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-244
Summary: Hibernate creates alias identifiers that are too long
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.2
Assignee:
Reporter: Mark Woon
Created: Mon, 11 Aug 2003 1:17 AM
Updated: Thu, 27 Nov 2003 10:46 AM
Environment: Oracle 9.0.2.
Description:
After switching to Hibernate 2 I find that Hibernate is still creating alias identifiers that are too long.
The HQL query that's causing it:
select freqInSs, freqInRae, freqInSs.allele
from DbVariantPosition as varPos,
DbVariantAllele as varAl,
DbAlleleFrequencyInSampleSet as freqInSs,
DbAlleleFrequencyInRaceAndEthnicity as freqInRae
where varPos.goldenPathPosition = ?
and varPos.id != ?
order by freqInSs, freqInRae
The SQL query that gets generated:
select dballele2_.alleleFreqInSampleSetsId as alleleFreqInSampleSetsId0_, dballele3_.alleleFreqInSSRaceEthnicityId as alleleFreqInSSRaceEthnicityId1_, dballele2_.variantPositionId as variantP2_0_, dballele2_.sampleSetId as sampleSe3_0_, dballele2_.allele as allele0_, dballele2_.totalObserved as totalObs5_0_, dballele2_.frequency as frequency0_, dballele3_.alleleFreqInSampleSetId as alleleFr2_1_, dballele3_.racialClassId as racialCl3_1_, dballele3_.ethnicClassId as ethnicCl4_1_, dballele3_.totalObserved as totalObs5_1_, dballele3_.frequency as frequency1_, dballele2_.alleleFreqInSampleSetsId as x0_0_, dballele3_.alleleFreqInSSRaceEthnicityId as x1_0_, dballele2_.allele as x2_0_ from VariantPositions dbvarian0_, VariantAlleles dbvarian1_, AlleleFreqInSampleSets dballele2_, AlleleFreqInSSRaceEthnicity dballele3_ where (dbvarian0_.goldenPathPosition=? )and(dbvarian0_.variantPositionId!=? ) order by dballele2_.alleleFreqInSampleSetsId , dballele3_.alleleFreqInSSRaceEthnicityId
The offending alias identifier is "alleleFreqInSSRaceEthnicityId1_" which is 31 characters long -- one more that Oracle's max identifier length.
Is this a known problem? I can attach my mappings if it will help...
---------------------------------------------------------------------
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-11-27 16:43:16
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 27 Nov 2003 10:42 AM
This was already fixed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-504
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-504
Summary: index name too long for DB2 v7.2
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Components:
core
Versions:
2.1 beta 5
Assignee:
Reporter: Grigoroscuta Catalin
Created: Thu, 27 Nov 2003 9:05 AM
Updated: Thu, 27 Nov 2003 10:42 AM
Environment: Hibernate v2.1b5
Database: DB2 v7.2, Linux platform
Description:
The name automatically generated for indexes (IDX################) is 19 characters long, while DB2 allows maximum 18 characters for index name.
(My quick fix was to replace IDX with IX).
---------------------------------------------------------------------
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-11-27 15:24:42
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-505 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-505 Summary: Allow proxy not to initialize object on hashCode/equals Type: New Feature Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: Dmitry Created: Thu, 27 Nov 2003 9:23 AM Updated: Thu, 27 Nov 2003 9:23 AM Description: There should be a way to tell Hibernate what although class A implements hashCode() and equals(), Hibernate should not initialize proxy for this class when these methods are called. This allows creation of classes with simple hashCode/equals which operate on Id property only. Currently such an objects get initialized when equals() is called resulting in inefficient operations with collections of proxied objects. One of the way of doing this would be addition of proxy-equals and proxy-hashcode attributes to <class> mapping element with following values: "true" - proxy handles hashCode()/equals() by itself (using Id property) "false" - proxy doesn't handle hashCode()/equals() but calls target's method WITHOUT initializing the object. "auto" - default. Do exactly what proxy does now - if objects doesn't override hashCode()/equals(), proxy handles these methods. Otherwise, object is initialized when one of these methods get called. Note: when proxy-equals="true", proxy must set target's Id property before calling it's equals() method. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-11-27 15:05:44
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-504 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-504 Summary: index name too long for DB2 v7.2 Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 5 Assignee: Reporter: Grigoroscuta Catalin Created: Thu, 27 Nov 2003 9:05 AM Updated: Thu, 27 Nov 2003 9:05 AM Environment: Hibernate v2.1b5 Database: DB2 v7.2, Linux platform Description: The name automatically generated for indexes (IDX################) is 19 characters long, while DB2 allows maximum 18 characters for index name. (My quick fix was to replace IDX with IX). --------------------------------------------------------------------- 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-11-27 15:05:43
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 27 Nov 2003 9:03 AM
Steve fixed this in CVS.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-495
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-495
Summary: Intermedia search problems begining 2.1 version
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 rc1
Versions:
2.1 beta 2
2.1 beta 3
2.1 beta 4
2.1 beta 5
2.1 beta 6
Assignee: Steve Ebersole
Reporter: Irakli Nadareishvili
Created: Mon, 24 Nov 2003 3:38 PM
Updated: Thu, 27 Nov 2003 9:03 AM
Environment: Hibernate 2.1 beta4 and beta6. Oracle 9i
Description:
Hi,
Oracle Intermedia queries that have a "?" fails with Hibernate 2.1.
The following OQL fails with a message : net.sf.hibernate.QueryException: Not all positional parameters have been set
select cpv.id , message.message , cpv.indent from cpv in class org.digijava.module.eproc.dbentity.CPV , from message in class org.digijava.kernel.entity.Message where contains(message.message,'?asd', 1) > 0 and ( message.key = 'cpv:'||cpv8 and message.locale = 'en' ) order by cpv.id
Hibernate 2.0 was ignoring the '?' within the contains clause, while 2.1 thinks it is a replacement parameter. We experience this problem on 2.1 beta4, 2.1 beta6. No such issues with 2.0 or 2.1beta1
Please, advise.
Stack Trace:
net.sf.hibernate.QueryException: Not all positional parameters have been set [se
lect cpv.id , message.message , cpv.indent from cpv in class org.digijava.modul
e.eproc.dbentity.CPV , from message in class org.digijava.kernel.entity.Message
where contains(message.message,'?asd', 1) > 0 and ( message.key = 'cpv:'||cpv8
and message.locale = 'en' ) order by cpv.id]
at net.sf.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQuer
yImpl.java:88)
at net.sf.hibernate.impl.QueryImpl.list(QueryImpl.java:43)
at app.HBTest.main(HBTest.java:280)
---------------------------------------------------------------------
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-11-27 15:03:43
|
Message:
The following issue has been resolved as FIXED.
Resolver: Gavin King
Date: Thu, 27 Nov 2003 9:02 AM
I applied the patch, with some adjustments. Didn't add the tests yet though.
Thanks.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-496
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-496
Summary: Version and unsaved-value
Type: New Feature
Status: Resolved
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 rc1
Versions:
2.1 beta 6
Assignee: Gavin King
Reporter: Emmanuel Bernard
Created: Mon, 24 Nov 2003 11:08 PM
Updated: Thu, 27 Nov 2003 9:02 AM
Environment: Hibernate CVS head of branchv21 nov 25
Description:
Here is a patch allowing unsaved value for version. This is useful for saveOrUpdate() assigned id and having version as primitive type.
Version unsaved-value can be:
* undefined: let the saveOrUpdate choice to id's unsaved-value
this is the default to prevent mapping break down primitive type version)
* null: save if version==null, update otherwise
* negative: save if version < 0, update otherwise (allowed for short, int, long only)
Timestamp unsaved-value can be:
* null: I think this is the only needed behavior. I don't know how undefined could be useful.
---------------------------------------------------------------------
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-11-26 21:53:36
|
The following comment has been added to this issue:
Author: Jeff Turner
Created: Wed, 26 Nov 2003 3:53 PM
Body:
> Can you alter the code that is generated for the Sybase case so that
> it works in either case? Sybase support provided the following, which
> seems to address the issue. I combines the insert and the select of
> the new identity value into a single prepared statement so that both
> are in the same compiled object on the server.
>
> String nl=System.getProperty("line.separator");
> PreparedStaement ps=conn.prepareStatement(
> "insert into Yadd (val1,val2) values ( 1,2 )"
> + nl
> + "select @@identity");
(on behalf of Richard Scranton, whose reply went to leg...@at...)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-485
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-485
Summary: DYNAMIC_PREPARE and @@identity
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Richard Scranton
Created: Thu, 20 Nov 2003 1:22 PM
Updated: Wed, 26 Nov 2003 3:53 PM
Description:
Using the Sybase jConnect jdbc driver version 4.5 or 5.5, if the connection property DYNAMIC_PREPARE is set to "true", "select @@identity" will always return a "0". This is an artifact of the Sybase implementation of prepared statements. Statements compiled at the server become stored procedures marked by the "DYN" token, and appear named as dyn100, dyn101, etc in the
captured TDS stream. The value of @@identity is lost at the end of a procedure, so a sequence of prepared statements like:
insert into Yadda (val1,val2) values ( 1,2 )
select @@identity
will execute as expected when DYNAMIC_PREPARE is false. If it is set to true, the statement "select @@identity" will return "0". Sybase suggests something like this workaround to get the expected behavior:
String nl=System.getProperty("line.separator");
PreparedStaement ps=conn.prepareStatement(
"insert into Yadd (val1,val2) values ( 1,2 )"
+ nl
+ "select @@identity");
Leaving DYNAMIC_PREPARE set false gives away throughput if the queries being sent and parsed are of significant size. TDS dumps show they are being sent and parsed with each invocation. Setting DYNAMIC_PREPARE to true allows reuse of the parsed queries.
---------------------------------------------------------------------
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-11-26 16:20:49
|
The following comment has been added to this issue:
Author: Philippe Chal=C3=A9at
Created: Wed, 26 Nov 2003 10:19 AM
Body:
Sorry, it's not for 2.02, but for 2.1rc6
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-503
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-503
Summary: Using index() function many-to-many
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:=20
core
Versions:
2.0.2
Assignee:=20
Reporter: Philippe Chal=C3=A9at
Created: Wed, 26 Nov 2003 10:17 AM
Updated: Wed, 26 Nov 2003 10:19 AM
Description:
I think it could be interesting to have to built-in index() function work o=
n many-to-many Map.
For example :
I have an object, say Article, with some text fields that can be translated=
in many langages.
In Article, I declare a map whose key is Langage Object and value is an obj=
ect with all my translatable fields.
In some cases, I want make a query on Article and order it according to one=
of my translatable field and for a given langage.
---------------------------------------------------------------------
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-11-26 16:20:49
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@hi...)
Assigner: Gavin King (mailto:ga...@hi...)
Date: Wed, 26 Nov 2003 10:19 AM
Comment:
Patch looks good to me. Thanks.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-496
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-496
Summary: Version and unsaved-value
Type: New Feature
Status: Open
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 6
Assignee: Gavin King
Reporter: Emmanuel Bernard
Created: Mon, 24 Nov 2003 11:08 PM
Updated: Wed, 26 Nov 2003 10:19 AM
Environment: Hibernate CVS head of branchv21 nov 25
Description:
Here is a patch allowing unsaved value for version. This is useful for saveOrUpdate() assigned id and having version as primitive type.
Version unsaved-value can be:
* undefined: let the saveOrUpdate choice to id's unsaved-value
this is the default to prevent mapping break down primitive type version)
* null: save if version==null, update otherwise
* negative: save if version < 0, update otherwise (allowed for short, int, long only)
Timestamp unsaved-value can be:
* null: I think this is the only needed behavior. I don't know how undefined could be useful.
---------------------------------------------------------------------
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-11-26 16:18:48
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?= key=3DHB-503 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-503 Summary: Using index() function many-to-many Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components:=20 core Versions: 2.0.2 Assignee:=20 Reporter: Philippe Chal=C3=A9at Created: Wed, 26 Nov 2003 10:17 AM Updated: Wed, 26 Nov 2003 10:17 AM Description: I think it could be interesting to have to built-in index() function work o= n many-to-many Map. For example : I have an object, say Article, with some text fields that can be translated= in many langages. In Article, I declare a map whose key is Langage Object and value is an obj= ect with all my translatable fields. In some cases, I want make a query on Article and order it according to one= of my translatable field and for a given langage. --------------------------------------------------------------------- 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-11-26 16:16:48
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 26 Nov 2003 10:16 AM
This should be working in latest releases afaik. Try Hibernate 2.1.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-502
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-502
Summary: group by clause in subselect
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Versions:
2.0.2
Assignee:
Reporter: Jo Droogmans
Created: Wed, 26 Nov 2003 9:56 AM
Updated: Wed, 26 Nov 2003 10:16 AM
Environment: Hibernate 2.0.2
Database Informix (any database that supports correlated subselects)
Description:
HQL does not support a group by clause in a correlated subselect
e.g.
select o1.objid
from object o1
where
o1.property1 in
(select o2.property1
from object o2
where o1 = 02
group by 02.property1)
---------------------------------------------------------------------
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-11-26 16:09:48
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 26 Nov 2003 10:08 AM
Done.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-501
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-501
Summary: ODMG: Lifecycle of Database class in Implementation Singleton
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1 final
Assignee: Gavin King
Reporter: Oliver Gries
Created: Wed, 26 Nov 2003 12:21 AM
Updated: Wed, 26 Nov 2003 10:08 AM
Description:
I'm sorry for posting this again, but it's a bit annoying after every new hibernate relase to add this 2 fixes manually.
Bug (1)
Here is the short solution of this problem allreay posted within Hibernate 1.2.5 (HBI-5).
Solution in Implementation class:
******************************
newTransaction() must not use the local variable database for creating a transaction but the db instance assoc. with the current thread, which gets returned by the currentTransaction() method.
public org.odmg.Transaction newTransaction() {
try {
// old
return new Transaction(database);
// new
return new Transaction(currentDatabase());
}
catch (ODMGException ode) {
throw new ODMGRuntimeException( ode.getMessage() );
}
}
Bug (2)
Allready posted as HB-85. Solution is very easy !!! ;-))
---------------------------------------------------------------------
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-11-26 16:02:48
|
Message:
The following issue has been re-assigned.
Assignee: Steve Ebersole (mailto:ste...@vi...)
Assigner: Gavin King (mailto:ga...@hi...)
Date: Wed, 26 Nov 2003 10:02 AM
Comment:
Max, I'm reassigning this to steve, since you are sick.
Steve, we added some code to scan the query string and validate parameters to AbstractQueryImpl in 2.1. It is this code that is broken, not the actual query parser I imagine. It just needs to handle quoted identifiers. But hopefully it can do this in a reasonably performant way.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-495
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-495
Summary: Intermedia search problems begining 2.1 version
Type: Bug
Status: Open
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 2
2.1 beta 3
2.1 beta 4
2.1 beta 5
2.1 beta 6
Assignee: Steve Ebersole
Reporter: Irakli Nadareishvili
Created: Mon, 24 Nov 2003 3:38 PM
Updated: Wed, 26 Nov 2003 10:02 AM
Environment: Hibernate 2.1 beta4 and beta6. Oracle 9i
Description:
Hi,
Oracle Intermedia queries that have a "?" fails with Hibernate 2.1.
The following OQL fails with a message : net.sf.hibernate.QueryException: Not all positional parameters have been set
select cpv.id , message.message , cpv.indent from cpv in class org.digijava.module.eproc.dbentity.CPV , from message in class org.digijava.kernel.entity.Message where contains(message.message,'?asd', 1) > 0 and ( message.key = 'cpv:'||cpv8 and message.locale = 'en' ) order by cpv.id
Hibernate 2.0 was ignoring the '?' within the contains clause, while 2.1 thinks it is a replacement parameter. We experience this problem on 2.1 beta4, 2.1 beta6. No such issues with 2.0 or 2.1beta1
Please, advise.
Stack Trace:
net.sf.hibernate.QueryException: Not all positional parameters have been set [se
lect cpv.id , message.message , cpv.indent from cpv in class org.digijava.modul
e.eproc.dbentity.CPV , from message in class org.digijava.kernel.entity.Message
where contains(message.message,'?asd', 1) > 0 and ( message.key = 'cpv:'||cpv8
and message.locale = 'en' ) order by cpv.id]
at net.sf.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQuer
yImpl.java:88)
at net.sf.hibernate.impl.QueryImpl.list(QueryImpl.java:43)
at app.HBTest.main(HBTest.java:280)
---------------------------------------------------------------------
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-11-26 16:00:48
|
Message:
The following issue has been re-assigned.
Assignee: Steve Ebersole (mailto:ste...@vi...)
Assigner: Gavin King (mailto:ga...@hi...)
Date: Wed, 26 Nov 2003 10:00 AM
Comment:
Steve, take a look at this if you get a chance, otherwise assign back to me. Probably need to handle this inside the Alias class.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-499
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-499
Summary: Wrong alias with a class with $s name
Type: Bug
Status: Open
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 beta 6
Assignee: Steve Ebersole
Reporter: Alfonso da Silva
Created: Tue, 25 Nov 2003 9:59 AM
Updated: Wed, 26 Nov 2003 10:00 AM
Environment: Hibernate 2.1 beta 6, PostgreSQL 7.2
Description:
I have a class (generated with gclib) with this name:
persistent.core.DAO$$EnhancedByCGLIB$$0
When I want to load an object, Hibernate generates this SQL sentence:
select dao$$enh0_.IDO as IDO0_, dao$$enh0_.nom as nom0_, dao$$enh0_.edat as edat0_ from alumne1 dao$$enh0_ where dao$$enh0_.IDO=?
and the JDBC driver crashes:
java.sql.SQLException: ERROR: parser: parse error at or near "$$"
at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:94)
at org.postgresql.Connection.ExecSQL(Connection.java:398)
at org.postgresql.jdbc2.Statement.execute(Statement.java:130)
at org.postgresql.jdbc2.Statement.executeQuery(Statement.java:54)
at org.postgresql.jdbc2.PreparedStatement.executeQuery(PreparedStatement.java:99)
at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:83)
at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:631)
at net.sf.hibernate.loader.Loader.doResultSet(Loader.java:166)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:111)
I think that the class alias generation would have to replace '$' by '_' (or another inoffensive character ;) ).
The class alias generation takes place in net.sf.hibernate.loader.OuterJoinLoader (lines 517-528) and uses net.sf.hibernate.sql.Alias.
Thankx.
Kutlax.
---------------------------------------------------------------------
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-11-26 15:58:49
|
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-501 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-501 Summary: ODMG: Lifecycle of Database class in Implementation Singleton Type: Bug Status: Open Priority: Major Project: Hibernate2 Assignee: Gavin King Reporter: Oliver Gries Created: Wed, 26 Nov 2003 12:21 AM Updated: Wed, 26 Nov 2003 9:57 AM Description: I'm sorry for posting this again, but it's a bit annoying after every new hibernate relase to add this 2 fixes manually. Bug (1) Here is the short solution of this problem allreay posted within Hibernate 1.2.5 (HBI-5). Solution in Implementation class: ****************************** newTransaction() must not use the local variable database for creating a transaction but the db instance assoc. with the current thread, which gets returned by the currentTransaction() method. public org.odmg.Transaction newTransaction() { try { // old return new Transaction(database); // new return new Transaction(currentDatabase()); } catch (ODMGException ode) { throw new ODMGRuntimeException( ode.getMessage() ); } } Bug (2) Allready posted as HB-85. Solution is very easy !!! ;-)) --------------------------------------------------------------------- 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-11-26 15:58:48
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-502 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-502 Summary: group by clause in subselect Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0.2 Assignee: Reporter: Jo Droogmans Created: Wed, 26 Nov 2003 9:56 AM Updated: Wed, 26 Nov 2003 9:56 AM Environment: Hibernate 2.0.2 Database Informix (any database that supports correlated subselects) Description: HQL does not support a group by clause in a correlated subselect e.g. select o1.objid from object o1 where o1.property1 in (select o2.property1 from object o2 where o1 = 02 group by 02.property1) --------------------------------------------------------------------- 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-11-26 15:51:49
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 26 Nov 2003 9:51 AM
If thats the case, you should actually be able to work around this by being careful about which order you map columns in, perhaps.
Anyway, I'm resoving this as "won't fix".
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-484
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-484
Summary: ResultSet can not re-read row data for column 2
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Assignee:
Reporter: Benoit Menendez
Created: Thu, 20 Nov 2003 12:24 PM
Updated: Wed, 26 Nov 2003 9:51 AM
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-11-26 06:29:48
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 26 Nov 2003 12:29 AM
Body:
My reading of the ODMG spec is that you can only update an object that is already associated with a transaction. I don't get the impression that it is possible to reassociate an object with a new transaction. Am I wrong about this?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-85
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-85
Summary: ODMG: Database.makePersistent() -> saveOrUpdate() inst. of save()
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Assignee:
Reporter: Oliver Gries
Created: Mon, 19 May 2003 12:33 AM
Updated: Wed, 26 Nov 2003 12:29 AM
Environment: n.a.
Description:
Would'nt it be only consistent to wrap Session.saveOrUpdate() in the odmg implementation for the Database.makePersistent() method instead of Session.save() ??
Greetings Oliver
---------------------------------------------------------------------
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-11-26 06:22:50
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-501 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-501 Summary: ODMG: Lifecycle of Database class in Implementation Singleton Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Oliver Gries Created: Wed, 26 Nov 2003 12:21 AM Updated: Wed, 26 Nov 2003 12:21 AM Description: I'm sorry for posting this again, but it's a bit annoying after every new hibernate relase to add this 2 fixes manually. Bug (1) Here is the short solution of this problem allreay posted within Hibernate 1.2.5 (HBI-5). Solution in Implementation class: ****************************** newTransaction() must not use the local variable database for creating a transaction but the db instance assoc. with the current thread, which gets returned by the currentTransaction() method. public org.odmg.Transaction newTransaction() { try { // old return new Transaction(database); // new return new Transaction(currentDatabase()); } catch (ODMGException ode) { throw new ODMGRuntimeException( ode.getMessage() ); } } Bug (2) Allready posted as HB-85. Solution is very easy !!! ;-)) --------------------------------------------------------------------- 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-11-26 05:57:49
|
The following comment has been added to this issue:
Author: Oliver Gries
Created: Tue, 25 Nov 2003 11:57 PM
Body:
Hi,
maybe the priority of this issue should be increased, because if you don't use saveOrUpdate() as the implementation of the ODMG method makePersistent(), how should an object ever be updated??
Because makePersistent() is the only interface method where you can trigger the persistence of an transient AND persistent object.
;-(
Oliver
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-85
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-85
Summary: ODMG: Database.makePersistent() -> saveOrUpdate() inst. of save()
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Assignee:
Reporter: Oliver Gries
Created: Mon, 19 May 2003 12:33 AM
Updated: Tue, 25 Nov 2003 11:57 PM
Environment: n.a.
Description:
Would'nt it be only consistent to wrap Session.saveOrUpdate() in the odmg implementation for the Database.makePersistent() method instead of Session.save() ??
Greetings Oliver
---------------------------------------------------------------------
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.
