Changes between Initial Version and Version 1 of Ticket #24048, comment 2


Ignore:
Timestamp:
Dec 30, 2014, 4:40:27 AM (10 years ago)
Author:
Will Earp

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #24048, comment 2

    initial v1  
    11It looks as if the `only()`'s "problem" is caused by `add_immediate_loading()`. Taking the example above, `field_names.difference(existing)` in the method evaluates to `set(["value", "name"]).difference(set["name"])`.
    22
    3 Cut a story short, `self.deferred_loading` is `set(["value"]), False` when it should be `set(["name", "value"]), False`.  
     3Cut a story short, `self.deferred_loading` is `set(["value"]), False` when it should be `set(["name", "value"]), False`.
    44
    5 If the problem is to be fixed, is it best addressed in `add_immediate_loading()` or `only()`?
     5`only()`'s documentations suggests it will override `defer()`. However, `add_immediate_loading()` is to "respect existing referrals", according to its comments.
     6
     7If the problem is to be fixed, is it best addressed in `add_immediate_loading()` or `only()`? I'm guessing it will be to change `only()` as it contradicts the docs?
Back to Top