Apple

On May 18, 2009, at 9:05 PM, email@hidden wrote:

Message: 7
Date: Mon, 18 May 2009 17:58:32 -0700
From: Chuck Hill <email@hidden>
Subject: Re: EOF Stumper (for me at least)
To: Lon Varscsak <email@hidden>
Cc: WebObjects-Dev Mailing List List <email@hidden>
Message-ID: <email@hidden">email@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes

Hi Lon,

This and your other problem cause me to suspect that you are violating
an EOF commandment somewhere. The "it works sometimes and not others"
is often indicative of a violation somewhere. Perhaps in this
process? I am also unsure that Propagate Primary Key is intended to
be used with a partially user controlled PK. I don't know that is
not, but it sounds suspicious.

I agree with Chuck, you are violating an EOF commandment; namely, when you use compound primary keys, you are on your own!

I'd been using Sybase since EOF was in beta, and compound primary keys were always a headache... I am not sure, but my guess is that it is a locking problem.

Now I assign both (or sometimes three or more) keys by hand; indeed, I have as part of my framework an specialised object (BAFolio) just to do that.

If you have the proper protocol (like all PKs have the same "key-structure"), such an object is not hard to implement and you can forget about that problem forever... HIH.

Suerte!

On May 18, 2009, at 2:27 PM, Lon Varscsak wrote:

The worst part of this is that without any code changes sometimes it
works and sometimes it fails (meaning sometimes orderLineNumber is
written to the adaptor op properly and therefore the database...but
not always).

I have changed "propagates primary keys" and propagated it myself by
overriding the setOrderNumber method on OrderHeader (and then
passing it down to OrderDetailSale) and the error goes away
completely. I'd prefer not to do this as it really does propagate
orderNumber which I want, it just seems to be occasionally trampling
orderLineNumber.