Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Becoming an Enterprise Django Developer

You're reading from   Becoming an Enterprise Django Developer Discover best practices, tooling, and solutions for writing and organizing Django applications in production

Arrow left icon
Product type Paperback
Published in Jun 2022
Publisher Packt
ISBN-13 9781801073639
Length 526 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Mike Dinder Mike Dinder
Author Profile Icon Mike Dinder
Mike Dinder
Michael Dinder Michael Dinder
Author Profile Icon Michael Dinder
Michael Dinder
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1 – Starting a Project
2. Chapter 1: Undertaking a Colossal Project FREE CHAPTER 3. Chapter 2: Project Configuration 4. Chapter 3: Models, Relations, and Inheritance 5. Part 2 – Django Components
6. Chapter 4: URLs, Views, and Templates 7. Chapter 5: Django Forms 8. Chapter 6: Exploring the Django Admin Site 9. Chapter 7: Working with Messages, Email Notifications, and PDF Reports 10. Part 3 – Advanced Django Components
11. Chapter 8: Working with the Django REST Framework 12. Chapter 9: Django Testing 13. Chapter 10: Database Management 14. Other Books You May Enjoy

Working with model field relationships

Django provides three relationship types for linking tables:

  • Manytoone
  • Manytomany
  • Onetoone

A many-to-one relationship is defined by using a ForeignKey field, and the other two relationship types are defined using the self-explanatory ManyToManyField and OneToOneField. These fields are named appropriately after the relationship type that they represent.

Next, we will discuss the key components of working with model field relationships.

Field arguments

The three field types, ForeignKey, ManyToManyField, and OneToOneField, all accept the standard default, blank, and verbose_name field arguments that other field types accept. The null argument will have no effect on a ManyToManyField and will only apply to the ForeignKey and OneToOneField types. Two of these field types—ForeignKey and OneToOneField—require at least two positional arguments, the first being...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image