Re: [gemini-dev] Gemini JPA - EntityManager question

[Tom Ware <tom.ware@xxxxxxxxxx>]

The "beautiful way" is likely somewhat more involved than specifying a property. 
 It involves disabling the ddl creation property and using the internal 
EclipseLink table creation constructs. (i.e. instead of setting the propery, 
mimicking what happens when the property is set in your own code after you have 
created you entity manager).

-Tom

On 14/10/2011 8:31 AM, András Liter wrote:
> Hello Tom,
>
> thanks for the answer! I figured out as well that without drop it's ok to create
> tables and if they are already created, they wont get hurt but I thought there
> is a "beautiful" way, without exceptions.
>
> Thanks, bye!
> András
>
> On Fri, Oct 14, 2011 at 1:57 PM, Tom Ware <tom.ware@xxxxxxxxxx
> <mailto:tom.ware@xxxxxxxxxx>> wrote:
>
>     For most databases, just using the create table options solves this issue
>     (rather than drop and create).  EclipseLink not fail when it gets exceptions
>     from table creation, it will simply move on and try to create the rest of
>     the tables.
>
>     -Tom
>
>
>     On 14/10/2011 5:46 AM, András Liter wrote:
>
>         ogger.debug("Database tables are already created.");
>
>     _________________________________________________
>     gemini-dev mailing list
>     gemini-dev@xxxxxxxxxxx <mailto:gemini-dev@xxxxxxxxxxx>
>     https://dev.eclipse.org/__mailman/listinfo/gemini-dev
>     <https://dev.eclipse.org/mailman/listinfo/gemini-dev>
>
>
>
>
> _______________________________________________
> gemini-dev mailing list
> gemini-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gemini-dev