problem with umlaut in foreign key table

g Sore without the foreign key to Rorg works fine as well) did I miss something in the model documentation or may this be a bug in django? thanks for any helpful hints goobee --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Goo

ModelForm and ForeignKeys

hi there I'm in dire need of a good idea. django drives me crazy with its foreignkey-resolver. class person(models.Model): name ... firstname class participant(models.Model): group .. person(foreignkey(person)) funk ... I want to show 'participant

Re: ModelForm and ForeignKeys

thanks Léon but I need name and firstname from the referenced table 'person', but only from ONE person; the person I read from 'participant'. goobee --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google G

Re: ModelForm and ForeignKeys

ist referenced by the selected CharacterHome. In addition the user should only get non-editable fields on the html- page regards goobee On 24 Aug., 12:11, Léon Dignòn wrote: > Basically you have to link them with a foreign key. I hope this fits > your needs with the legacy table

Re: ModelForm and ForeignKeys

ist referenced by the selected CharacterHome. In addition the user should only get non-editable fields on the html- page regards goobee On 24 Aug., 12:11, Léon Dignòn wrote: > Basically you have to link them with a foreign key. I hope this fits > your needs with the legacy table

changing model manager

y_key=True) . --> no single id_... as PK Would it be a big deal to change django to be able to handle these database models? if no, any hints where to find the 'switch' ;-) thanks goobee --~--~-~--~~~---~--~~ You received this message because

Re: changing model manager

great to hear, thanks Karen I will check the ticket and hope goobee --~--~-~--~~~---~--~~ 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@googlegro