Django Rest Framework POST fails: null value in column “cat_id” violates not-null constraint
I've recently converted my views to generic class-based views, however I've just noticed that POST requests fail on classes that have foreign-keys. The following is my code, followed by the error message.
models.py
class Category(models.Model):
name = models.CharField(max_length=25, blank=False)
class Meta:
ordering = ('id',)
class Task(models.Model):
name = models.CharField(max_length=25, blank=False)
cat = models.ForeignKey(Category, on_delete=models.CASCADE)
class Meta:
ordering = ('id',)
serializers.py
class TaskSerializer(serializers.ModelSerializer):
class Meta:
model = Task
fields = ('id', 'name', 'cat_id')
class CategorySerializer(serializers.ModelSerializer):
class Meta:
model = Category
fields = ('id', 'name')
views.py
class TaskList(generics.ListCreateAPIView):
"""
List all Tasks (OR for specified cat_id)
"""
queryset = Task.objects.all()
serializer_class = TaskSerializer
filter_fields = ('cat_id',)
urls.py
path('tasks/', views.TaskList.as_view()),
Error returned
django.db.utils.IntegrityError: null value in column "cat_id" violates not-null constraint
DETAIL: Failing row contains (51, buy-some, null).
REQUEST content: JSON Object
{
"name": "buy-some",
"cat_id": 1
}
Additionally, Content-Type, Accept headers are set to application/json.
Category with id=1 exists
python django python-3.x django-rest-framework django-class-based-views
add a comment |
I've recently converted my views to generic class-based views, however I've just noticed that POST requests fail on classes that have foreign-keys. The following is my code, followed by the error message.
models.py
class Category(models.Model):
name = models.CharField(max_length=25, blank=False)
class Meta:
ordering = ('id',)
class Task(models.Model):
name = models.CharField(max_length=25, blank=False)
cat = models.ForeignKey(Category, on_delete=models.CASCADE)
class Meta:
ordering = ('id',)
serializers.py
class TaskSerializer(serializers.ModelSerializer):
class Meta:
model = Task
fields = ('id', 'name', 'cat_id')
class CategorySerializer(serializers.ModelSerializer):
class Meta:
model = Category
fields = ('id', 'name')
views.py
class TaskList(generics.ListCreateAPIView):
"""
List all Tasks (OR for specified cat_id)
"""
queryset = Task.objects.all()
serializer_class = TaskSerializer
filter_fields = ('cat_id',)
urls.py
path('tasks/', views.TaskList.as_view()),
Error returned
django.db.utils.IntegrityError: null value in column "cat_id" violates not-null constraint
DETAIL: Failing row contains (51, buy-some, null).
REQUEST content: JSON Object
{
"name": "buy-some",
"cat_id": 1
}
Additionally, Content-Type, Accept headers are set to application/json.
Category with id=1 exists
python django python-3.x django-rest-framework django-class-based-views
add a comment |
I've recently converted my views to generic class-based views, however I've just noticed that POST requests fail on classes that have foreign-keys. The following is my code, followed by the error message.
models.py
class Category(models.Model):
name = models.CharField(max_length=25, blank=False)
class Meta:
ordering = ('id',)
class Task(models.Model):
name = models.CharField(max_length=25, blank=False)
cat = models.ForeignKey(Category, on_delete=models.CASCADE)
class Meta:
ordering = ('id',)
serializers.py
class TaskSerializer(serializers.ModelSerializer):
class Meta:
model = Task
fields = ('id', 'name', 'cat_id')
class CategorySerializer(serializers.ModelSerializer):
class Meta:
model = Category
fields = ('id', 'name')
views.py
class TaskList(generics.ListCreateAPIView):
"""
List all Tasks (OR for specified cat_id)
"""
queryset = Task.objects.all()
serializer_class = TaskSerializer
filter_fields = ('cat_id',)
urls.py
path('tasks/', views.TaskList.as_view()),
Error returned
django.db.utils.IntegrityError: null value in column "cat_id" violates not-null constraint
DETAIL: Failing row contains (51, buy-some, null).
REQUEST content: JSON Object
{
"name": "buy-some",
"cat_id": 1
}
Additionally, Content-Type, Accept headers are set to application/json.
Category with id=1 exists
python django python-3.x django-rest-framework django-class-based-views
I've recently converted my views to generic class-based views, however I've just noticed that POST requests fail on classes that have foreign-keys. The following is my code, followed by the error message.
models.py
class Category(models.Model):
name = models.CharField(max_length=25, blank=False)
class Meta:
ordering = ('id',)
class Task(models.Model):
name = models.CharField(max_length=25, blank=False)
cat = models.ForeignKey(Category, on_delete=models.CASCADE)
class Meta:
ordering = ('id',)
serializers.py
class TaskSerializer(serializers.ModelSerializer):
class Meta:
model = Task
fields = ('id', 'name', 'cat_id')
class CategorySerializer(serializers.ModelSerializer):
class Meta:
model = Category
fields = ('id', 'name')
views.py
class TaskList(generics.ListCreateAPIView):
"""
List all Tasks (OR for specified cat_id)
"""
queryset = Task.objects.all()
serializer_class = TaskSerializer
filter_fields = ('cat_id',)
urls.py
path('tasks/', views.TaskList.as_view()),
Error returned
django.db.utils.IntegrityError: null value in column "cat_id" violates not-null constraint
DETAIL: Failing row contains (51, buy-some, null).
REQUEST content: JSON Object
{
"name": "buy-some",
"cat_id": 1
}
Additionally, Content-Type, Accept headers are set to application/json.
Category with id=1 exists
python django python-3.x django-rest-framework django-class-based-views
python django python-3.x django-rest-framework django-class-based-views
edited Nov 14 '18 at 23:38
somekid
asked Nov 14 '18 at 21:36
somekidsomekid
318
318
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Probably what you want is to define the field cat
in your TaskSerializer
to be a PrimaryKeyRelatedField
(documentation here), in your case would be:
class TaskSerializer(serializers.ModelSerializer):
cat = PrimaryKeyRelatedField(queryset=Category.objects.all())
class Meta:
model = Task
fields = ('id', 'name', 'cat')
Then in your request just send the pk in the "cat"
field like so:
{
"name": "buy-some",
"cat": 1
}
This should do the trick.
Thank you. It did the trick!
– somekid
Nov 15 '18 at 22:33
add a comment |
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%2f53309082%2fdjango-rest-framework-post-fails-null-value-in-column-cat-id-violates-not-nul%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Probably what you want is to define the field cat
in your TaskSerializer
to be a PrimaryKeyRelatedField
(documentation here), in your case would be:
class TaskSerializer(serializers.ModelSerializer):
cat = PrimaryKeyRelatedField(queryset=Category.objects.all())
class Meta:
model = Task
fields = ('id', 'name', 'cat')
Then in your request just send the pk in the "cat"
field like so:
{
"name": "buy-some",
"cat": 1
}
This should do the trick.
Thank you. It did the trick!
– somekid
Nov 15 '18 at 22:33
add a comment |
Probably what you want is to define the field cat
in your TaskSerializer
to be a PrimaryKeyRelatedField
(documentation here), in your case would be:
class TaskSerializer(serializers.ModelSerializer):
cat = PrimaryKeyRelatedField(queryset=Category.objects.all())
class Meta:
model = Task
fields = ('id', 'name', 'cat')
Then in your request just send the pk in the "cat"
field like so:
{
"name": "buy-some",
"cat": 1
}
This should do the trick.
Thank you. It did the trick!
– somekid
Nov 15 '18 at 22:33
add a comment |
Probably what you want is to define the field cat
in your TaskSerializer
to be a PrimaryKeyRelatedField
(documentation here), in your case would be:
class TaskSerializer(serializers.ModelSerializer):
cat = PrimaryKeyRelatedField(queryset=Category.objects.all())
class Meta:
model = Task
fields = ('id', 'name', 'cat')
Then in your request just send the pk in the "cat"
field like so:
{
"name": "buy-some",
"cat": 1
}
This should do the trick.
Probably what you want is to define the field cat
in your TaskSerializer
to be a PrimaryKeyRelatedField
(documentation here), in your case would be:
class TaskSerializer(serializers.ModelSerializer):
cat = PrimaryKeyRelatedField(queryset=Category.objects.all())
class Meta:
model = Task
fields = ('id', 'name', 'cat')
Then in your request just send the pk in the "cat"
field like so:
{
"name": "buy-some",
"cat": 1
}
This should do the trick.
answered Nov 15 '18 at 1:51
ivissaniivissani
66657
66657
Thank you. It did the trick!
– somekid
Nov 15 '18 at 22:33
add a comment |
Thank you. It did the trick!
– somekid
Nov 15 '18 at 22:33
Thank you. It did the trick!
– somekid
Nov 15 '18 at 22:33
Thank you. It did the trick!
– somekid
Nov 15 '18 at 22:33
add a comment |
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%2f53309082%2fdjango-rest-framework-post-fails-null-value-in-column-cat-id-violates-not-nul%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