Code

Changes between Version 16 and Version 17 of DescriptorFields


Ignore:
Timestamp:
12/30/05 08:14:13 (9 years ago)
Author:
adrian
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DescriptorFields

    v16 v17  
    2828 
    2929 * ForeignKeys and other related fields would place another descriptor on the related class. 
    30    When accessed via the instance, this would return a  lazy collection object. It will act like a set  
     30   When accessed via the instance, this would return a lazy collection object. It will act like a set  
    3131   (an ordered one if there is an ordering involved).   
    3232    
    3333   This would also support other methods in favour of the get_related_list things.  
    3434    
    35    Other end of ForeignKey relationship: 
     35   Other end of ForeignKey! relationship: 
    3636    
    3737   {{{ 
     
    116116= Query Syntax = 
    117117 
    118 In further discussions about this idea, it seemed consistent that both the manager ( Person.objects ) and relationship end points, ( reporter.articles ) would act as lazy sets of instances (base class QuerySet?) , with these 'refinement' methods on them ( filter, order_by, etc).  
     118In further discussions about this idea, it seemed consistent that both the manager ( Person.objects ) and relationship end points, ({{{reporter.articles}}}) would act as lazy sets of instances (base class QuerySet?) , with these 'refinement' methods on them (filter, order_by, etc).  
    119119 
    120120eg  
     
    132132{{{ar_list = Person.objects.get_list(complex=Q(name_startswith="R")|Q(name_startswith="A") ) }}} 
    133133goes to (idiosyncratically) 
    134 {{{people = Person.objects 
    135    ar_set = people.filter(name_startswith="R") | people.filter(name_startswith="A") 
     134 
     135{{{ 
     136people = Person.objects 
     137ar_set = people.filter(name_startswith="R") | people.filter(name_startswith="A") 
    136138}}} 
    137139