django

Commit Graph

Author	SHA1	Message	Date
Michal Petrucha	c339a5a6f7	Refs #16508 -- Renamed the current "virtual" fields to "private". The only reason why GenericForeignKey and GenericRelation are stored separately inside _meta is that they need to be cloned for every model subclass, but that's not true for any other virtual field. Actually, it's only true for GenericRelation.	2016-04-13 10:10:53 -04:00
Aymeric Augustin	e542e81b39	Renamed descriptor classes for related objects. The old names were downright confusing. Some seemed to mean the opposite of what the class actually did. The new names follow a consistent nomenclature: (Forward\|Reverse)(ManyToOne\|OneToOne\|ManyToMany)Descriptor. I mentioned combinations that do not exist in the docstring in order to help people who would search for them in the code base.	2015-09-21 22:20:42 +02:00
Alex Hill	98bcdfa8bd	Fixed #25064 -- Allowed empty join columns.	2015-08-15 07:26:44 -04:00

Author

SHA1

Message

Date

Michal Petrucha

c339a5a6f7

Refs #16508 -- Renamed the current "virtual" fields to "private".

The only reason why GenericForeignKey and GenericRelation are stored
separately inside _meta is that they need to be cloned for every model
subclass, but that's not true for any other virtual field. Actually,
it's only true for GenericRelation.

2016-04-13 10:10:53 -04:00

Aymeric Augustin

e542e81b39

Renamed descriptor classes for related objects.

The old names were downright confusing. Some seemed to mean the opposite
of what the class actually did.

The new names follow a consistent nomenclature:

    (Forward|Reverse)(ManyToOne|OneToOne|ManyToMany)Descriptor.

I mentioned combinations that do not exist in the docstring in order to
help people who would search for them in the code base.

2015-09-21 22:20:42 +02:00

Alex Hill

98bcdfa8bd

Fixed #25064 -- Allowed empty join columns.

2015-08-15 07:26:44 -04:00

3 Commits