Customization of CREATE TABLE with storage clause etc.

Description

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()

depends on

Activity

Show:

Christian Beikov April 4, 2024 at 3:18 PM

With JPA 3.2 and ORM 7.0, the @Table annotation will get an options member, so this will be solved then. Also see https://github.com/hibernate/hibernate-orm/discussions/5607

Steve Ebersole May 3, 2011 at 6:43 PM

Depends on new metamodel code ()

Steve Ebersole March 4, 2011 at 11:58 PM

needs to be part of the metamodel rework which is scheduled for the second 2 alphas

StefanI October 8, 2010 at 10:37 AM

Not only appendix on CREATE INDEX is useful. Other useful customization for me would be the option to create functional indices.

Max Rydahl Andersen January 23, 2006 at 6:41 PM

no, this should not be done by velocity by default since velocity sucks for this kinda thing.

but if we want the base tools to be distributed with the core then the velocity dependencies would be needed. But is that a great issue ?

Out of Date

Details

Assignee

Reporter

Components

Priority

Created October 24, 2005 at 1:37 PM
Updated April 4, 2024 at 3:18 PM
Resolved April 4, 2024 at 3:18 PM