Re: dynamically adding derived EOAttribute

> I solved this. In order for the definition to 'stick', you need to 
> create the EOAttribute with the constructor that takes an EOEntity. It 
> has to already know it's entity to take a definition.
> This works:
>
>             EOAttribute countAtt = new EOAttribute(new 
> NSMutableDictionary(), entity);
>             countAtt.setName("_derivedCount");
>             countAtt.setColumnName("");
>             countAtt.setDefinition("count(*)");
>             countAtt.setExternalType("int");
>             countAtt.setValueClassName("NSNumber");
>             countAtt.setValueType("i");
>
> Questions:
>
> 1) Is this a bug? Either in documentation or in effect? Should I file 
> it?

I think EOAttribute is trying to parse the definition you pass it, and 
it needs to have a context (the owning EOEntity) to do this. So I would 
say the bug is that setDefinition() isn't raising an exception telling 
us about the missing EOEntity instead of silently ignoring the argument.

Christian