[Hibernate-JIRA] Updated: (HHH-1083) Customization of CREATE TABLE with storage clause etc.
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1083?page=c... ]
Steve Ebersole updated HHH-1083:
--------------------------------
Fix Version/s: (was: 4.1.0)
5.0.0
> Customization of CREATE TABLE with storage clause etc.
> ------------------------------------------------------
>
> Key: HHH-1083
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1083
> Project: Hibernate Core
> Issue Type: New Feature
> Components: core
> Reporter: Christian Bauer
> Assignee: Steve Ebersole
> Priority: Minor
> Fix For: 5.0.0
>
>
> Currently Hibernate features a hotfix for the MySQLInnoDBDialect:
> public String getTableTypeString() {
> return " type=InnoDB";
> }
> However, this is not the only appendix that is useful for CREATE TABLE. We should do several things:
> - allow appendix for CREATE INDEX, for example, to define the tablespace
> - pass in additional arguments to getTableTypeString(), such as tableName, schemaName, catalogName - for example, to allow custom Dialects to return different tablespaces for particular tables
> - probably rename the getTableTypeString() method to getTableAppendixString() and getIndexAppendixString()
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[Hibernate-JIRA] Created: (HHH-2434) No standard way to calculate date intervals in HQL
by Don Smith (JIRA)
No standard way to calculate date intervals in HQL
--------------------------------------------------
Key: HHH-2434
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2434
Project: Hibernate3
Type: Improvement
Components: core
Versions: 3.2.0.ga
Environment: All
Reporter: Don Smith
Priority: Minor
Date interval calculation is supported differently on different database platforms. Some allow direct arithmetic on columns, i.e. enddate - startdate. Some require functions, datediff(), timestampdiff(), etc. This causes cross-platform issues. For instance, an application I work on has to figure out the dialect that's in use (out of the four we currently support) and create the HQL string differently for each platform. This is undesirable, since we use Hibernate to enable platform neutrality; our installer asks which database the customer wants to deploy to, and sets the dialect. We'd like our codebase to be free of dialect-specific code.
I propose a standard solution for this, either direct date arithmetic, or a function defintion that is ported across dialects. Timestampdiff seems to be a fairly standard function, although DB2 has different syntax than MySQL and Derby. I've seen hints that timestampdiff is part of the ANSI SQL standard, but do not have access to the documents to determine if that is the case.
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
13 years