Re: Case sensitivity problem with primary keys in EOEditingContext.faultForRawRow

On 31-Jul-06, at 5:10 AM, Marc Gumpinger wrote:
> However, this dict worked:
> {ID=123, id=123, SOME_COLUMN='Hello', ...}
>
> And that's what was kind of strange to me, because a raw row dict  
> with mixed column names and attribute names for pks works.

I think that it's not so strange...

When EOF is constructing a fault, it asks for the PK values based on  
the primary key name(s) specified by the EOEntity.
When EOF is populating an EO, it will ask for each attribute value  
using the associated key in the EOEntity.

IIRC, I've fetched lots of raw rows with lots more elements then the  
EOEntity ever knew about.
I've never had the impression that the EOEntity was enumerating all  
the keys.
It always seemed to me that it was only asking for specific key-value  
pairs.
Could be that I've been lucky in more then 10 years of using  
EOF! ;-)  YMMV.

Good luck!
Mark
__
Mark Ritchie
Diamond Lake Consulting Inc.
Toronto Ontario Canada.