No, there's no conversion in the manual sense, but there's conversion
in the workflow sense. If you look at your version control system,
going from EOModeler to Entity Modeler makes it appear that every line
of your model files changed. This patch makes that a much smoother
process when you convert your workflow over to Entity Modeler.
ms
On Jan 28, 2008, at 9:40 AM, Ken Anderson wrote:
> You must be using an EntityModeler after the switch back to single
> line plist format.
>
> On Jan 28, 2008, at 9:28 AM, David Avendasora wrote:
>
>> Conversion? Was my model just too simple, or did I miss something,
>> because when I switched from EOModeler to Entity Modeler, I didn't
>> "convert" anything, it just worked.
>>
>> Dave
>>
>> On Jan 27, 2008, at 7:50 PM, Ken Anderson wrote:
>>
>>> Personally, while the diffing is incredibly useful, I was very
>>> pleased to see it using the single line format for now, since it
>>> was much less traumatic for my conversion...
>>>
>>> On Jan 27, 2008, at 12:18 PM, Mike Schrag wrote:
>>>
>>>>> And what was written as:
>>>>>
>>>>>> primaryKeyAttributes = (
>>>>>> eoid
>>>>>> );
>>>>>
>>>>> is now being written as:
>>>>>
>>>>>> primaryKeyAttributes = (eoid);
>>>>>
>>>>> I feel this is a change to the worse, as the previous format
>>>>> allowed for easy diffing. So, before committing all those
>>>>> changes, I thought I'd ask. :-)
>>>> This "new" format is actually now consistent with EOModeler's
>>>> format. This patch was from the iTunes folks and it basically
>>>> makes it much less traumatic to convert from EOModeler to Entity
>>>> Modeler because it won't completely change your model files when
>>>> you switch. I agree it makes it a little harder to diff, but
>>>> Eclipse should highlight subsections of the line that are
>>>> different, so you should still be able to see the diffs without
>>>> too much pain.
>>>>
>>>> ms
>>>>
>>>
>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Mon Jan 28 2008 - 10:26:19 EST