Splitting a django model using property and setters
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:
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?
Is there a better way this could be done?
Using:
Django 1.11
python django django-models
asked Nov 22 '18 at 0:01
nara_lnara_l
171114
add a comment |
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:
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?
Is there a better way this could be done?
Using:
Django 1.11
python django django-models
asked Nov 22 '18 at 0:01
nara_lnara_l
171114
add a comment |
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:
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?
Is there a better way this could be done?
Using:
Django 1.11
python django django-models
asked Nov 22 '18 at 0:01
nara_lnara_l
171114
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:
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?
Is there a better way this could be done?
Using:
Django 1.11
python django django-models
python django django-models
asked Nov 22 '18 at 0:01
nara_lnara_l
171114
asked Nov 22 '18 at 0:01
nara_lnara_l
171114
asked Nov 22 '18 at 0:01
nara_lnara_l
171114
asked Nov 22 '18 at 0:01
nara_lnara_l
171114
asked Nov 22 '18 at 0:01
nara_lnara_l
171114
171114
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422128%2fsplitting-a-django-model-using-property-and-setters%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422128%2fsplitting-a-django-model-using-property-and-setters%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
