I cannot decide if this is something that EOF should or could deal with. On the one hand, it is clearly not correct. But it is clear what is happening, so EOF could just do the thing that makes it work. I have tables that look like this:
table 1 for eo1: pk name ---- -------- 1 thingA 2 thingB 3 thingC table 2 for eo2: pk fkey name ---- ------ -------- 1 1 other01 2 2 other02 3 2 other03 4 3 other04 5 4 other05 As you might guess there is a relationship eo1<-->>eo2. I am importing this data from an external source. There is obviously intended to be a "thingD" with a pk of 4. It might be an error that it does not yet exist. But, even if it is an error, it may or may not be fixed. This could be something I just have to deal with. Right now, one gets an exception, something like "no eo1 object found for pk 4". Would there be a sensible way for EOF to allow one to model this? Perhaps a "provisionally required" to-one join from eo2 to eo1? I am not sure. Or, I could just stomp on the bad fkey value on import. But EOF is smart, yes? It could do something smart. Any thoughts? - ray _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
