Oh ok I see. The related_name is what you use to access the specific field in the template so it needs to be unique to the model field. When you use the ForeignKey field type it uses the primaryKey of the related database models automatically so you dont need to worry about actually telling it which field to use to relate to in a RDBMS sense.
On Tuesday, July 10, 2018 at 11:30:00 AM UTC-6, aditya wrote: > > I am using CBVs in model.py file and FBVs in views.py file. > As in image :- > > On Tue, Jul 10, 2018, 10:29 PM Alexander Joseph <alexander...@gmail.com > <javascript:>> wrote: > >> Also- this is assuming you're using CBVs, if youre just using FBVs its >> probably even easier on the view side, the model side would be the same >> >> On Tuesday, July 10, 2018 at 10:23:51 AM UTC-6, Alexander Joseph wrote: >>> >>> Good question - I'm looking for a similar solution myself. My >>> application is a purchase order app so that a purchase order has details >>> about the purchase order but also has an unspecified number of objects that >>> belong to it (purchase items). >>> The only way I can think this MIGHT work is making a model for each, >>> including a foreignKey to relate the puchase items back to the purchase >>> order, and possibly putting both in the same >>> CreateView/DetailView/UpdateView/etc. (if this is possible). I'll keep you >>> updated if I find any better solutions though >>> >>> >>> >>> >>> On Tuesday, July 10, 2018 at 9:26:55 AM UTC-6, aditya wrote: >>>> >>>> I have created a model Named Gallery and set upload path to media >>>> folder and in that folder I have 15 more folders with different images. >>>> Now I want to access each folder and images present inside it using >>>> database. >>>> My question is : >>>> Is it possible to create 15 model inside an model and if possible, then >>>> How to access them in my Html file? If not then what should I do to show >>>> them in my Html file ? >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users...@googlegroups.com <javascript:>. >> To post to this group, send email to django...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/10f8139f-ecd3-44d2-a7a6-9b6e7e2329ae%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/10f8139f-ecd3-44d2-a7a6-9b6e7e2329ae%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/17af2e69-1756-4156-99ce-20f01cf3aa67%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
