on 5/31/02 8:19 AM, "Scott Finnerty" <[EMAIL PROTECTED]> wrote:
> The bug #3496 is marked resolved, but I'm not sure it is. The attached > patch makes sure that when the object is populated by the peer that keys > are set to null and not to a key containing a null value. Particularly > in the case of foreign keys, it is plausible to have a null value. This > fix makes checks for null work with key fields - as occurs in the gets > for associated objects. Thus this fix seems to address the problem > described in bug #3496. > > Scott Finnerty Done. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
