Nate Lowrie wrote:
> On Tue, Mar 11, 2008 at 11:42 AM, Paul M¢Nett <[EMAIL PROTECTED]> wrote:
>> Hey Ed,
>>
>> Revision 3925[1] seems to break my application. Some or all child bizobj
>> records either aren't getting saved, or not linked properly to the
>> parent on a parent.new(). I'll do more testing to try to figure out
>> exactly what is/is not happening but I'm not sure when I'll have the
>> time to do this. All I can say for certain right now is that revision
>> 3924 seems to behave correctly, and revisions 3925 up to HEAD seem to
>> behave incorrectly.
>>
>> [1]: http://trac.dabodev.com/changeset/3925
>
> I had the same problem with rev 3949 a couple of nights ago. I had a
> bizobj that was the child of the primary bizobj. That bizobj had two
> children. The bizobj wasn't linking properly to the two children on
> parent.new(). Neither of the 2 children used the primary key of the
> parent bizobj. I went in a different route with the code, but I
> thought I would chime in with this.
My situation has:
-bizOrders
-bizOpenings
-bizSubopenings
-bizStiles
-bizRails
And the problem appears to be that when I call bizOpenings.new(), the
bizSubopenings record is added but the bizStiles and bizRails records
are not. There is overridden code in I need to do testing to confirm it,
but our problems sound like they could be related.
Code in bizOpenings.afterNew() is responsible for adding the subopening
record by calling code in bizSubopenings, which in turn does some
bizStiles.new() and bizRails.new() call. So, all the new records get
added manually in the bizOpenings.afterNew() method.
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
