Hi Aaron,
On Aug 6, 2008, at 8:24 AM, [EMAIL PROTECTED] wrote:
Thank you Chuck and Mike for your thoughts on this rather scary issue.
I will try to free up some cycles to build a "reduction" or "test
case", but probably not today. Assuming I could make a reproducible
and simple reduction
Thank you Chuck and Mike for your thoughts on this rather scary issue.
I will try to free up some cycles to build a "reduction" or "test case",
but probably not today. Assuming I could make a reproducible and simple
reduction, anyone know what Database Apple would most likely like to see?
I'm a
On Aug 5, 2008, at 6:50 AM, [EMAIL PROTECTED] wrote:
Hi Everyone,
Sorry to rebump this question but I really want to know what our
current collective consensus is on this topic.
The following thread from 2006 appears to me, at least, to be our
most current and complete understanding of
On Aug 4, 2008, at 8:21 AM, [EMAIL PROTECTED] wrote:
Hello WOrriors,
What, me worry?
We're using WO 5.3.x (not 5.4.x)
I've run into a pickle where if I do an ec.deleteObject() and then
call ec.saveChanges() I find that this fails during a
"validateFor*Save*". Curious, indeed, because
Has anyone else used Lenny's extension of EOEditingContext to
positive effect? Personally, I'm testing it right now and it seems
to be working but at one point yesterday it seemed that it ignored
my request to delete the object but didn't throw an error either.
I believe Project Wonder's ERXE
Hi Everyone,
Sorry to rebump this question but I really want to know what our current
collective consensus is on this topic.
The following thread from 2006 appears to me, at least, to be our most
current and complete understanding of this issue:
http://lists.apple.com/archives/Webobjects-dev/2
Hi Kieran,
I tried this solution just now but I couldn't get it to work for me. I
even trashed my entire build directory and tried it to no avail. I still
see the same behavior namely:
1) deleted EO causes "validateForSave" exception in ec.saveChanges()
The validation exception is still the sa
Er ..
On Aug 4, 2008, at 1:39 PM, [EMAIL PROTECTED] wrote:
Hi Kieran,
That is an interesting thought. To mark the relationship as
"Mandatory" but yet leave the foreign key itself as optional
("allows null"). You would think the two would need to back each
other up though, and to a c
Hi Kieran,
That is an interesting thought. To mark the relationship as "Mandatory"
but yet leave the foreign key itself as optional ("allows null"). You
would think the two would need to back each other up though, and to a
casual developer passing by and perusing your model he might think you
If I have understood you correctly, then this is how I prevent this
error for mandatory relationships:
1) Make the relationship foreigh key attribute "AllowNull" in the
eomodel
2) Make them NOT NULL in the database (therby ensuring a record with
NULL foreign key can never be saved or update
Hello WOrriors,
We're using WO 5.3.x (not 5.4.x)
I've run into a pickle where if I do an ec.deleteObject() and then call
ec.saveChanges() I find that this fails during a "validateFor*Save*".
Curious, indeed, because it should only call "validateFor*Delete*". When
asking the EC to delete the Ob
11 matches
Mail list logo
