On Thu, Aug 21, 2014 at 2:21 AM, Shai Berger <s...@platonix.com> wrote:

> On Wednesday 20 August 2014 10:29:49 Anssi Kääriäinen wrote:
> > On Wednesday, August 20, 2014 11:19:33 AM UTC+3, Russell Keith-Magee
> wrote:
> > >
> > > This yields the following formal API for _meta:
> > >  * get_fields(data, many_to_many, related, include_hidden,
> > >                     include_parents)
> > >
> > >  * @property data_fields
> > >
> > >  * @property many_to_many_fields
> > >
> > >  * @property related_objects
> > >  (=> get_fields(data=False, many_to_many=False, related=True,
> > >                          include_hidden=False, include_parents=True)
> > >
> > +1 if we also consider defining and documenting an useful set of field
> flags.
>
> +1 Anssi.
>
> >
> > I wonder if a better name for the related category exists. My first
> > instinct is that foreign key fields should match the related flag. Could
> it
> > be made cleaner that these are relations defined on remote model? Maybe
> > just remote_relations could work?
> >
>
> Since this is a bikeshedding thread, I'll say that the name
> "related_objects"
> makes me itch a little as well -- mostly, because each of the objects
> returned
> by the property is not a related-object, but rather a manager of related-
> objects.
>
> I was considering "related_managers", but that is sort-of mixing the "what"
> with the "how", and also thinking about the possible Array(FK) fields, I
> prefer
> "related_collections".
>

Hi Shai,

I'll accept that there are probably better names for this - but as I said
in my response to Anssi, until we actually know what "it" is, it will be
more productive to focus on the categories and flags that need to exist.
Once we've got those categories nailed down, the names will hopefully be
more obvious (or, at least, more obviously a bikeshed).

Russ %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJxq84-LdY15%2Bfp4afOo-QT5aHODoWGsdN28v%2B0Qs2gPycqpUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to