Try changing __unicode__ to __str__. The unicode merge was after .96 and
therefore it isn't looking for __unicode__ to define the name of the field.
Hope that helps,
Michael
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.
>
> 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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---
