Re: Using a text formatter on a WOBuilder WOString object
Re: Using a text formatter on a WOBuilder WOString object
- Subject: Re: Using a text formatter on a WOBuilder WOString object
- From: Nat Fast <email@hidden>
- Date: Wed, 18 Jun 2003 11:03:34 -0700
Hi Chuck,
To clarify the solution that you suggested was to modify the accessor
method to deal with the to-many relationship as a to-one, so that it
returned an object rather than a NSArray. This I did and it
automatically fixed the relationship chain returning the string object
from the value field rather than the coerced NSArray to string. It
corrected many other problems that were yet to occur.
I was more commenting on the source of the problem that led to me
having to use a to-many in the middle of my relationship chain in the
first place. I can confirm that the bug, inserting a record to a
related database attached to a to-one relationship losing synch when
the record is inserted, still exists in 5.1 as my model and
implementation attests to. I was pulling what little hair I had out as
I tried to figure out why my session lost the pointer to the parent
record on the execution of the form action. As soon as I modified the
database to a to-many, the operation worked and the parent relationship
was not lost. What I did wrong is that I modified my WOComponent code
to deal with the NSArray issues, not the accessors in the table class
generated by EOModeler. Once I modified the table class all problems
went away, as you suggested in your post.
Thank you for pointing me in the right direction,
On Wednesday, June 18, 2003, at 08:49 AM, Chuck Hill wrote:
At 07:01 PM 17/06/2003 -0700, Nat Fast wrote:
This did the trick!
Thank you very much. This is obviously a legacy of the whole
one-to-one
relation issue that has been documented on this board extensively,
where if you edit and recall a WOComponent the database loses synch
with the session and you lose your data.
Which problem? I don't recall anything based on your description.
Chuck
That was the first problem I
had and had to solve it with the one-to-many, single item object.
I recall that as being a workaround for a bug in the Java
implementation in
4.5.
Cheers,
Chuck
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.