I think this deserves some elaboration...
We have a similar thing going in our desktop app. Generally our policy
is this: when a change happens in one component (the entity name in
this case), we auto-update the dependent component (the table name in
this case) only if the original value in the first component was equal
(camel case and similar mutations taken into account) to the value in
the dependent component. This policy handles Lachlan's described
situation in the way he wants, but handles other situations in a more
graceful way.
F
On Mar 10, 2009, at 20:04, Lachlan Deck (JIRA) wrote:
> Entity Modeler: editing the entity or column name should only
> populate the table name if the entity name was blank
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WOL-978
> URL: http://issues.objectstyle.org/jira/browse/WOL-978
> Project: WOProject/WOLips
> Issue Type: Bug
> Components: wolips
> Environment: WOLips 3.4.5693
> Reporter: Lachlan Deck
> Priority: Minor
>
>
> If editing an entity's name (i.e., where the entity name is not
> blank and the table name is blank) then the table name shouldn't
> auto-update to have the same value.
>
> The same applies for editing entity properties. The corresponding
> column name should remain blank if simply editing the name of the
> property.
This archive was generated by hypermail 2.0.0 : Wed Mar 11 2009 - 12:04:36 EDT