Fair enough. BTW, I am in need of an auto-schema-bootstrap
functionality (maybe we do it with another DbAdapter decorator??) I
guess this feature can be done based on DbGenerator as well, as it is
most useful for the new databases. As e.g. blindly dropping columns in
an existing database may not be what the user wants.
Andrus
On Mar 9, 2009, at 12:34 PM, Tore Halset wrote:
> Hello.
>
> On Mar 9, 2009, at 10:27 , Andrus Adamchik wrote:
>
>>
>> On Mar 6, 2009, at 11:27 PM, Øyvind Harboe (JIRA) wrote:
>>
>>> Øyvind Harboe commented on CAY-1037:
>>> ------------------------------------
>>>
>>> I no longer use DbGenerator. Should DbGenerator be deprecated?
>>>
>>> The new MergerContext stuff is a million times better for my
>>> purposes: to add new tables/columns to the database if the model
>>> changed and the database didn't.
>>
>> I am very much in favor of doing that. In practical terms it means
>> switching Modeler / Ant / Maven to the MergerContext, and add
>> support for some missing databases. Wonder if we still need to
>> preserve "generate all" mode.
>
>
> I think the merger stuff (nice name) has some limitations related to
> the order the different tokens are performed preventing us from
> deprecating DbGenerator.
>
> Within a single entity, different tokens are ordered correctly, but
> there may be some problems with several dependent entities and
> relationships between them. Before this is fixed/improved, I still
> think we need DbGenerator. Sorry.
>
> Regards,
> - Tore.
This archive was generated by hypermail 2.0.0 : Thu Mar 12 2009 - 07:31:58 EDT