thanks - I am also confused about whether I have the "latest and greatest" install as the djangoproject lists .96 as the latest release and running
svn co http://code.djangoproject.com/svn/django/trunk/ in cmd.exe returns an error PROPFIND request failed on '/svn/django/trunk' the latest version listed is 0.96.1 so ?? but I do suspect my problem stems from the FK connection to the lookup table is only returning the ID number, not the text field: File "C:\Python25\lib\site-packages\django\db\models\fields \__init__.py" in get_choices 302. lst = [(getattr(x, self.rel.get_related_field().attname), str(x)) for x in rel_model._default_manager.complex_filter(self.rel.limit_choices_to)] I notice the reference to get_related_field() there. I could be wrong, that does make some sense. On Apr 13, 8:36 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Sun, Apr 13, 2008 at 9:28 PM, steve skelton <[EMAIL PROTECTED]> > wrote: > > > > > sorry I forgot to specify - am using 0.96.1 (django) and MySQL 5.0.51a > > (server) and 5.1.11 (client) and my local install is on Vista laptop > > with Apache and PHP also installed. > > The problem is your code below is using __unicode__ as the method to display > itself, and that was not added until after the 0.96 release. So when the > (0.96.1) admin goes to display your objects it doesn't find the str() method > it looks for to do that, so just displays the kind of object it is. > > So, you can either upgrade to an SVN checkout of Django, or change your > __unicode__ methods to str ones. If you stick with 0.96.1, you'll also need > to watch out for other things added since then, since it seems you are using > doc that is post-0.96.1, or switch to using the 0.96 docs. > > Karen > > On Apr 13, 8:24 pm, steve skelton <[EMAIL PROTECTED]> wrote: > > > > Trying to get admin on my system to load values based on related > > > tables on db. I have set the FK on the papers table to tie with the > > > PK of each look-up table and set models like so: > > > > class LuPaperContentEra(models.Model): > > > paper_content_era = models.CharField(blank=True, maxlength=150) > > > > def __unicode__(self): > > > return self.paper_content_era > > > > class Meta: > > > db_table='lu_paper_content_era' > > > > The main table, which should contain drop-downs for things like the > > > model/table above, has things like: > > > > class Paper(models.Model): > > > ... many fields defined > > > PaperContent_Era = models.ForeignKey(LuPaperContentEra) > > > ... more fields defined > > > > class Meta: > > > db_table='papers_admin' > > > > class Admin: > > > list_display=('id','FirstName','LastName','Institution') > > > search_fields=['LastName'] > > > > However, Admin displays the drop-down as > > > > LuPaperContactEra object, NOT the actual human-readable value list. > > > > I feel I am probably close to getting this to work but can't seem to > > > find the right direction in which to be "nudged". > > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
