In trying to split a model in an already working application, I used property and setters to prevent making potentially hundreds of updates within the code base.

Model setup:

class A(models.Model):

  name = models.CharField()

  type = models.CharField()

  spec = models.SmallIntergerField()



  @property

  def salary(self):

      self.b.salary



  @salary.setter 

  def salary(self, value):

      self.b.salary = value

      self.b.save()



class B(models.Model):

  a = models.OneToOneField(A)

  salary = model.IntergerField()

  height = model.IntergerField()

Model usage

model_a = A(salary=129980, height=6.00, type="several types")

model_a.save()

Again I"m using property and setters to avoid changing queries in old migration files and several other places where the query occur in the code.

Question:

1. Does using property / setters in this way trigger inadvertently lot of queries when model A properties are called? i.e. are there cons to this?




2. Is there a better way this could be done?

Using:
Django 1.11