Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: <leg...@at...> - 2003-10-31 10:41:14
|
The following comment has been added to this issue:
Author: Maarten Coene
Created: Fri, 31 Oct 2003 4:40 AM
Body:
I did search the forum and none of the 2 solutions is a good one:
1. http://forum.hibernate.org/old//809065.html
The first solutions tells met to use the --default-table-type=InnoDB setting of the MySQL database which is not possible in my case.
2. http://forum.hibernate.org/old//856390.html
The second solution is similar to my solution and also requires modifications to the hibernate sources. But I think my solution is better because you don't have to check if the specific Dialect is an instance of the MySQL4Dialect. (In my case this would mean that the hibernate sources would have a dependency to my custom dialect and this is something you don't want to)
I just want a solution for this problem where I don't have to patch the hibernate sources and can use the official hibernate releases.
Maarten Coene
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-441
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-441
Summary: Allow dialect specific table options in create table scripts
Type: Improvement
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Assignee:
Reporter: Maarten Coene
Created: Fri, 31 Oct 2003 4:24 AM
Updated: Fri, 31 Oct 2003 4:27 AM
Environment: all
Description:
Hi,
I need support for table_options in the MySQL create table syntax. The MySQL create syntax looks like:
CREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name [(create_definition,...)]
[table_options] [select_statement]
I don't know if ohter databases can have table_options in their create scripts.
The reason I need this is that I want to create tables using the SchemaExport tool and these tables must have the InnoDB type, this means I have to create SQL commands like:
CREATE mytable (...) TYPE=INNODB;
I want to solve my problem by creating my own dialect (e.g. InnoDbMySQLDialect extends MySQLDialect) but I didn't find a way to specify these table_options with the current implementation.
To allow these table_options, I propose the following mimimal changes to your code:
1. add this method to Dialect.java:
public String getTableOptions() {
return "";
}
2. change the sqlCreateString(Dialect dialect, Mapping p) method of Table.java (add this to the end of the method):
buf.append(StringHelper.CLOSE_PAREN);
buf.append(" "); // ADD THIS LINE
buf.append(dialect.getTableOptions()); // ADD THIS LINE
return buf.toString();
This way, I can easily create my own dialect:
public class InnoDbMySQLDialect extends MySQLDialect {
public String getTableOptions() {
return "TYPE=INNODB";
}
}
kind regards,
Maarten Coene
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-31 10:28:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 31 Oct 2003 4:27 AM
Search the forums for two solutions to this problem.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-441
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-441
Summary: Allow dialect specific table options in create table scripts
Type: Improvement
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Assignee:
Reporter: Maarten Coene
Created: Fri, 31 Oct 2003 4:24 AM
Updated: Fri, 31 Oct 2003 4:27 AM
Environment: all
Description:
Hi,
I need support for table_options in the MySQL create table syntax. The MySQL create syntax looks like:
CREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name [(create_definition,...)]
[table_options] [select_statement]
I don't know if ohter databases can have table_options in their create scripts.
The reason I need this is that I want to create tables using the SchemaExport tool and these tables must have the InnoDB type, this means I have to create SQL commands like:
CREATE mytable (...) TYPE=INNODB;
I want to solve my problem by creating my own dialect (e.g. InnoDbMySQLDialect extends MySQLDialect) but I didn't find a way to specify these table_options with the current implementation.
To allow these table_options, I propose the following mimimal changes to your code:
1. add this method to Dialect.java:
public String getTableOptions() {
return "";
}
2. change the sqlCreateString(Dialect dialect, Mapping p) method of Table.java (add this to the end of the method):
buf.append(StringHelper.CLOSE_PAREN);
buf.append(" "); // ADD THIS LINE
buf.append(dialect.getTableOptions()); // ADD THIS LINE
return buf.toString();
This way, I can easily create my own dialect:
public class InnoDbMySQLDialect extends MySQLDialect {
public String getTableOptions() {
return "TYPE=INNODB";
}
}
kind regards,
Maarten Coene
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-31 10:24:24
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-441 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-441 Summary: Allow dialect specific table options in create table scripts Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Maarten Coene Created: Fri, 31 Oct 2003 4:24 AM Updated: Fri, 31 Oct 2003 4:24 AM Environment: all Description: Hi, I need support for table_options in the MySQL create table syntax. The MySQL create syntax looks like: CREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name [(create_definition,...)] [table_options] [select_statement] I don't know if ohter databases can have table_options in their create scripts. The reason I need this is that I want to create tables using the SchemaExport tool and these tables must have the InnoDB type, this means I have to create SQL commands like: CREATE mytable (...) TYPE=INNODB; I want to solve my problem by creating my own dialect (e.g. InnoDbMySQLDialect extends MySQLDialect) but I didn't find a way to specify these table_options with the current implementation. To allow these table_options, I propose the following mimimal changes to your code: 1. add this method to Dialect.java: public String getTableOptions() { return ""; } 2. change the sqlCreateString(Dialect dialect, Mapping p) method of Table.java (add this to the end of the method): buf.append(StringHelper.CLOSE_PAREN); buf.append(" "); // ADD THIS LINE buf.append(dialect.getTableOptions()); // ADD THIS LINE return buf.toString(); This way, I can easily create my own dialect: public class InnoDbMySQLDialect extends MySQLDialect { public String getTableOptions() { return "TYPE=INNODB"; } } kind regards, Maarten Coene --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-31 09:27:13
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-440 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-440 Summary: Direct collection property access Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 5 Assignee: Reporter: Alexey Kaigorodov Created: Fri, 31 Oct 2003 3:26 AM Updated: Fri, 31 Oct 2003 3:26 AM Description: <bag name="..." access="field"> ... </bag> causes exception unless exists getter net.sf.hibernate.MappingException: Problem trying to set property type by reflection at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103) at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953) at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946) at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313) at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143) at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243) at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266) at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349) at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320) ... Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ... -- With best regards, Alexey --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-31 05:41:15
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 30 Oct 2003 11:40 PM
I implemented Session.cancelQuery()
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-439
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-439
Summary: Ability to cancel query from a separate thread
Type: New Feature
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 rc1
Versions:
2.0.3
Assignee:
Reporter: Jeff Rhines
Created: Thu, 30 Oct 2003 6:09 PM
Updated: Thu, 30 Oct 2003 11:40 PM
Environment: Hib2.0.3/My App/JDK1.4.2/Win2000/Dell PC/Grey Cubical Walls/etc.
Description:
Need a way to allow a user to cancel a running query. Tried Session.close() to pull the connection out from under the query, but received a ConcurrentModificationException on SessionImpl:1949. Reasonable, as the documentation claims Session implementations are not required to be thread safe. So, it would be nice to have a feature so one thread could cancel a query being actively run by another thread. Maybe similar to (or using?) java.sql.Statement.cancel()?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-31 00:14:13
|
The following comment has been added to this issue:
Author: Jeff Rhines
Created: Thu, 30 Oct 2003 6:13 PM
Body:
Forgot to mention it's Oracle9i with the Thin driver, though using OCI is not out of the question (for me, anyway... don't remember if Hib has any particular req). Dunno if it matters.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-439
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-439
Summary: Ability to cancel query from a separate thread
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee:
Reporter: Jeff Rhines
Created: Thu, 30 Oct 2003 6:09 PM
Updated: Thu, 30 Oct 2003 6:09 PM
Environment: Hib2.0.3/My App/JDK1.4.2/Win2000/Dell PC/Grey Cubical Walls/etc.
Description:
Need a way to allow a user to cancel a running query. Tried Session.close() to pull the connection out from under the query, but received a ConcurrentModificationException on SessionImpl:1949. Reasonable, as the documentation claims Session implementations are not required to be thread safe. So, it would be nice to have a feature so one thread could cancel a query being actively run by another thread. Maybe similar to (or using?) java.sql.Statement.cancel()?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-31 00:10:13
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-439 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-439 Summary: Ability to cancel query from a separate thread Type: New Feature Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: Jeff Rhines Created: Thu, 30 Oct 2003 6:09 PM Updated: Thu, 30 Oct 2003 6:09 PM Environment: Hib2.0.3/My App/JDK1.4.2/Win2000/Dell PC/Grey Cubical Walls/etc. Description: Need a way to allow a user to cancel a running query. Tried Session.close() to pull the connection out from under the query, but received a ConcurrentModificationException on SessionImpl:1949. Reasonable, as the documentation claims Session implementations are not required to be thread safe. So, it would be nice to have a feature so one thread could cancel a query being actively run by another thread. Maybe similar to (or using?) java.sql.Statement.cancel()? --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-30 23:55:13
|
The following comment has been added to this issue:
Author: John Kristian
Created: Thu, 30 Oct 2003 5:54 PM
Body:
Yes, but at DEBUG level, and via the same log4j category as many other messages of more limited interest. The people who will support my Hibernate-based application strongly prefer to enable/disable SQL tracing independent of all the other messages logged via BatcherImpl.log. I imagine many others will, too.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-438
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-438
Summary: Log SQL
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Kristian
Created: Thu, 30 Oct 2003 2:52 PM
Updated: Thu, 30 Oct 2003 2:52 PM
Description:
Please log executed SQL, in addition to (or instead of) passing it to System.out.println. System.out is useful for development. But logging is often better in a production server; for example, when System.out is directed to /dev/null.
The patch logSql.diff-u (attached) works for me.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 23:03:13
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 30 Oct 2003 5:02 PM
Body:
Hibernate /does/ log the SQL....
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-438
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-438
Summary: Log SQL
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Kristian
Created: Thu, 30 Oct 2003 2:52 PM
Updated: Thu, 30 Oct 2003 2:52 PM
Description:
Please log executed SQL, in addition to (or instead of) passing it to System.out.println. System.out is useful for development. But logging is often better in a production server; for example, when System.out is directed to /dev/null.
The patch logSql.diff-u (attached) works for me.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 22:57:14
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@hi...)
Assigner: Gavin King (mailto:ga...@hi...)
Date: Thu, 30 Oct 2003 4:57 PM
Comment:
Thanks. I'll accept this patch.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-436
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-436
Summary: Divide QueryCache in multiple regions
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee: Gavin King
Reporter: Mikheil Kapanadze
Created: Thu, 30 Oct 2003 9:06 AM
Updated: Thu, 30 Oct 2003 4:57 PM
Description:
Hibernate uses one instance of query cache for all cached queries. In some cases user may want to store query results in the different caches instead of using "main" one.
Here is a description of the major changes
1. There were 2 caches in QueryCache.java - query cache itself and timestamp cache. The last one was moved to the separate class, because we didn't divide that cache.
2. cacheRegion property was added to the Query and QueryParameter classes
3. There is a new method, getQueryCache(String cacheRegion) in SessionFactoryImpl. It returns query cache, stored in the internal map or creates new one and puts it there. It also destroys all these caches in the close() method.
4. There are some minor changes, too. For example, default query cache's region name was changed to net.sf.hibernate.cache.QueryCache. This was done as object cache's region name equals to classname and there may be conflict in naming if someone has QueryCache class (without package) in his code.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 22:57:14
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@hi...)
Assigner: Gavin King (mailto:ga...@hi...)
Date: Thu, 30 Oct 2003 4:56 PM
Comment:
Thanks. I'll accept this patch.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-437
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-437
Summary: Add Dialect for Microsoft SQL Server
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee: Gavin King
Reporter: John Kristian
Created: Thu, 30 Oct 2003 1:20 PM
Updated: Thu, 30 Oct 2003 4:56 PM
Environment: Microsoft SQL Server
Description:
Please enable Hibernate to work with Microsoft SQL Server, using Transact-SQL statements of the form "INSERT ... SELECT SCOPE_IDENTITY()" to insert a row whose identifier is generated by the database.
The patch mssql.zip (attached) works for me. If you like, I'll gladly make additional changes to clean up the indentation and exception handling. <mailto:jkr...@do...>
A related forum thread is http://forum.hibernate.org/viewtopic.php?p=2176297
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 20:53:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-438 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-438 Summary: Log SQL Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 beta 4 Assignee: Reporter: John Kristian Created: Thu, 30 Oct 2003 2:52 PM Updated: Thu, 30 Oct 2003 2:52 PM Description: Please log executed SQL, in addition to (or instead of) passing it to System.out.println. System.out is useful for development. But logging is often better in a production server; for example, when System.out is directed to /dev/null. The patch logSql.diff-u (attached) works for me. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-30 20:53:14
|
The following issue has been updated:
Updater: John Kristian (mailto:jkr...@do...)
Date: Thu, 30 Oct 2003 2:52 PM
Changes:
Attachment changed to logSql.diff-u
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-438&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-438
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-438
Summary: Log SQL
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Kristian
Created: Thu, 30 Oct 2003 2:52 PM
Updated: Thu, 30 Oct 2003 2:52 PM
Description:
Please log executed SQL, in addition to (or instead of) passing it to System.out.println. System.out is useful for development. But logging is often better in a production server; for example, when System.out is directed to /dev/null.
The patch logSql.diff-u (attached) works for me.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 19:22:14
|
The following issue has been updated:
Updater: John Kristian (mailto:jkr...@do...)
Date: Thu, 30 Oct 2003 1:21 PM
Changes:
Attachment changed to mssql.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-437&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-437
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-437
Summary: Add Dialect for Microsoft SQL Server
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Kristian
Created: Thu, 30 Oct 2003 1:20 PM
Updated: Thu, 30 Oct 2003 1:21 PM
Environment: Microsoft SQL Server
Description:
Please enable Hibernate to work with Microsoft SQL Server, using Transact-SQL statements of the form "INSERT ... SELECT SCOPE_IDENTITY()" to insert a row whose identifier is generated by the database.
The patch mssql.zip (attached) works for me. If you like, I'll gladly make additional changes to clean up the indentation and exception handling. <mailto:jkr...@do...>
A related forum thread is http://forum.hibernate.org/viewtopic.php?p=2176297
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 19:22:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-437 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-437 Summary: Add Dialect for Microsoft SQL Server Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 4 Assignee: Reporter: John Kristian Created: Thu, 30 Oct 2003 1:20 PM Updated: Thu, 30 Oct 2003 1:20 PM Environment: Microsoft SQL Server Description: Please enable Hibernate to work with Microsoft SQL Server, using Transact-SQL statements of the form "INSERT ... SELECT SCOPE_IDENTITY()" to insert a row whose identifier is generated by the database. The patch mssql.zip (attached) works for me. If you like, I'll gladly make additional changes to clean up the indentation and exception handling. <mailto:jkr...@do...> A related forum thread is http://forum.hibernate.org/viewtopic.php?p=2176297 --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-30 16:32:14
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Thu, 30 Oct 2003 10:31 AM
Body:
Michail - this should already be possible in HQL...everything it does not recognize is sent further down to the database..
Secondly, if you look at the OracleDialect you should be able to register your own functions ...just do what OracleDialect do in your own dialect ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-158
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-158
Summary: Customizable SQL
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: TURIN ACCOUNT
Created: Tue, 8 Jul 2003 3:38 PM
Updated: Tue, 8 Jul 2003 3:38 PM
Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database. This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 16:14:13
|
The following comment has been added to this issue:
Author: Per-Erik Lindskog
Created: Thu, 30 Oct 2003 10:13 AM
Body:
Accidentally this issue was tagged as Hibernate 1.2, it should really be 2.1
/ Perre
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-15
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HBI-15
Summary: Suggstion: Make mapping optional in configuration-DTD
Type: Improvement
Status: Unassigned
Priority: Trivial
Project: Hibernate 1.2
Assignee:
Reporter: Per-Erik Lindskog
Created: Thu, 30 Oct 2003 10:09 AM
Updated: Thu, 30 Oct 2003 10:09 AM
Description:
When I create Configurations in more than one EJB in JBoss, there seem to occur a confusion that makes all the different EJB:s pick the hibernate.cfg.xml from the same ejb-jar.
To get around that I use addClass() to define all the mappings in each EJB, but I still use the xml for the rest of the definitions. They are the same for all the EJB:s.
This works fine, but I get a SAXParserWarning telling me that I must have at least one mapping in the xml. This seem to be an estethical problem, but still...
/ Perre
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 16:11:13
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-15 Here is an overview of the issue: --------------------------------------------------------------------- Key: HBI-15 Summary: Suggstion: Make mapping optional in configuration-DTD Type: Improvement Status: Unassigned Priority: Trivial Project: Hibernate 1.2 Assignee: Reporter: Per-Erik Lindskog Created: Thu, 30 Oct 2003 10:09 AM Updated: Thu, 30 Oct 2003 10:09 AM Description: When I create Configurations in more than one EJB in JBoss, there seem to occur a confusion that makes all the different EJB:s pick the hibernate.cfg.xml from the same ejb-jar. To get around that I use addClass() to define all the mappings in each EJB, but I still use the xml for the rest of the definitions. They are the same for all the EJB:s. This works fine, but I get a SAXParserWarning telling me that I must have at least one mapping in the xml. This seem to be an estethical problem, but still... / Perre --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-30 16:09:13
|
The following comment has been added to this issue:
Author: Michail Jekimov
Created: Thu, 30 Oct 2003 10:08 AM
Body:
I would wish something similar, but on the HQL level. We are using Hibernate with the Oracle DBMS and I would like to be able to use my own PL/SQL function in my HQL queries (I would pass some scalar value to this function and it would return another scalar value, just like a built-in TO_CHAR function).
Another way to do that is to use session.createSQLQuery(), but I don't want to depend on SQL just for this need.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-158
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-158
Summary: Customizable SQL
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: TURIN ACCOUNT
Created: Tue, 8 Jul 2003 3:38 PM
Updated: Tue, 8 Jul 2003 3:38 PM
Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database. This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 15:08:16
|
The following issue has been updated:
Updater: Mikheil Kapanadze (mailto:mi...@di...)
Date: Thu, 30 Oct 2003 9:07 AM
Comment:
The attached QueryCache.zip file contains patch for this issue
Changes:
Attachment changed to QueryCache.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-436&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-436
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-436
Summary: Divide QueryCache in multiple regions
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Mikheil Kapanadze
Created: Thu, 30 Oct 2003 9:06 AM
Updated: Thu, 30 Oct 2003 9:07 AM
Description:
Hibernate uses one instance of query cache for all cached queries. In some cases user may want to store query results in the different caches instead of using "main" one.
Here is a description of the major changes
1. There were 2 caches in QueryCache.java - query cache itself and timestamp cache. The last one was moved to the separate class, because we didn't divide that cache.
2. cacheRegion property was added to the Query and QueryParameter classes
3. There is a new method, getQueryCache(String cacheRegion) in SessionFactoryImpl. It returns query cache, stored in the internal map or creates new one and puts it there. It also destroys all these caches in the close() method.
4. There are some minor changes, too. For example, default query cache's region name was changed to net.sf.hibernate.cache.QueryCache. This was done as object cache's region name equals to classname and there may be conflict in naming if someone has QueryCache class (without package) in his code.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 15:06:15
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-436 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-436 Summary: Divide QueryCache in multiple regions Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: Mikheil Kapanadze Created: Thu, 30 Oct 2003 9:06 AM Updated: Thu, 30 Oct 2003 9:06 AM Description: Hibernate uses one instance of query cache for all cached queries. In some cases user may want to store query results in the different caches instead of using "main" one. Here is a description of the major changes 1. There were 2 caches in QueryCache.java - query cache itself and timestamp cache. The last one was moved to the separate class, because we didn't divide that cache. 2. cacheRegion property was added to the Query and QueryParameter classes 3. There is a new method, getQueryCache(String cacheRegion) in SessionFactoryImpl. It returns query cache, stored in the internal map or creates new one and puts it there. It also destroys all these caches in the close() method. 4. There are some minor changes, too. For example, default query cache's region name was changed to net.sf.hibernate.cache.QueryCache. This was done as object cache's region name equals to classname and there may be conflict in naming if someone has QueryCache class (without package) in his code. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-30 11:35:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 30 Oct 2003 5:33 AM
applied this.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-435
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-435
Summary: Allow create sequence to have parameters
Type: Improvement
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Mathias Bogaert
Created: Thu, 30 Oct 2003 2:00 AM
Updated: Thu, 30 Oct 2003 5:33 AM
Description:
Patch allows for sequences to have parameters.
Usage:
@hibernate.id column="NATCORR_ID" generator-class="native"
@hibernate.generator-param name="sequence" value="AUD_REF_NATIONAL_CORRESP_SEQ"
@hibernate.generator-param name="parameters" value="START WITH 1 NOCACHE"
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 08:02:33
|
The following issue has been updated:
Updater: Mathias Bogaert (mailto:pa...@pa...)
Date: Thu, 30 Oct 2003 2:00 AM
Changes:
Attachment changed to sequence.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-435&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-435
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-435
Summary: Allow create sequence to have parameters
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Mathias Bogaert
Created: Thu, 30 Oct 2003 2:00 AM
Updated: Thu, 30 Oct 2003 2:00 AM
Description:
Patch allows for sequences to have parameters.
Usage:
@hibernate.id column="NATCORR_ID" generator-class="native"
@hibernate.generator-param name="sequence" value="AUD_REF_NATIONAL_CORRESP_SEQ"
@hibernate.generator-param name="parameters" value="START WITH 1 NOCACHE"
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-30 08:00:34
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-435 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-435 Summary: Allow create sequence to have parameters Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: Mathias Bogaert Created: Thu, 30 Oct 2003 2:00 AM Updated: Thu, 30 Oct 2003 2:00 AM Description: Patch allows for sequences to have parameters. Usage: @hibernate.id column="NATCORR_ID" generator-class="native" @hibernate.generator-param name="sequence" value="AUD_REF_NATIONAL_CORRESP_SEQ" @hibernate.generator-param name="parameters" value="START WITH 1 NOCACHE" --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-29 23:28:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 29 Oct 2003 5:27 PM
We don't want to grow Hibernate's properties. We agreed that this should be addressed by making default values for these parameters settable on oscache, not in Hibernate.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-428
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-428
Summary: Update OSCache support to support properties
Type: Improvement
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Mathias Bogaert
Created: Tue, 28 Oct 2003 10:16 AM
Updated: Wed, 29 Oct 2003 5:27 PM
Description:
I've added support for various parameters. Also added a method to clear all cached, this can be used from eg. WebWork action.
---------------------------------------------------------------------
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.
