title: When to use one-to-one relationships in Django models
body: <p>I've read <a href="https://stackoverflow.com/questions/12318870/when-i-should-use-one-to-one-relationship">a few</a> <a href="https://stackoverflow.com/questions/9800490/django-onetoonefield-in-which-model-should-i-put-it">places</a> (see the second answer) that one-to-one relationships in Django models should almost always only be used for inheritance, or to access an otherwise inaccessible model (like the Django user model).  </p>
  
  <p>However, it seems like there are cases where you have an object that will always have exactly one instance of another object where you would logically want to separate those two objects.  Say, for example, your app was storing information about cars.  Each car has exactly one driver and each driver only drives one car.  Does it not make sense to separate car and driver into two separate models?</p>