That's what I thought you might get. Here's the deal. The referential integrity between your REFCONTAINERS table and your CONTAINER table is totally blown. That rowcount confirms that there are 2571 containers for which there is *no* data. This is a problem because a call to getData() using any of those container id's would result in a NULL return. That NULL is what's causing the error we've been fighting.
Now that we've have the source of the error pinned down I'm confident to modify the container component to check that the getData() call actually returned a value. I'll patch the hole this AM my time and committ to CVS. So the question still remains. How did REFCONTAINERS get in it's current state? I don't know yet. I ran the same query on my REFCONTAINERS table here and I got back 19,000+ container id's that we're rogue :-( Obviously we have a problem in 2.2 or an earlier version of Farcry. The good news is that Geoff reworked most of the container code in 2.3 when he added Container Reflection (Which is sweet by the way) and I have not be able to recreate this scenario in the 2.3 release. You are safe to delete those references if you wish. I deleted mine without any problems. Although I highly recommend you backup your Db first. I'll patch that file right now. Have a look for it in CVS. ~tom On Tue, 01 Feb 2005 13:38:14 +0100, Silvio Resch <[EMAIL PROTECTED]> wrote: > rowcount is 2571 > > should I delete this references and trying again sending the object live? > > Whats your suspicion? What went wrong with the update? > > Silvio --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
