In addition to my prior post, I have another problem with DDL generation.
When I use drop-and-create-tables I get an exception when the tables are not
available at drop time.
When I use create-tables I get an exception when the tables are already there.
Why is drop-and-create-tables not just ignoring it when there are no tables to
drop. Thats fine...it can continue with the creation. I dont want to change my
persistence.xml every time I run my testcases or drop tables in the database
Furthermore I get exception regarding a table called SEQUENCE (sometimes telling
me that it is missing, or that it is already there).
I guess I am doing something wrong in my top-down-approach. I know that in real
scenarios usually bottom-up is used, but right now I am just playing around how
to organize my object and how to map it...and currently EclipseLink seems to
have some problems with that.
Can somebody explain what I might do wrong or what I have to be aware of.