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-08 22:15:13
|
Message:
The following issue has been closed.
Resolver: Christian Bauer
Date: Sat, 8 Nov 2003 4:14 PM
Tried it in Mozilla, Firebird and Konqueror, worked with an empty base attribute. Stupid IE doesn't work, so I removed it from the website template.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-459
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-459
Summary: documentation in distribution seems to be broken
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1 rc1
Assignee: Christian Bauer
Reporter: Steve Kwee
Created: Thu, 6 Nov 2003 7:04 AM
Updated: Sat, 8 Nov 2003 4:14 PM
Environment: Any
Description:
I would not call this a bug, but it's annoying.
Every page of the wiki-dump of the documentation contains a
<base href="">
in line 19 or so.
It is impossible to browse the documentatin from the filesystem
or a local webserver.
The Version is 2.1 beta6, there was no entry for this.
---------------------------------------------------------------------
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-08 21:53:14
|
Message:
The following issue has been closed.
Resolver: Christian Bauer
Date: Sat, 8 Nov 2003 3:52 PM
Added this to reference documentation slightly modified.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-359
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-359
Summary: Ordered list example for the reference docs
Type: Improvement
Status: Closed
Priority: Trivial
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1 rc1
Assignee: Christian Bauer
Reporter: Matt Hall
Created: Tue, 23 Sep 2003 3:08 PM
Updated: Sat, 8 Nov 2003 3:52 PM
Environment: All
Description:
I wrote an example for ordered lists with the index column managed by hibernate. I had some problems figuring out the details and had to ask for help on the forum, hopefully this example in the collections mapping section of the docs will alleviate some confusion.
The patch file is against the XML source file for the collections mapping chapter.
---------------------------------------------------------------------
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-07 15:59:13
|
The following comment has been added to this issue:
Author: Gavin King
Created: Fri, 7 Nov 2003 9:59 AM
Body:
Yours is broken; it has some nulls in the output. Trust me - the doco is correct.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-462
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-462
Summary: UUIDStringGenerator returns a string of length 32 not 16
Type: Bug
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0rc2
Assignee:
Reporter: Chris Patterson
Created: Fri, 7 Nov 2003 9:13 AM
Updated: Fri, 7 Nov 2003 9:20 AM
Environment: Windows XP, JDK 1.4.1, Microsoft Sql Server
Description:
The documentation for UUIDStringGenerator states that it returns a string of length 16. In my tests I have found that it returns a string of length 32. Not a major issue but it should be changed in the docs.
---------------------------------------------------------------------
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-07 15:32:14
|
The following comment has been added to this issue:
Author: Chris Patterson
Created: Fri, 7 Nov 2003 9:31 AM
Body:
**
* <b>uuid.string</b><br>
* <br>
* A <tt>UUIDGenerator</tt> that returns a string of length 16,
* This string will NOT consist of only alphanumeric
* characters. Use this only if you don't mind unreadable
* identifiers.<br>
* <br>
* This implementation is known to be incompatible with
* Postgres.
*
* @see UUIDHexGenerator
* @author Gavin King
*/
public class UUIDStringGenerator extends UUIDGenerator {
here is the doc and code from the Class
I ran the main method out of the class the results of which are in my previous comment.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-462
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-462
Summary: UUIDStringGenerator returns a string of length 32 not 16
Type: Bug
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0rc2
Assignee:
Reporter: Chris Patterson
Created: Fri, 7 Nov 2003 9:13 AM
Updated: Fri, 7 Nov 2003 9:20 AM
Environment: Windows XP, JDK 1.4.1, Microsoft Sql Server
Description:
The documentation for UUIDStringGenerator states that it returns a string of length 16. In my tests I have found that it returns a string of length 32. Not a major issue but it should be changed in the docs.
---------------------------------------------------------------------
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-07 15:22:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 7 Nov 2003 9:20 AM
Actually all the doco is right. Don't confuse uuid.string with uuid.hex. :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-462
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-462
Summary: UUIDStringGenerator returns a string of length 32 not 16
Type: Bug
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0rc2
Assignee:
Reporter: Chris Patterson
Created: Fri, 7 Nov 2003 9:13 AM
Updated: Fri, 7 Nov 2003 9:20 AM
Environment: Windows XP, JDK 1.4.1, Microsoft Sql Server
Description:
The documentation for UUIDStringGenerator states that it returns a string of length 16. In my tests I have found that it returns a string of length 32. Not a major issue but it should be changed in the docs.
---------------------------------------------------------------------
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-07 15:16:14
|
The following comment has been added to this issue:
Author: Chris Patterson
Created: Fri, 7 Nov 2003 9:14 AM
Body:
D:\Borland\JBuilderX\jdk1.4\bin\javaw -classpath "C:\Documents and Settings=
\cpatterson\jbproject\HibernateTest\classes;D:\Tools\Microsoft SQL Server 2=
000 Driver for JDBC\lib\msbase.jar;D:\Tools\Microsoft SQL Server 2000 Drive=
r for JDBC\lib\mssqlserver.jar;D:\Tools\Microsoft SQL Server 2000 Driver fo=
r JDBC\lib\msutil.jar;D:\projects\samples\hibernate-2.0.3\lib\c3p0.jar;D:\p=
rojects\samples\hibernate-2.0.3\lib\cglib-asm.jar;D:\projects\samples\hiber=
nate-2.0.3\lib\commons-beanutils.jar;D:\projects\samples\hibernate-2.0.3\li=
b\commons-collections.jar;D:\projects\samples\hibernate-2.0.3\lib\commons-d=
bcp.jar;D:\projects\samples\hibernate-2.0.3\lib\commons-lang.jar;D:\project=
s\samples\hibernate-2.0.3\lib\commons-logging.jar;D:\projects\samples\hiber=
nate-2.0.3\lib\commons-pool.jar;D:\projects\samples\hibernate-2.0.3\lib\con=
nector.jar;D:\projects\samples\hibernate-2.0.3\lib\dom4j.jar;D:\projects\sa=
mples\hibernate-2.0.3\lib\jaas.jar;D:\projects\samples\hibernate-2.0.3\lib\=
jcs.jar;D:\projects\samples\hibernate-2.0.3\lib\jdbc2_0-stdext.jar;D:\proje=
cts\samples\hibernate-2.0.3\lib\jta.jar;D:\projects\samples\hibernate-2.0.3=
\lib\junit.jar;D:\projects\samples\hibernate-2.0.3\lib\odmg.jar;D:\projects=
\samples\hibernate-2.0.3\lib\optional.jar;D:\projects\samples\hibernate-2.0=
.3\lib\proxool.jar;D:\projects\samples\hibernate-2.0.3\lib\xalan.jar;D:\pro=
jects\samples\hibernate-2.0.3\lib\xerces.jar;D:\projects\samples\hibernate-=
2.0.3\lib\xml-apis.jar;D:\projects\samples\hibernate-2.0.3\hibernate2.jar;D=
:\Borland\JBuilderX\jdk1.4\demo\jfc\Java2D\Java2Demo.jar;D:\Borland\JBuilde=
rX\jdk1.4\demo\plugin\jfc\Java2D\Java2Demo.jar;D:\Borland\JBuilderX\jdk1.4\=
jre\javaws\javaws.jar;D:\Borland\JBuilderX\jdk1.4\jre\lib\charsets.jar;D:\B=
orland\JBuilderX\jdk1.4\jre\lib\ext\dnsns.jar;D:\Borland\JBuilderX\jdk1.4\j=
re\lib\ext\ldapsec.jar;D:\Borland\JBuilderX\jdk1.4\jre\lib\ext\localedata.j=
ar;D:\Borland\JBuilderX\jdk1.4\jre\lib\ext\sunjce_provider.jar;D:\Borland\J=
BuilderX\jdk1.4\jre\lib\im\indicim.jar;D:\Borland\JBuilderX\jdk1.4\jre\lib\=
im\thaiim.jar;D:\Borland\JBuilderX\jdk1.4\jre\lib\jce.jar;D:\Borland\JBuild=
erX\jdk1.4\jre\lib\jsse.jar;D:\Borland\JBuilderX\jdk1.4\jre\lib\plugin.jar;=
D:\Borland\JBuilderX\jdk1.4\jre\lib\rt.jar;D:\Borland\JBuilderX\jdk1.4\jre\=
lib\sunrsasign.jar;D:\Borland\JBuilderX\jdk1.4\lib\dt.jar;D:\Borland\JBuild=
erX\jdk1.4\lib\htmlconverter.jar;D:\Borland\JBuilderX\jdk1.4\lib\tools.jar"=
net.sf.hibernate.id.UUIDStringGenerator=20
=01=15Dnullx6Aenull=E2=82=ACxnull6Ae=13null=E2=82=AC=E2=82=AC: 32
=01=15Dnullx6Aenull=E2=82=ACxnull6Ae=13null=E2=82=AC?: 32
=01=15Dnullx6Aenull=E2=82=ACxnull6Ae=13null=E2=82=AC=E2=80=9A: 32
=01=15Dnullx6Aenull=E2=82=ACxnull6Ae=13null=E2=82=AC=C6=92: 32
=01=15Dnullx6Aenull=E2=82=ACxnull6Ae=13null=E2=82=AC=E2=80=9E: 32
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-462
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-462
Summary: UUIDStringGenerator returns a string of length 32 not 16
Type: Bug
Status: Unassigned
Priority: Minor
Project: Hibernate2
Versions:
2.0rc2
Assignee:=20
Reporter: Chris Patterson
Created: Fri, 7 Nov 2003 9:13 AM
Updated: Fri, 7 Nov 2003 9:13 AM
Environment: Windows XP, JDK 1.4.1, Microsoft Sql Server
Description:
The documentation for UUIDStringGenerator states that it returns a string o=
f length 16. In my tests I have found that it returns a string of length 3=
2. Not a major issue but it should be changed in the docs.
---------------------------------------------------------------------
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-07 15:14:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-462 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-462 Summary: UUIDStringGenerator returns a string of length 32 not 16 Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Versions: 2.0rc2 Assignee: Reporter: Chris Patterson Created: Fri, 7 Nov 2003 9:13 AM Updated: Fri, 7 Nov 2003 9:13 AM Environment: Windows XP, JDK 1.4.1, Microsoft Sql Server Description: The documentation for UUIDStringGenerator states that it returns a string of length 16. In my tests I have found that it returns a string of length 32. Not a major issue but it should be changed in the docs. --------------------------------------------------------------------- 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-07 14:32:26
|
The following comment has been added to this issue:
Author: Joseph Fifield
Created: Fri, 7 Nov 2003 8:31 AM
Body:
Not sure if this helps, but the following code returns the right update count for me using the jTDS driver on SQL Server 2000. SQL Server appears to return multiple update counts when a trigger is fired, and the last one is the update count for the statement you actually executed.
ps.executeUpdate();
int updateCount = ps.getUpdateCount();
while (!ps.getMoreResults() && (ps.getUpdateCount() != -1)) {
updateCount = ps.getUpdateCount();
}
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-139
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-139
Summary: Relax rowcount to be > instead of equal to account for triggers.
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Don Eddleman
Created: Tue, 17 Jun 2003 10:15 AM
Updated: Tue, 4 Nov 2003 5:48 PM
Environment: All OSs, SQLServer and more than likely any other DB that supports triggers.
Description:
Within the NonBatchingBatcher class the check for row count to determine success should be relaxed to rowCount >= expected so that any triggers defined on tables affected by the insert/update will not cause a txn to fail just because they fired.
---------------------------------------------------------------------
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-07 09:26:14
|
The following comment has been added to this issue:
Author: Gavin King
Created: Fri, 7 Nov 2003 3:25 AM
Body:
No, not in the near future. I made a better exception report, btw.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-461
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-461
Summary: Mapping of formula-based properties
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Michail Jekimov
Created: Thu, 6 Nov 2003 10:35 AM
Updated: Thu, 6 Nov 2003 6:13 PM
Environment: JDK 1.4, WinXP Professional, Tomcat 4.1
Description:
When I try to define a mapping with a formula-based property I get the following exception:
net.sf.hibernate.MappingException: property mapping has wrong number of columns: net.sf.hibernate.mapping.Subclass.history
at net.sf.hibernate.mapping.PersistentClass.validate(PersistentClass.java:237)
at net.sf.hibernate.cfg.Configuration.validate(Configuration.java:555)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:712)
...
The property mapping looks like:
<property name="value" formula="myfunc(VALUE)"/>
This happens with Hibernate 2.1 beta 6. When I change the mapping to
<property name="value" column="VALUE"/>
everything works.
---------------------------------------------------------------------
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-07 09:15:14
|
The following comment has been added to this issue:
Author: Michail Jekimov
Created: Fri, 7 Nov 2003 3:13 AM
Body:
Is it intended to support formulas for properties of components?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-461
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-461
Summary: Mapping of formula-based properties
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Michail Jekimov
Created: Thu, 6 Nov 2003 10:35 AM
Updated: Thu, 6 Nov 2003 6:13 PM
Environment: JDK 1.4, WinXP Professional, Tomcat 4.1
Description:
When I try to define a mapping with a formula-based property I get the following exception:
net.sf.hibernate.MappingException: property mapping has wrong number of columns: net.sf.hibernate.mapping.Subclass.history
at net.sf.hibernate.mapping.PersistentClass.validate(PersistentClass.java:237)
at net.sf.hibernate.cfg.Configuration.validate(Configuration.java:555)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:712)
...
The property mapping looks like:
<property name="value" formula="myfunc(VALUE)"/>
This happens with Hibernate 2.1 beta 6. When I change the mapping to
<property name="value" column="VALUE"/>
everything works.
---------------------------------------------------------------------
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-07 00:16:14
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 6 Nov 2003 6:14 PM
Body:
Its just a comment in the DTD, btw.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-461
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-461
Summary: Mapping of formula-based properties
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Michail Jekimov
Created: Thu, 6 Nov 2003 10:35 AM
Updated: Thu, 6 Nov 2003 6:13 PM
Environment: JDK 1.4, WinXP Professional, Tomcat 4.1
Description:
When I try to define a mapping with a formula-based property I get the following exception:
net.sf.hibernate.MappingException: property mapping has wrong number of columns: net.sf.hibernate.mapping.Subclass.history
at net.sf.hibernate.mapping.PersistentClass.validate(PersistentClass.java:237)
at net.sf.hibernate.cfg.Configuration.validate(Configuration.java:555)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:712)
...
The property mapping looks like:
<property name="value" formula="myfunc(VALUE)"/>
This happens with Hibernate 2.1 beta 6. When I change the mapping to
<property name="value" column="VALUE"/>
everything works.
---------------------------------------------------------------------
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-07 00:14:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 6 Nov 2003 6:13 PM
As per the DTD, the formula attribute is not supported for properties of components.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-461
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-461
Summary: Mapping of formula-based properties
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Michail Jekimov
Created: Thu, 6 Nov 2003 10:35 AM
Updated: Thu, 6 Nov 2003 6:13 PM
Environment: JDK 1.4, WinXP Professional, Tomcat 4.1
Description:
When I try to define a mapping with a formula-based property I get the following exception:
net.sf.hibernate.MappingException: property mapping has wrong number of columns: net.sf.hibernate.mapping.Subclass.history
at net.sf.hibernate.mapping.PersistentClass.validate(PersistentClass.java:237)
at net.sf.hibernate.cfg.Configuration.validate(Configuration.java:555)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:712)
...
The property mapping looks like:
<property name="value" formula="myfunc(VALUE)"/>
This happens with Hibernate 2.1 beta 6. When I change the mapping to
<property name="value" column="VALUE"/>
everything works.
---------------------------------------------------------------------
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-06 20:15:14
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Thu, 6 Nov 2003 2:14 PM
Body:
well - I did think I could do it that way when I originally started building SQLLoader....the problem is that the Query "semantics" is that you can call getReturnTypes[] BEFORE you execute the query....
That makes it hard to use resultsetmetadata....and if I remember correctly some parts of hibernate de/hydration from resultset's expect to have some type knowledge before starting executing the query...
..but yes - using the resultsetmetadata would be nice ;)
(and one could just perform an implicit list if you call getReturnTypes[] on a scalar query....and maybe cache the result for later retreival via list(), iterate() etc....)
what'da'ya'say ?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-454
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-454
Summary: Session.createSQLQuery(sql)
Type: New Feature
Status: Unassigned
Priority: Trivial
Project: Hibernate2
Versions:
2.1 beta 5
Assignee:
Reporter: Alexey Kaigorodov
Created: Tue, 4 Nov 2003 9:15 PM
Updated: Tue, 4 Nov 2003 9:15 PM
Description:
Session.createSQLQuery(sql) without returning some entity.
I.e. add the possibility to execute any SELECT through Hibernate API without use JDBC API.
Will useful be for uniform access to data.
--
With best regards,
Alex Kaigorodov
---------------------------------------------------------------------
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-06 16:53:14
|
The following comment has been added to this issue:
Author: Michail Jekimov
Created: Thu, 6 Nov 2003 10:52 AM
Body:
Addition #2: the context seems to be essential; I tried formula mappings in other contexts, e.g. directly under <class> element, and it worked.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-461
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-461
Summary: Mapping of formula-based properties
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Michail Jekimov
Created: Thu, 6 Nov 2003 10:35 AM
Updated: Thu, 6 Nov 2003 10:35 AM
Environment: JDK 1.4, WinXP Professional, Tomcat 4.1
Description:
When I try to define a mapping with a formula-based property I get the following exception:
net.sf.hibernate.MappingException: property mapping has wrong number of columns: net.sf.hibernate.mapping.Subclass.history
at net.sf.hibernate.mapping.PersistentClass.validate(PersistentClass.java:237)
at net.sf.hibernate.cfg.Configuration.validate(Configuration.java:555)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:712)
...
The property mapping looks like:
<property name="value" formula="myfunc(VALUE)"/>
This happens with Hibernate 2.1 beta 6. When I change the mapping to
<property name="value" column="VALUE"/>
everything works.
---------------------------------------------------------------------
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-06 16:42:14
|
The following comment has been added to this issue:
Author: Michail Jekimov
Created: Thu, 6 Nov 2003 10:42 AM
Body:
Addition: the described property mapping is situated in the following context:
<class ...>
...
<subclass ...>
...
<component ...>
...
<component ...>
<property name="value" formula="myfunc(VALUE)"/>
...
</component>
...
</component>
...
</subclass>
...
</class>
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-461
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-461
Summary: Mapping of formula-based properties
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Michail Jekimov
Created: Thu, 6 Nov 2003 10:35 AM
Updated: Thu, 6 Nov 2003 10:35 AM
Environment: JDK 1.4, WinXP Professional, Tomcat 4.1
Description:
When I try to define a mapping with a formula-based property I get the following exception:
net.sf.hibernate.MappingException: property mapping has wrong number of columns: net.sf.hibernate.mapping.Subclass.history
at net.sf.hibernate.mapping.PersistentClass.validate(PersistentClass.java:237)
at net.sf.hibernate.cfg.Configuration.validate(Configuration.java:555)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:712)
...
The property mapping looks like:
<property name="value" formula="myfunc(VALUE)"/>
This happens with Hibernate 2.1 beta 6. When I change the mapping to
<property name="value" column="VALUE"/>
everything works.
---------------------------------------------------------------------
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-06 16:36:18
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-461 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-461 Summary: Mapping of formula-based properties Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: Michail Jekimov Created: Thu, 6 Nov 2003 10:35 AM Updated: Thu, 6 Nov 2003 10:35 AM Environment: JDK 1.4, WinXP Professional, Tomcat 4.1 Description: When I try to define a mapping with a formula-based property I get the following exception: net.sf.hibernate.MappingException: property mapping has wrong number of columns: net.sf.hibernate.mapping.Subclass.history at net.sf.hibernate.mapping.PersistentClass.validate(PersistentClass.java:237) at net.sf.hibernate.cfg.Configuration.validate(Configuration.java:555) at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:712) ... The property mapping looks like: <property name="value" formula="myfunc(VALUE)"/> This happens with Hibernate 2.1 beta 6. When I change the mapping to <property name="value" column="VALUE"/> everything works. --------------------------------------------------------------------- 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-06 14:30:14
|
Message: The following issue has been re-assigned. Assignee: Christian Bauer (mailto:chr...@hi...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-459 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-459 Summary: documentation in distribution seems to be broken Type: Bug Status: Assigned Priority: Minor Project: Hibernate2 Assignee: Christian Bauer Reporter: Steve Kwee Created: Thu, 6 Nov 2003 7:04 AM Updated: Thu, 6 Nov 2003 8:29 AM Environment: Any Description: I would not call this a bug, but it's annoying. Every page of the wiki-dump of the documentation contains a <base href=""> in line 19 or so. It is impossible to browse the documentatin from the filesystem or a local webserver. The Version is 2.1 beta6, there was no entry for this. --------------------------------------------------------------------- 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-06 13:51:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 6 Nov 2003 7:50 AM
Oh gawd. This broke while refactoring. A parameter type of an overriding method was slightly wrong.
Thanks.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-460
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-460
Summary: Collection sort order bug when using cache
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1 rc1
Assignee:
Reporter: Matjaz Smolej
Created: Thu, 6 Nov 2003 7:28 AM
Updated: Thu, 6 Nov 2003 7:50 AM
Description:
I am using Hibernate 2.1 beta 6. I have a collection property mapped as:
<set
name="partyRoleSet"
lazy="true"
inverse="true"
cascade="all"
sort="natural"
>
<jcs-cache
usage="read-write"
/>
<key
column="Party_ID"
/>
<one-to-many
class="entity.PartyRoleEntity"
/>
</set>
The natural sort order is specified and read-write caching is enabled.
When reading a collection mapped this way for the first time, the sort order is correct, however, on the next read, the elements are not properly sorted. Here is the snapshot of the debug info for the same collection before and after caching:
First read:
m_partyRoleSet= net.sf.hibernate.collection.SortedSet (id=16050)
additions= null
collectionSnapshot= net.sf.hibernate.impl.SessionImpl$CollectionEntry (id=16062)
currentKey= null
currentPersister= null
dirty= false
dorecreate= false
doremove= false
doupdate= false
initialized= true
loadedKey= java.lang.Long (id=16036)
loadedPersister= net.sf.hibernate.collection.OneToManyPersister (id=16073)
processed= false
reached= false
role= "entity.PartyEntity.partyRoleSet"
snapshot= java.util.HashMap (id=16075)
comparator= null
directlyAccessible= false
initialized= true
session= net.sf.hibernate.impl.SessionImpl (id=16065)
set= java.util.TreeSet (id=16066)
keySet= java.util.TreeMap$1 (id=16071)
m= java.util.TreeMap (id=16072)
tempList= null
Second read:
m_partyRoleSet= net.sf.hibernate.collection.Set (id=16097)
additions= null
collectionSnapshot= net.sf.hibernate.impl.SessionImpl$CollectionEntry (id=16105)
currentKey= null
currentPersister= null
dirty= false
dorecreate= false
doremove= false
doupdate= false
initialized= true
loadedKey= java.lang.Long (id=16090)
loadedPersister= net.sf.hibernate.collection.OneToManyPersister (id=16073)
processed= false
reached= false
role= "entity.PartyEntity.partyRoleSet"
snapshot= java.util.HashMap (id=16108)
directlyAccessible= false
initialized= true
session= net.sf.hibernate.impl.SessionImpl (id=16106)
set= java.util.HashSet (id=16107)
map= java.util.HashMap (id=16109)
tempList= null
Note that the collection type changed from SortedSet to Set. It seems like sorted collections are not cached or retrieved in a proper way.
---------------------------------------------------------------------
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-06 13:46:14
|
The following comment has been added to this issue:
Author: Matjaz Smolej
Created: Thu, 6 Nov 2003 7:45 AM
Body:
One other thing: this worked in beta 4, haven't checked with beta 5.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-460
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-460
Summary: Collection sort order bug when using cache
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Assignee:
Reporter: Matjaz Smolej
Created: Thu, 6 Nov 2003 7:28 AM
Updated: Thu, 6 Nov 2003 7:28 AM
Description:
I am using Hibernate 2.1 beta 6. I have a collection property mapped as:
<set
name="partyRoleSet"
lazy="true"
inverse="true"
cascade="all"
sort="natural"
>
<jcs-cache
usage="read-write"
/>
<key
column="Party_ID"
/>
<one-to-many
class="entity.PartyRoleEntity"
/>
</set>
The natural sort order is specified and read-write caching is enabled.
When reading a collection mapped this way for the first time, the sort order is correct, however, on the next read, the elements are not properly sorted. Here is the snapshot of the debug info for the same collection before and after caching:
First read:
m_partyRoleSet= net.sf.hibernate.collection.SortedSet (id=16050)
additions= null
collectionSnapshot= net.sf.hibernate.impl.SessionImpl$CollectionEntry (id=16062)
currentKey= null
currentPersister= null
dirty= false
dorecreate= false
doremove= false
doupdate= false
initialized= true
loadedKey= java.lang.Long (id=16036)
loadedPersister= net.sf.hibernate.collection.OneToManyPersister (id=16073)
processed= false
reached= false
role= "entity.PartyEntity.partyRoleSet"
snapshot= java.util.HashMap (id=16075)
comparator= null
directlyAccessible= false
initialized= true
session= net.sf.hibernate.impl.SessionImpl (id=16065)
set= java.util.TreeSet (id=16066)
keySet= java.util.TreeMap$1 (id=16071)
m= java.util.TreeMap (id=16072)
tempList= null
Second read:
m_partyRoleSet= net.sf.hibernate.collection.Set (id=16097)
additions= null
collectionSnapshot= net.sf.hibernate.impl.SessionImpl$CollectionEntry (id=16105)
currentKey= null
currentPersister= null
dirty= false
dorecreate= false
doremove= false
doupdate= false
initialized= true
loadedKey= java.lang.Long (id=16090)
loadedPersister= net.sf.hibernate.collection.OneToManyPersister (id=16073)
processed= false
reached= false
role= "entity.PartyEntity.partyRoleSet"
snapshot= java.util.HashMap (id=16108)
directlyAccessible= false
initialized= true
session= net.sf.hibernate.impl.SessionImpl (id=16106)
set= java.util.HashSet (id=16107)
map= java.util.HashMap (id=16109)
tempList= null
Note that the collection type changed from SortedSet to Set. It seems like sorted collections are not cached or retrieved in a proper way.
---------------------------------------------------------------------
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-06 13:28:13
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-460 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-460 Summary: Collection sort order bug when using cache Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Matjaz Smolej Created: Thu, 6 Nov 2003 7:28 AM Updated: Thu, 6 Nov 2003 7:28 AM Description: I am using Hibernate 2.1 beta 6. I have a collection property mapped as: <set name="partyRoleSet" lazy="true" inverse="true" cascade="all" sort="natural" > <jcs-cache usage="read-write" /> <key column="Party_ID" /> <one-to-many class="entity.PartyRoleEntity" /> </set> The natural sort order is specified and read-write caching is enabled. When reading a collection mapped this way for the first time, the sort order is correct, however, on the next read, the elements are not properly sorted. Here is the snapshot of the debug info for the same collection before and after caching: First read: m_partyRoleSet= net.sf.hibernate.collection.SortedSet (id=16050) additions= null collectionSnapshot= net.sf.hibernate.impl.SessionImpl$CollectionEntry (id=16062) currentKey= null currentPersister= null dirty= false dorecreate= false doremove= false doupdate= false initialized= true loadedKey= java.lang.Long (id=16036) loadedPersister= net.sf.hibernate.collection.OneToManyPersister (id=16073) processed= false reached= false role= "entity.PartyEntity.partyRoleSet" snapshot= java.util.HashMap (id=16075) comparator= null directlyAccessible= false initialized= true session= net.sf.hibernate.impl.SessionImpl (id=16065) set= java.util.TreeSet (id=16066) keySet= java.util.TreeMap$1 (id=16071) m= java.util.TreeMap (id=16072) tempList= null Second read: m_partyRoleSet= net.sf.hibernate.collection.Set (id=16097) additions= null collectionSnapshot= net.sf.hibernate.impl.SessionImpl$CollectionEntry (id=16105) currentKey= null currentPersister= null dirty= false dorecreate= false doremove= false doupdate= false initialized= true loadedKey= java.lang.Long (id=16090) loadedPersister= net.sf.hibernate.collection.OneToManyPersister (id=16073) processed= false reached= false role= "entity.PartyEntity.partyRoleSet" snapshot= java.util.HashMap (id=16108) directlyAccessible= false initialized= true session= net.sf.hibernate.impl.SessionImpl (id=16106) set= java.util.HashSet (id=16107) map= java.util.HashMap (id=16109) tempList= null Note that the collection type changed from SortedSet to Set. It seems like sorted collections are not cached or retrieved in a proper way. --------------------------------------------------------------------- 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-06 13:22:15
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@hi...)
Date: Thu, 6 Nov 2003 7:22 AM
Changes:
Comment changed from to
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-380
Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
Type: Improvement
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee: Gavin King
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:02 AM
Updated: Thu, 6 Nov 2003 7:22 AM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.
Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-11-06 13:22:15
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 6 Nov 2003 7:21 AM
Body:
Patch is looking good now. Thanks everyone!
But I don't think I'll apply it until after 2.1 final. (Which is soon, I hope.)
Lets make it a feature for 2.1.1.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-380
Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
Type: Improvement
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee: Gavin King
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:02 AM
Updated: Wed, 5 Nov 2003 1:36 PM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.
Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-11-06 13:22:14
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 6 Nov 2003 7:21 AM
Body:
Patch is looking good now. Thanks everyone!
But I don't think I'll apply it until after 2.1 final. (Which is soon, I hope.)
Lets make it a feature for 2.0.1.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-380
Summary: Use ResultSet.getGeneratedKeys() when supported by JDBC driver
Type: Improvement
Status: Assigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee: Gavin King
Reporter: David Morris
Created: Sat, 4 Oct 2003 1:02 AM
Updated: Wed, 5 Nov 2003 1:36 PM
Environment: JDBC 3.0 Drivers with 1.4 JDKs. MySql and DB2 both have JDBC drivers that support get generated keys.
Description:
Retrieve ResultSet of natively generated keys after inserting records into databases that provide this support. Performance is genrally better with this technique. The code change should be backward compatable with 1.3 JREs and older JDBC drivers.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-11-06 13:05:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-459 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-459 Summary: documentation in distribution seems to be broken Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Assignee: Reporter: Steve Kwee Created: Thu, 6 Nov 2003 7:04 AM Updated: Thu, 6 Nov 2003 7:04 AM Environment: Any Description: I would not call this a bug, but it's annoying. Every page of the wiki-dump of the documentation contains a <base href=""> in line 19 or so. It is impossible to browse the documentatin from the filesystem or a local webserver. The Version is 2.1 beta6, there was no entry for this. --------------------------------------------------------------------- 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-06 08:31:14
|
The following comment has been added to this issue:
Author: Dieter Bogdoll
Created: Thu, 6 Nov 2003 2:30 AM
Body:
To lock the data of a SELECT you have to specifiy for each table the table hints HOLDLOCK,XLOCK.
SELECT ... FOR table_name WITH (HOLDLOCK,XLOCK)
If the transaction isolation level is SERIALIZABLE or a user tries to do a SELECT with the table hint SERIALIZABLE on the same data he will be locked until the first transaction is commited/aborted.
So the user has to do two things to work with looks in MS SQLServer:
1. Apply the necessary table hints for the SELECTs
2. Either change the isolation level to SERILIZABLE or apply the table hint SERIALIZABLE to SELECTSs which should block.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-456
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-456
Summary: Select for update isn't supported for MS SQLServer
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Assignee:
Reporter: Dieter Bogdoll
Created: Wed, 5 Nov 2003 3:51 AM
Updated: Wed, 5 Nov 2003 3:51 AM
Environment: MS SQLServer 6.5, 7, 2000
Description:
MS SQLServer doesn't support the "FOR UPDATE" keyword within the SELECT statement.
But it is possible to create the same effect with table hints.
Hibernate just add "FOR UPDATE" behind the select to lock objects.
This has to be changed for the MS SQLServer.
After each table name the correct table hints has to be written.
---------------------------------------------------------------------
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.
