[hibernate-dev] SchemaExport adds engine=MyISAM to all create table statements.
Vlad Mihalcea
mihalcea.vlad at gmail.com
Sun Apr 2 09:31:25 EDT 2017
Hi Petar,
It must be a bug. I changed the way storage info is resolved, and it might
be that the Schema Exporter does not take that into consideration.
Please open an issue and provide a replicating tests case.
Thanks,
Vlad
On Sun, Apr 2, 2017 at 3:59 PM, Petar Tahchiev <paranoiabla at gmail.com>
wrote:
> Hey guys,
>
> I've been using Hibernate's SchemaExport tool (5.1.x) for a long time it
> has always created an sql script with create-table statements like this:
>
> create table abstract_modifiable_entity (
> id bigint not null,
> code varchar(255) not null,
> created_by varchar(255),
> created_date datetime,
> last_modified_by varchar(255),
> last_modified_date datetime,
> primary key (id)
> );
>
> However now that I try to upgrade to the latest 5.2.x I see a change - it
> adds engine=MyISAM to the end of every create-table statement:
>
> create table abstract_modifiable_entity (
> id bigint not null,
> code varchar(255) not null,
> created_by varchar(255),
> created_date datetime,
> last_modified_by varchar(255),
> last_modified_date datetime,
> primary key (id)
> ) engine=MyISAM;
>
>
> Is this intentional or a bug? I tried to find something in the changelog
> but I couldn't. I even tried to declare the InnoDB dialect:
>
> spring.jpa.database-platform=org.hibernate.dialect.MySQL57InnoDBDialect
>
> but it still adds the MyISAM engine.
>
> Is there any API to set the required engine?
>
> Thank you.
> --
> Regards, Petar!
> Karlovo, Bulgaria.
> ---
> Public PGP Key at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
More information about the hibernate-dev
mailing list