Chris Withers wrote:
i'm no expert but deeply nested data structures in a single object are
rife with possibilities for conflict errors. if data might be changing
concurrently in the structures or frequently changing you would be
better off to switch the structure to nested persistent objects.
> No, for once it has nothing to do with the catalog. ;-)
> This is a python product of ours that stores lots of data in somewhat
> nested, persistent dictionaries. How can this be improved so this
> doesn't happen?
> > I know your next questions are going to be "why?" and "how do I fix it?" and
> > "why don't you fix it?".
> While I'd love it if you'd fix our code for free, it's probably beyond
> the OSS remit ;-) Any clues about how to make our code 'less bad' would
> be cool...
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -