My app has clients that each have a single billing profile.
I'm envisioning my app having a "Client" model with an attribute called "billing_profile" which would reference another model called "BillingProfile". Rather than define "BillingProfile" with a foreign key back to "Client" (ie, "client = models.ForeignKey(Client)"), I was thinking that since there will only be one billing profile for each client that I could simply use a one-to-one field instead. Does this seem logical to do, or does it seem backwards (Then I would have to create a BillingProfile before ever establishing a Client). Is there a good way to do this versus my paradigm of understanding it?