Right now it rewrites the whole thing ... It's certainly "doable" to
not have to do this, but for the first pass it makes me a little
nervous. If it misses marking an entity dirty, it would just toss
data, which would really suck. The EOModel file format really
doesn't help us here either, because it's crazy unnormalized. There
are cross-file references in multiple places, so for instance even if
you didn't add a new entity, you might have to rewrite index.eomodeld
just because it has the class name of its entities in it.
If you turn on contents comparison vs just timestamp comparison (or
whatever it's technically called), you should find that the .eomodeld
files becomes diff-stable after the first save (i.e. if you open an
old model, it will write it back out sorted, and successive saves
will maintain that sort order).
But consider the requests duly noted.
ms
On Jul 25, 2006, at 2:23 PM, Watkins, Garry wrote:
> Do you re-write all of the entities when you save? If you do, I would
> like to put in a request that it only write files (entities, fetch
> specs) after they have been changed. That way subversion doesn't
> tell me
> that all 200+ files of my model have changed. One more thing, it is
> writing an initial blank line, which causes subversion to pick up
> differences.
>
>
> Thanks
> Garry
>
>
> -----Original Message-----
> From: Mike Schrag [mailto:mschra..dimension.com]
> Sent: Tuesday, July 25, 2006 1:28 PM
> To: woproject-de..bjectstyle.org
> Subject: Re: EOModeler Attributes
>
> They should all be editable, but via the attribute "inspector panel"
> right now (if you're in the Entity Modeler perspective, you will have
> the Properties view in the lower right. If you select an
> attribute, the
> editor will appear there) ... The list of columns in the table is not
> configurable right now and probably won't be before WWDC unless
> someone
> else wants to take this on (it's a bit of a tricky problem to do it
> live). I've intentionally selected the columns in the attribute
> view at
> the moment to encourage the use of prototypes, which is why these
> other
> fields don't appear as columns by default.
>
> ms
>
> On Jul 25, 2006, at 1:14 PM, Jake Fisher wrote:
>
>> Mike,
>>
>> Can you add the following as either columns or editable attributes
>> in the new integrated EOModeler?. We make use of them fairly often in
>> our models.
>>
>> Missing EOAttribute attributes:
>>
>> value Class = 'valueClassName'
>> precision = 'precision'
>> scale = 'scale'
>> as an example:
>> {
>> allowsNull = Y;
>> columnName = ID_AMOUNT;
>> externalType = DECIMAL;
>> name = amount;
>> precision = 7;
>> scale = 2;
>> valueClassName = NSDecimalNumber;
>> }
>>
>>
>> Thanks,
>> ~jake
>
>
>
>
>
> Confidential & Privileged
>
> Unless otherwise indicated or obvious from its nature, the
> information contained in this communication is attorney-client
> privileged and confidential information/work product. This
> communication is intended for the use of the individual or entity
> named above. If the reader of this communication is not the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error or
> are not sure whether it is privileged, please immediately notify us
> by return e-mail and destroy any copies--electronic, paper or
> otherwise--which you may have of this communication.
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Jul 25 2006 - 14:52:27 EDT