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-05-30 08:35:52
|
The following comment has been added to this issue:
Author: Mathias Bogaert
Created: Fri, 30 May 2003 2:37 AM
Body:
Your configuration file is wrong:
net.sf.hibernate.dialect.McKoiDialect
should be
net.sf.hibernate.dialect.MckoiDialect
(lower case Mckoi)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-104
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-104
Summary: Unable to locate dialect when only specified in properties file
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0rc2
Assignee:
Reporter: Axel Fontaine
Created: Sun, 25 May 2003 4:34 PM
Updated: Sun, 25 May 2003 4:34 PM
Environment: WinXP SP1, Eclipse 2.1, Hibernate 2.0 beta 6, McKoi 1.0.1
Description:
When using the following property file:
hibernate.dialect = net.sf.hibernate.dialect.McKoiDialect
hibernate.connection.driver_class = com.mckoi.JDBCDriver
hibernate.connection.url = jdbc:mckoi://localhost/
hibernate.connection.username = dbadmin
hibernate.connection.password = dbpass
hibernate complains that it can't find the dialect net.sf.hibernate.dialect.McKoiDialect
Adding this to the code makes it work:
Configuration config = new Configuration();
config.setProperty("hibernate.dialect", MckoiDialect.class.getName());
---------------------------------------------------------------------
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/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-05-30 04:59:18
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-115 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-115 Summary: Save after refresh object with unloaded lazy collections Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: Ivlev Dmitry Created: Thu, 29 May 2003 11:56 PM Updated: Thu, 29 May 2003 11:56 PM Description: Save after refresh object with unloaded lazy collections delete unloaded objects! Step by step: - I have class with childs (lazy collection) - I load class (childs are not loaded) - I refresh object (object refreshed but unloaded lazy collection becams empty collection) - I modify object fileds and don't touch childs - I save object (object is saved and all childs are DELETED!!!) --------------------------------------------------------------------- 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/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-05-30 01:57:55
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 29 May 2003 8:55 PM
this is allowed in Hibernate2
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-110
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-110
Summary: Provide a way to use hibernate.cfg.xml without JNDI
Type: Improvement
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Versions:
2.0rc2
Assignee: Gavin King
Reporter: Axel Fontaine
Created: Thu, 29 May 2003 4:42 AM
Updated: Thu, 29 May 2003 8:55 PM
Description:
Currently hibernate.cfg.xml can not be used as a drop-in replacement for hibernate.properties
This is really a shame!
There is really no reason why this shouldn't be the case.
And it is much nicer than all the config.addClass(XYZ) statements, as it moves this out of the code.
So, why not factor out the JNDI specific part in its own subclass?
---------------------------------------------------------------------
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/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-05-30 01:55:48
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@in...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-114 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-114 Summary: SchemaExportTask tries to open files as URLs Type: Patch Status: Assigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.0rc2 Assignee: Gavin King Reporter: Ken Geis Created: Thu, 29 May 2003 7:20 PM Updated: Thu, 29 May 2003 8:54 PM Environment: Windows XP, ant Description: I was using the SchemaExportTask for Ant in Windows. The input file name started with C:, so the SAXReader interpreted this as a URL with protocol "c." It should not be treated as a URL at all. In net.sf.hibernate.cfg.Configuration, change the method addFile from ---------------------------------------------------------- log.info("Mapping file: " + xmlFile); try { add( XMLHelper.createSAXReader(xmlFile).read(xmlFile) ); } catch (Exception e) { ----------------------------------------------------------- to ----------------------------------------------------------- log.info("Mapping file: " + xmlFile); try { add( XMLHelper.createSAXReader(xmlFile).read(new File(xmlFile)) ); } catch (Exception e) { ----------------------------------------------------------- --------------------------------------------------------------------- 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/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-05-30 01:53:50
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Thu, 29 May 2003 8:53 PM
Changes:
priority changed from Major to Minor
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-112&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-112
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-112
Summary: If connection not available, no exception thrown
Type: Bug
Status: Unassigned
Priority: Minor
Project: Hibernate2
Assignee:
Reporter: Chris Winters
Created: Thu, 29 May 2003 10:49 AM
Updated: Thu, 29 May 2003 8:53 PM
Environment: Hibernate 2.0 rc5
Description:
When building a SessionFactory with a 'Datasource' set I'd like to know if it fails to connect to the given datasource. Currently it just logs a message and keeps on going (lines 159-172 of SessionFactoryImpl). So once the SessionFactory is created I have no idea if this aspect failed or not. Having a status on the SessionFactory would be useful, probably even better would be a configuration setting (e.g., Environment.DIE_ON_FAILED_CONNECTION) that tells the constructor to throw an exception if the connection cannot be made.
---------------------------------------------------------------------
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/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-05-30 01:53:50
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@in...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Thu, 29 May 2003 8:52 PM
Comment:
i take a will look at this
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-113
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-113
Summary: Oracle LIMIT Bug (Was HB-88)
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee: Gavin King
Reporter: Leonardo Quijano
Created: Thu, 29 May 2003 7:19 PM
Updated: Thu, 29 May 2003 8:52 PM
Environment: CVS May 29, 2003
Description:
I'm reopening bug HB-88 (I don't know how to reopen bugs like in Bugzilla.. :( ). It's still wrong. Right now, we have in Oracle9Dialect:
public String getLimitString(String sql) {
StringBuffer pagingSelect = new StringBuffer(100);
pagingSelect.append("select * from ( select row_.*, rownum rownum_ from ( ");
pagingSelect.append(sql);
pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= ?");
return pagingSelect.toString();
}
From Oracle 9i Documentation (http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96540/sql_elements6a.htm#27457)
"ROWNUM
For each row returned by a query, the ROWNUM pseudocolumn returns a number indicating the order in which Oracle selects the row from a table or set of joined rows. The first row selected has a ROWNUM of 1, the second has 2, and so on."
In Hibernate's doc, it says:
"setFirstResult
public Query setFirstResult(int firstResult)
Set the first row to retrieve. If not set, rows will be retrieved beginnning from row 0. This method is more efficient if the JDBC driver supports scrollable ResultSets.
Parameters:
firstResult - a row number, numbered from 0"
So, if I call query.setFirstResult(0) - as documented - it should give me the first result in Oracle (Oracle ROWNUM 1). So maybe it should be:
pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ > ?");
or
pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= (? + 1)");
(don't know if the last one works, though).
I don't know if the value is increased in some other place... but it's still not working for me. I applied the change and it did work.
Leonardo
---------------------------------------------------------------------
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/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-05-30 01:09:15
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-114 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-114 Summary: SchemaExportTask tries to open files as URLs Type: Patch Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.0rc2 Assignee: Reporter: Ken Geis Created: Thu, 29 May 2003 7:20 PM Updated: Thu, 29 May 2003 7:20 PM Environment: Windows XP, ant Description: I was using the SchemaExportTask for Ant in Windows. The input file name started with C:, so the SAXReader interpreted this as a URL with protocol "c." It should not be treated as a URL at all. In net.sf.hibernate.cfg.Configuration, change the method addFile from ---------------------------------------------------------- log.info("Mapping file: " + xmlFile); try { add( XMLHelper.createSAXReader(xmlFile).read(xmlFile) ); } catch (Exception e) { ----------------------------------------------------------- to ----------------------------------------------------------- log.info("Mapping file: " + xmlFile); try { add( XMLHelper.createSAXReader(xmlFile).read(new File(xmlFile)) ); } catch (Exception e) { ----------------------------------------------------------- --------------------------------------------------------------------- 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/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-05-30 00:25:33
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-113 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-113 Summary: Oracle LIMIT Bug (Was HB-88) Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: Leonardo Quijano Created: Thu, 29 May 2003 7:19 PM Updated: Thu, 29 May 2003 7:19 PM Environment: CVS May 29, 2003 Description: I'm reopening bug HB-88 (I don't know how to reopen bugs like in Bugzilla.. :( ). It's still wrong. Right now, we have in Oracle9Dialect: public String getLimitString(String sql) { StringBuffer pagingSelect = new StringBuffer(100); pagingSelect.append("select * from ( select row_.*, rownum rownum_ from ( "); pagingSelect.append(sql); pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= ?"); return pagingSelect.toString(); } From Oracle 9i Documentation (http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96540/sql_elements6a.htm#27457) "ROWNUM For each row returned by a query, the ROWNUM pseudocolumn returns a number indicating the order in which Oracle selects the row from a table or set of joined rows. The first row selected has a ROWNUM of 1, the second has 2, and so on." In Hibernate's doc, it says: "setFirstResult public Query setFirstResult(int firstResult) Set the first row to retrieve. If not set, rows will be retrieved beginnning from row 0. This method is more efficient if the JDBC driver supports scrollable ResultSets. Parameters: firstResult - a row number, numbered from 0" So, if I call query.setFirstResult(0) - as documented - it should give me the first result in Oracle (Oracle ROWNUM 1). So maybe it should be: pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ > ?"); or pagingSelect.append(" ) row_ where rownum <= ?) where rownum_ >= (? + 1)"); (don't know if the last one works, though). I don't know if the value is increased in some other place... but it's still not working for me. I applied the change and it did work. Leonardo --------------------------------------------------------------------- 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/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-05-29 18:55:49
|
The following comment has been added to this issue:
Author: Chris Winters
Created: Thu, 29 May 2003 1:55 PM
Body:
Whoops -- I meant Hibernate 2.0 rc2, not rc5.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-112
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-112
Summary: If connection not available, no exception thrown
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Assignee:
Reporter: Chris Winters
Created: Thu, 29 May 2003 10:49 AM
Updated: Thu, 29 May 2003 10:49 AM
Environment: Hibernate 2.0 rc5
Description:
When building a SessionFactory with a 'Datasource' set I'd like to know if it fails to connect to the given datasource. Currently it just logs a message and keeps on going (lines 159-172 of SessionFactoryImpl). So once the SessionFactory is created I have no idea if this aspect failed or not. Having a status on the SessionFactory would be useful, probably even better would be a configuration setting (e.g., Environment.DIE_ON_FAILED_CONNECTION) that tells the constructor to throw an exception if the connection cannot be made.
---------------------------------------------------------------------
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/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-05-29 15:51:17
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-112 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-112 Summary: If connection not available, no exception thrown Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Chris Winters Created: Thu, 29 May 2003 10:49 AM Updated: Thu, 29 May 2003 10:49 AM Environment: Hibernate 2.0 rc5 Description: When building a SessionFactory with a 'Datasource' set I'd like to know if it fails to connect to the given datasource. Currently it just logs a message and keeps on going (lines 159-172 of SessionFactoryImpl). So once the SessionFactory is created I have no idea if this aspect failed or not. Having a status on the SessionFactory would be useful, probably even better would be a configuration setting (e.g., Environment.DIE_ON_FAILED_CONNECTION) that tells the constructor to throw an exception if the connection cannot be made. --------------------------------------------------------------------- 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/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-05-29 09:58:52
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-111 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-111 Summary: Invalid sql alias computation for fields with formulas... Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0rc2 Assignee: Reporter: Fabio Parise Created: Thu, 29 May 2003 4:58 AM Updated: Thu, 29 May 2003 4:58 AM Description: Trying to define a computed field (i.e. 'status1000' as the result of the following computation: status+1000; where 'status' is a table column) in this way: <property column="STATUS+1000" length="10" name="status1000" not-null="true" type="java.lang.Long" update="false" insert="false"/> if the first 7 chars of the attribute 'column' contains some non-valid chars for sql aliases, the produced SELECT statement will fail. In the example the alias for the computed field is 'STATUS+16_', which is not a valid sql alias. SELECT WkfPr0_.pkid as pkid, ..., WkfPr0_.STATUS+1000 as STATUS+16_ FROM WKF_PROCESS_CLASS WkfPr0_ WHERE WkfPr0_.pkid=? if the field involved in the formula has a longer name i.e. MYSTATUS --> formula=MYSTATUS+1000, the computed alias is MYSTATU16_, which is a valid alias. --------------------------------------------------------------------- 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/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-05-29 09:43:00
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-110 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-110 Summary: Provide a way to use hibernate.cfg.xml without JNDI Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0rc2 Assignee: Reporter: Axel Fontaine Created: Thu, 29 May 2003 4:42 AM Updated: Thu, 29 May 2003 4:42 AM Description: Currently hibernate.cfg.xml can not be used as a drop-in replacement for hibernate.properties This is really a shame! There is really no reason why this shouldn't be the case. And it is much nicer than all the config.addClass(XYZ) statements, as it moves this out of the code. So, why not factor out the JNDI specific part in its own subclass? --------------------------------------------------------------------- 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/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-05-28 00:18:09
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-109 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-109 Summary: Handle Entities with composite keys in HQL join criteria Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Assignee: Reporter: Gunther Schadow Created: Tue, 27 May 2003 7:17 PM Updated: Tue, 27 May 2003 7:17 PM Environment: any Description: Composite keys are a proper RDBMS idiom and Hibernate supports them fairly well. However, there are some non-orthogonal behaviors with composite keys in HQL. (1) while Entity types can be used in HQL join clauses (e.g., "from Person sibling1, Person sibling2 where sibling1.father = sibling2.father"), if the entity has a composite key, the above query stops working (non-atomic path.) (2) while one can pass an Entity type into a HQL bind variable (e.g., "from Person child where child.father = :father", where we setEntity("father",(Father)myFather);) this stops working when the entity has a composite key. Further investigation shows that in the case (2), the bind-variable mechanism of Hibernate already properly detects the case of composite keys and binds two variables in the java.sql.PreparedStatement. However, the statement that Hibernate generates can't handle the composite entity ids. The focus of the improvement would be somewhere in the hql.WhereParser or callers of it. At this point the WhereParser calls the PathExpressionParser.getWhereColumn() method instead of handling getWhereColumns(). The workaround is to write the HQL query (1) as "... where sibling1.father.id1 = sibling2.father.id1 AND sibling1.father.id2 = sibling2.father.id2 = ...", and for query (2) analogously. Notice also that HQL does not permit a composite bind variable's property to be accessed. So, "... where child.father.id1 = :father.id1 AND child.father.id2 = :father.id2 ..." is not possible to write (leads to all sorts of parser errors.) With ideomatic Java AND ideomatic RDBM, a mapper that can handle joins independent of whether keys are atomic or composite is highly desirable. That way a system is more stable vis-a-vis changes in the key strategy. The key design can be properly encapsulated and the details need not be exposed on the HQL layer. --------------------------------------------------------------------- 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/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-05-27 23:56:12
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-108 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-108 Summary: Mapping non-static inner classes Type: New Feature Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Assignee: Reporter: Gunther Schadow Created: Tue, 27 May 2003 6:55 PM Updated: Tue, 27 May 2003 6:55 PM Environment: any Description: It would be nice if Hibernate could handle true inner classes. For example, say you have a Person with several addresses: class Person { long id, String name, List/*<Address>*/ addresses class Address { String value; String purpose; } ... } whereas the database contains the two tables: CREATE TABLE Person ( id LONG NOT NULL PRIMARY KEY, name VARCHAR, ) CREATE TABLE PersonAddress ( personId LONG NOT NULL REFERENCES Person(id), value VARCHAR, purpose VARCHAR, PRIMARY KEY(personId, purpose); ) and the mapping file would contain <class name="Person" table="Person"> <id name="id" type="long">...</id> <property name="name" type="string"/> <bag name="addresses" lazy="true" table="PersonAddress"> <key column="personId"/> <composite-element class="Person$Address"> <property name="value" column="value" type="string"/> <property name="purpose" column="purpose" type="string"/> </composite-element> </bag> </class> Since personId is NOT NULL in the PersonAddress table, we know that we allways will have a Person if we load a PersonAddress, and, since PersonAddress is mapped as a composite element, we can't even load a Person$Address alone without having a Person in hand. Therefore all requirements for creating non-static inner classes are fulfilled. Workaround is of course to use a static inner class in which the implicit association to the parent class is made explicit. Since non-static inner classes are a proper idiom of Java, the goal of "persistence for idiomatic java" makes proper handling of non-static inner classes highly desirable. --------------------------------------------------------------------- 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/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-05-27 00:11:04
|
The following comment has been added to this issue:
Author: Paul Rivers
Created: Mon, 26 May 2003 7:10 PM
Body:
My main issue with using it in my code is that with the recommended approach, if you catch an "Exception" exception, then rethrow it, every single function that uses hibernate must declare that they throw "Exception"....
So each function:
public int getSomething() {
...
}
Now must be:
public int getSomething() throws Exception {
...
}
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-106
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-106
Summary: Minor flaw in suggested error handling
Type: Bug
Status: Closed
Priority: Trivial
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0rc2
Assignee: Gavin King
Reporter: Paul Rivers
Created: Sun, 25 May 2003 4:42 PM
Updated: Sun, 25 May 2003 8:33 PM
Environment: irrelevant
Description:
I wasn't sure where to put a documentation issue, I thought this would be the best place. Please let me know if this is incorrect, and I'll post elsewhere in the future.
In "6.9.4. Exception handling" in the documentation, the first exception handling idiom is recommended:
Session sess = factory.openSession();
Transaction tx = null;
try {
tx = sess.beginTransaction();
// do some work
...
tx.commit();
}
catch (Exception e) {
if (tx!=null) tx.rollback();
throw e;
}
finally {
sess.close();
}
However, notice the "catch (Exception e) {" line. If a RuntimeException is thrown, the catch block will never be entered, and the transaction will never be terminated. Thus that line should be replaced by "catch (Throwable e) {" so that the entire example will read:
Session sess = factory.openSession();
Transaction tx = null;
try {
tx = sess.beginTransaction();
// do some work
...
tx.commit();
}
catch (Throwable e) {
if (tx!=null) tx.rollback();
throw e;
}
finally {
sess.close();
}
This also applies to the next 2 examples in the documentation.
---------------------------------------------------------------------
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/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-05-26 08:55:03
|
The following issue has been updated:
Updater: Teodor Danciu (mailto:te...@ho...)
Date: Mon, 26 May 2003 3:54 AM
Comment:
Here's the version of the JdbsDatabaseInfo class that we use for schema update. It loads database metadata only when needed.
Changes:
Attachment changed from to JdbcDatabaseInfo.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-107&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-107
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-107
Summary: JdbcDatabaseInfo improvement
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
toolset
Versions:
2.0rc2
Assignee:
Reporter: Teodor Danciu
Created: Mon, 26 May 2003 3:51 AM
Updated: Mon, 26 May 2003 3:54 AM
Description:
The JdbcDatabaseInfo class tries to load all the
database metadata information when it is instantiated.
We found this inconvenient since in our Oracle database
we already have thousands of tables and retrieving the
whole metadata is time-consuming and inefficient in
case of simple updates (one or two tables).
We made some modifications in the JdbcDatabaseInfo
class so that the metadata information for each table be
loaded only when needed. Once the metadata for a table
loaded, it is kept in memory for later use.
---------------------------------------------------------------------
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/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-05-26 08:53:03
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-107 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-107 Summary: JdbcDatabaseInfo improvement Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.0rc2 Assignee: Reporter: Teodor Danciu Created: Mon, 26 May 2003 3:51 AM Updated: Mon, 26 May 2003 3:51 AM Description: The JdbcDatabaseInfo class tries to load all the database metadata information when it is instantiated. We found this inconvenient since in our Oracle database we already have thousands of tables and retrieving the whole metadata is time-consuming and inefficient in case of simple updates (one or two tables). We made some modifications in the JdbcDatabaseInfo class so that the metadata information for each table be loaded only when needed. Once the metadata for a table loaded, it is kept in memory for later use. --------------------------------------------------------------------- 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/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-05-26 01:37:03
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 25 May 2003 8:35 PM
SchemaExport does this already
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-105
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-105
Summary: hibernate should create hibernate_sequence if it doesn't already exist
Type: Improvement
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Assignee: Gavin King
Reporter: Axel Fontaine
Created: Sun, 25 May 2003 4:38 PM
Updated: Sun, 25 May 2003 8:35 PM
Environment: Hibernate 2.0 beta 6, McKoi 1.0.1
Description:
hibernate should create hibernate_sequence if it doesn't already exist
Or at least document that it needs a sequence called hibernate_sequence.
But I think automatic creation in the most user-friendly approach. (Might not be possible because of security though)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/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-05-26 01:35:03
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 25 May 2003 8:33 PM
RuntimeException inherits Exception. It is true that it wouldn't be called in the case of an Error. However, Errors are rare - its up you if you want to bother with them.
I prefer the current recommendation.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-106
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-106
Summary: Minor flaw in suggested error handling
Type: Bug
Status: Closed
Priority: Trivial
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0rc2
Assignee: Gavin King
Reporter: Paul Rivers
Created: Sun, 25 May 2003 4:42 PM
Updated: Sun, 25 May 2003 8:33 PM
Environment: irrelevant
Description:
I wasn't sure where to put a documentation issue, I thought this would be the best place. Please let me know if this is incorrect, and I'll post elsewhere in the future.
In "6.9.4. Exception handling" in the documentation, the first exception handling idiom is recommended:
Session sess = factory.openSession();
Transaction tx = null;
try {
tx = sess.beginTransaction();
// do some work
...
tx.commit();
}
catch (Exception e) {
if (tx!=null) tx.rollback();
throw e;
}
finally {
sess.close();
}
However, notice the "catch (Exception e) {" line. If a RuntimeException is thrown, the catch block will never be entered, and the transaction will never be terminated. Thus that line should be replaced by "catch (Throwable e) {" so that the entire example will read:
Session sess = factory.openSession();
Transaction tx = null;
try {
tx = sess.beginTransaction();
// do some work
...
tx.commit();
}
catch (Throwable e) {
if (tx!=null) tx.rollback();
throw e;
}
finally {
sess.close();
}
This also applies to the next 2 examples in the documentation.
---------------------------------------------------------------------
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/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-05-25 22:14:03
|
The following comment has been added to this issue:
Author: Paul Rivers
Created: Sun, 25 May 2003 5:13 PM
Body:
After further experimentation and thought, I realized the entire catch block was rather inconvenient. The original, again, was:
catch (Exception e) {
if (tx!=null) tx.rollback();
throw e;
}
finally {
sess.close();
}
However, catching a generic exception e then rethrowing it forces the function that contains the code to throw an "Exception" exception (public void functionName() throws Exception {}). (The same things happens if you're catching Throwable) This is obviously not desirable. Of course, you can catch the exact exceptions that could be thrown, but 1. This gets ugly when their are many exceptions 2. You still have to remember to catch RuntimeExeption. 3. You have to customize what it essentially boiler-plate code each time its used.
Instead, the code can be written so that the outline never needs to be changed, and will correctly handle all types of exceptions if it's written like this:
Session sess = factory.openSession();
Transaction tx = null;
try {
tx = sess.beginTransaction();
// do some work
//...
tx.commit();
}
finally {
if(tx != null && !tx.wasCommitted() && !tx.wasRolledBack()) tx.rollback();
sess.close();
}
(I'm not sure if calling Transaction.rollback() twice could possibly throw an exception, if it can't then the last conditional in the if statement could be removed).
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-106
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-106
Summary: Minor flaw in suggested error handling
Type: Bug
Status: Unassigned
Priority: Trivial
Project: Hibernate2
Versions:
2.0rc2
Assignee:
Reporter: Paul Rivers
Created: Sun, 25 May 2003 4:42 PM
Updated: Sun, 25 May 2003 4:42 PM
Environment: irrelevant
Description:
I wasn't sure where to put a documentation issue, I thought this would be the best place. Please let me know if this is incorrect, and I'll post elsewhere in the future.
In "6.9.4. Exception handling" in the documentation, the first exception handling idiom is recommended:
Session sess = factory.openSession();
Transaction tx = null;
try {
tx = sess.beginTransaction();
// do some work
...
tx.commit();
}
catch (Exception e) {
if (tx!=null) tx.rollback();
throw e;
}
finally {
sess.close();
}
However, notice the "catch (Exception e) {" line. If a RuntimeException is thrown, the catch block will never be entered, and the transaction will never be terminated. Thus that line should be replaced by "catch (Throwable e) {" so that the entire example will read:
Session sess = factory.openSession();
Transaction tx = null;
try {
tx = sess.beginTransaction();
// do some work
...
tx.commit();
}
catch (Throwable e) {
if (tx!=null) tx.rollback();
throw e;
}
finally {
sess.close();
}
This also applies to the next 2 examples in the documentation.
---------------------------------------------------------------------
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/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-05-25 21:44:03
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-106 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-106 Summary: Minor flaw in suggested error handling Type: Bug Status: Unassigned Priority: Trivial Project: Hibernate2 Versions: 2.0rc2 Assignee: Reporter: Paul Rivers Created: Sun, 25 May 2003 4:42 PM Updated: Sun, 25 May 2003 4:42 PM Environment: irrelevant Description: I wasn't sure where to put a documentation issue, I thought this would be the best place. Please let me know if this is incorrect, and I'll post elsewhere in the future. In "6.9.4. Exception handling" in the documentation, the first exception handling idiom is recommended: Session sess = factory.openSession(); Transaction tx = null; try { tx = sess.beginTransaction(); // do some work ... tx.commit(); } catch (Exception e) { if (tx!=null) tx.rollback(); throw e; } finally { sess.close(); } However, notice the "catch (Exception e) {" line. If a RuntimeException is thrown, the catch block will never be entered, and the transaction will never be terminated. Thus that line should be replaced by "catch (Throwable e) {" so that the entire example will read: Session sess = factory.openSession(); Transaction tx = null; try { tx = sess.beginTransaction(); // do some work ... tx.commit(); } catch (Throwable e) { if (tx!=null) tx.rollback(); throw e; } finally { sess.close(); } This also applies to the next 2 examples in the documentation. --------------------------------------------------------------------- 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/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-05-25 21:39:03
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-105 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-105 Summary: hibernate should create hibernate_sequence if it doesn't already exist Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Axel Fontaine Created: Sun, 25 May 2003 4:38 PM Updated: Sun, 25 May 2003 4:38 PM Environment: Hibernate 2.0 beta 6, McKoi 1.0.1 Description: hibernate should create hibernate_sequence if it doesn't already exist Or at least document that it needs a sequence called hibernate_sequence. But I think automatic creation in the most user-friendly approach. (Might not be possible because of security though) --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/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-05-25 21:35:03
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-104 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-104 Summary: Unable to locate dialect when only specified in properties file Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.0rc2 Assignee: Reporter: Axel Fontaine Created: Sun, 25 May 2003 4:34 PM Updated: Sun, 25 May 2003 4:34 PM Environment: WinXP SP1, Eclipse 2.1, Hibernate 2.0 beta 6, McKoi 1.0.1 Description: When using the following property file: hibernate.dialect = net.sf.hibernate.dialect.McKoiDialect hibernate.connection.driver_class = com.mckoi.JDBCDriver hibernate.connection.url = jdbc:mckoi://localhost/ hibernate.connection.username = dbadmin hibernate.connection.password = dbpass hibernate complains that it can't find the dialect net.sf.hibernate.dialect.McKoiDialect Adding this to the code makes it work: Configuration config = new Configuration(); config.setProperty("hibernate.dialect", MckoiDialect.class.getName()); --------------------------------------------------------------------- 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/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-05-25 16:47:03
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-103 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-103 Summary: Move tools et.al. to HibernateExt Type: Improvement Status: Assigned Priority: Minor Project: Hibernate2 Components: toolset Versions: 2.1 Assignee: Max Rydahl Andersen Reporter: Max Rydahl Andersen Created: Sun, 25 May 2003 11:46 AM Updated: Sun, 25 May 2003 11:46 AM Description: 1.Move hbm2java, class2hbm and ddl2hbm to HibernateExt/tools and create a HibernateExt/tools/build.xml to generate hibernate-tools.jar 2. Move jca, jmx to HibernateExt/j2eeopt and create a Hibernate/j2eeopt/build.xml to generate hibnerate-j2eeopt.jar 3. Move Hibern8IDE to HibernateExt/tools or is it to "heavy" for that part ? I guess the hibernateExt/xyz will have its own releases and be an ADDITION to the hibernate.jar ? --------------------------------------------------------------------- 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/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-05-25 16:45:03
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Sun, 25 May 2003 11:44 AM
Body:
working - and testing if jira notifications works.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-18
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-18
Summary: Integrate support for SQL queries
Type: New Feature
Status: In Progress
Priority: Major
Project: Hibernate2
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:08 AM
Updated: Mon, 19 May 2003 1:19 AM
Description:
Integrate support for SQL queries
To execute SQL in Hibernate one aquires a connection as normal
or via the session object.
This can really only be used to
fetch scalar values.
A real nice feature would be to be able to
provide SQL directly as an alternative to HQL. The SQL should
ofcourse return the named columns and data types that Hibernate
expects to be able to instantiate objects from the resultset.
(original: http://sourceforge.net/tracker/index.php?func=detail&aid=622605&group_id=40712&atid=428711=
---------------------------------------------------------------------
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/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.
