Like Pierre said, there was work done on what sounds like this exact
problem, but yeah, it appears the build server didn't push the new
build up ... Unfortunately, the machine that builds is internal and
it pushes it up to the server, but that machine is off right now
because there was some construction work being done on our server
room yesterday. It's supposed to be back up today, at which point
I'll kick off a new build.
Just to verify we're talking the same problem -- You have a prototype
that defines a column name, and you don't set the column name in the
attribute that uses it, and as a result, you end up with a column
named "" in the plist, right?
ms
On Aug 19, 2006, at 2:15 PM, André Koppany wrote:
> Hi,
>
> If a property with a prototype has not overwritten the column in
> the EOModeld, the column will be set to empty by the Entity Modeler.
> Also the model does not work anymore. If its overwritten then its
> not touched by the Entity Modeler.
>
> What can I do? I do not always overwrite the column from the
> EOPrototypes in the property.
>
> Best,
>
> André
>
This archive was generated by hypermail 2.0.0 : Sun Aug 20 2006 - 08:29:23 EDT