We've encountered a problem doing view.find() on ordered views where the "key" has more than one property. Metakit assumes that the "key" passed to find has the properties in the same order as they occur in the view to be searched. However, the Python interface to Metakit orders the properties based on the Python dictionary hashing algorithm. So it's pure luck whether or not the two orders match. I've logged this as a defect in the Metakit bug tracking system, along with a patch to give the correct behavior when using Metakit from Python. The behavior was observed on 2.4.9.3 and 2.4.9.4. I didn't check the CVS version. -- Cheers, Pat
_____________________________________________ Metakit mailing list - [email protected] http://www.equi4.com/mailman/listinfo/metakit
