I am moving an application (finally) from 0.96 to 1.1.1 and I'm
running into an issue I haven't been able to resolve.
To make things simple, here are the two relevant models:
class Station(models.Model):
station_index = models.AutoField(primary_key=True)
name = models.CharField()
...
class StationRelation(models.Model):
station = models.ForeignKey(Station, db_column='station_index')
objects = CustomStationRelationManager()
...
class CustomStationRelationManager()
def get_nearest(zipcode):
....
In the custom manager code, I set the primary key in a new Station
object so it (in 0.96) would only get loaded if it was referenced:
def get_nearest(zipcode):
... custom SQL that returns a station_index, etc. ...
s = Station(station_index=row[0]) # row[0] is select
station_index, from the sql result
rel = self.model(station=s)
return rel
In 0.96, if code that received the StationRelation object accessed,
say the name field, the Django ORM would do sql to fully populate the
station object.
print rel.station.name
COLUMBUS
However, in 1.1.1, the same code does not do that:
print rel.station.name
None
In either 0.96 or 1.1.1 if I use the standard manager, lazy
instantiation works as normal:
rel = StationRelation.objects.get(station__station_index=1846) # Note,
no select_related
...
print rel.station.name # the SQL to get station's properties happens
here, not before
COLUMBUS
So, the question is, what do I have to do in 1.1.1 that I didn't in
0.96 in order to properly lazy populate a manually created model
object, beyond just the primary key?
Thanks for your help!
Eric
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
