I don't like the name "MIGRATION" either. I just reuse it:
http://api.rubyonrails.org/classes/ActiveRecord/Migration.html
On 30.06.2011, at 15:45, Werner Keil wrote:
> Hi,
>
> Does sound like a good idea, assuming most databases or implementations can easily figure out a delta to alter tables.
>
> I hope for more suggestions for the strategy name, as "MIGRATION" sounds a bit like moving the DB to another server or similar. Since existing names are using the pragmatic approach based on SQL ("CREATE TABLE..." or "DROP TABLE...") what would be wrong with "ALTER" or "MODIFY" instead of "MIGRATION" ?
>
> Even if the latter seemed best, it should be "MIGRATE" following "CREATE" (not "CREATION" ;-)
>
> Werner
>
>
> -------- Original-Nachricht --------
>> Datum: Thu, 30 Jun 2011 11:50:57 +0200
>> Von: Adam Bien <abien_at_adam-bien.com>
>> An: jsr338-experts_at_jpa-spec.java.net
>> Betreff: [jsr338-experts] Standardization of additional persistence.xml properties
>
>> Hi all,
>>
>> proposal for standardization of table generation strategy:
>>
>> <property name="javax.persistence.table-generation-strategy"
>> value="CREATE | DROP-AND-CREATE | MIGRATION | NONE /> Default should be NONE.
>>
>> I would like to propose MIGRATION as an optional parameter. In this case
>> the JPA provider is expected to alter the tables, instead of drop and
>> recreate them,
>>
>> any thoughts?
>>
>> thanks!,
>>
>> adam
>>
>>
>>
>>
>
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Independent Consultant, Speaker, Java Champion
Weblog: blog.adam-bien.com
press: press.adam-bien.com
eMail: abien_at_adam-bien.com
twitter: twitter.com/AdamBien
Mobile: 0049(0)170 280 3144
Author of:
"Real World Java EE Night Hacks", "Real World Java EE Patterns--Rethinking Best Practices"