-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: SchemaExportTask : InnoDB : delimiter : Bad DROP SQL
PostPosted: Thu Jul 15, 2004 9:22 pm 
Beginner
Beginner

Joined: Thu May 06, 2004 4:06 pm
Posts: 25
What I can do:

1. Yes, I can create tables of type InnoDB by using:

Code:
delimiter=" type=InnoDB;"


2. Yes, you can create only DROP table SQL using:
Code:
drop="yes"


3. However, can you generate only CREATE table SQL? I ask this because if you add have:

Code:
delimiter=" type=InnoDB;"


the darn DROP SQL has " type=InnoDB;" appended to the end (obviously), so you can't drop the tables. If you remove the InnoDB type, then your DROPS will work, but your tables won't be InnoDB.

Any work around?


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jul 19, 2004 6:48 am 
Beginner
Beginner

Joined: Wed Jun 23, 2004 12:37 pm
Posts: 20
Hi

I don't think you can use the delimiter option in this way as once your mappings start to generate indexes and such like then a delimiter with ' type=innodb' will cause those bits of DDL to fail too.

We have a small stand alone script that alters each table to a type of innodb. We run this manually at present whenever we do a schemaexport.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.