Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Dali » DDL Generation observations
DDL Generation observations [message #584856] Tue, 25 April 2006 20:25
Kevin Sutter is currently offline Kevin SutterFriend
Messages: 106
Registered: July 2009
Senior Member
First off, now that I finally got DDL generation to actually kick off and
process, I was quite impressed with the result. I had read through the
gotchas already discovered, so I was ready for those. But, overall, it
generated the necessary ddl that matched my annotated source. Thanks.

But, of course, I have a few observations...

o Are Discriminator columns supported yet? I had a Discriminator Column
defined for one of my tables, and I didn't see that get generated in my
DDL. I modified my script before running it.

o Should Embedded classes work yet? One of my Entities referenced an
Embeddable class for a couple of its properties. But, the generated ddl
for this table didn't include these additional fields. They were
TIMESTAMP fields, if that makes any difference.

o The statement terminator doesn't seem to be working quite right. By
default, it used "GO" as the statement terminator. But, the generated
script didn't have the special statement to indicate the terminator:

-- <ScriptOptions statementTerminator="GO">

o Related to this, why wouldn't the semi-colon (;) be the default value
for the statement terminator? The word "GO" seems too common since it
found that in several locations of my generated DDL and, of course, died
all over the place when I first tried to run it... :-)

o The DDL generation seems to combine table definitions from several
files. (Again, this may be due to only having the option of running this
tool at the Project level.) Because I was experimenting with generating
Entities at the same time, I had multiple Entity class files that were
referencing the same table names. The DDL generator just combined all of
these definitions into a single table definition. This doesn't seem
right. I would have preferred a warning or an error that it couldn't
generate the ddl due to conflicting annotations.

That's it. Once I worked around these items, I was able to generate ddl
that actually dropped my old tables and re-created new ones based on the

Previous Topic:Refreshing of Persistence Properties
Next Topic:TableGenerator for DDL generation
Goto Forum:

Current Time: Sat Jun 23 06:56:23 GMT 2018

Powered by FUDForum. Page generated in 0.01905 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top