> Fair enough... it was checked as an attribute...
> I don't use them so I unchecked and that fixed that.... BUT, why
> would it make an error... I guess Mike is a real stickler.
I agree with Paul that 1) calling it rowid is a bad idea because that
is a reserved word in some databases and 2) presumably it was a class
attribute and I think that's what you're saying when you say you
"unchecked it" (that you made it a non-class attribute). However, I
just setup a test case with a class attribute PK and it didn't
generate the error you're seeing. Can you strip out your model to
JUST have that one entity that had the rowid error and send it to me?
Or actually, just send me the ProjectDocument.plist from inside your
model (with everything set back to what it was when you got that
error?).
Also, I committed a fix for the entity.name issue as well, so the next
build will have that part fixed up.
> NOW about this $relationship thing...
>
> Why isn't it picking up the relationships?
What exactly are the details of the
portfolioMetricListPortfolioProjects relationship? Is this a
flattened relationship by any chance? Can you send a screenshot of
the Basic properties tab for that relationship so I can see exactly
how it's setup?
ms
This archive was generated by hypermail 2.0.0 : Tue Dec 04 2007 - 07:17:38 EST