Caching instances via related_name seems to only work if primary_key=True

[blite]

this should at very least be in the documentation if you don't plan on fixing it soon

edited:
actually that doesn't seem right at all, the issue i'm seeing is when the primary key of the related object is out of sync with the parent object

[lamby]

primary key of the related object is out of sync with the parent object

As in, if you change the primary key of the child object?

[blite]

no as in say you have a onetoone relationship, well cache toolbox assumes that the primary key of the child object is equal to the parent object, this doesn't have to be the case at all.

[blite]

class Something(models.Model):
name = models.CharField(max_length=45, blank=True, default="")

class AnotherThing(models.Model):
something = models.OneToOneField(Something)
setting = models.CharField(max_length=45, blank=True, default="")

so to properly lookup the OneToOne relationship you'd do it via the automatic database column "something_id", however cache-toolbox does it via the pk or "id" field. This is great until for whatever reason a AnotherThing object fails to be initialized at the same time as a Something object causing the autoincrement to increase but no object to exist.