On Oct 5, 2010, at 12:31 AM, Mike Schrag wrote: >>> The order in which fetch specification bindings are in the >>> $fetchSpecification.allBindings and $fetchSpecification.distinctBindings >>> are not the same, and neither match the sequence that they are put in the >>> fetch specification in the model. >> Let me revise that. It appears that the allBindings sequence matches what's >> in the model. distinctBindings has a completely different, unpredictable >> (AFAICT) sequence. > it's alpha, but i just committed a new "qualifierOrderDistinctBindings" that > uses a linked hash map. i can't change getDistinctBindings because it would > ruin everyone's eogenerated classes and cause terrible problems.
Wow. That's awesome! I completely not being able to change the existing one, but since I'm writing my own template, I can use qualifierOrderDistinctBindings instead easily. My take is that as the bindings are added to the array/set/whatever if it is a duplicate binding name, it's skipped and you go on to the next. That way the sequence is preserved, just lacking any duplicate binding names. Thanks for the amazingly fast turn around Mike! Dave _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
