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

On Jul 29, 2006, at 9:19 AM, Marc Gumpinger wrote:

> Now the problem - at least in my case - is, that the dictionary's  
> keys are all upper case (here "ID") since that's what the database  
> returned. However, the primary key's name in the eomodel is all  
> lower case (here "id"). For this simple reason, the entire  
> faultForRawRow doesn't work.
>
> Is there an official solution to this problem?
> I mean, it was no effort, to adopt the dictionary correspondingly  
> so that the keys also match in case sensitivity. However, due to  
> EOFs maturity I'm sure that I either made a mistake or oversaw  
> something.

I would not call case-sensitivity a problem.  I would call that a  
feature.  If you've ever been bitten the other way, you'll know what  
I mean.


sacha


--
Sacha Michel Mallais             Senior Developer / President
Global Village Consulting Inc.   http://www.global-village.net/
PGP Key ID: 7D757B65             AIM: smallais
So it doesn't mess up the flow of reading.
 > How come?
 > > I prefer to reply inline.
 > > > What do you do instead?
 > > > > No.
 > > > > > Do you like top-posting?