Hi Xavier, Sorry, I misunderstood the earlier statement "JSON payload.".
Actually, you are right , the data which is fed to serializer for validating is in the form of JSON , since data is obtained at the internal API level using request.data (which generates unicode data). But to me, it seems like a bug in DRF, reason being if we don't override the implementation of "create" or "update" method, serializer validation will fail everytime, if we have "null" values in Database . Please correct me if I'm wrong in my understanding. Regards, Priyanka On Tuesday, 30 May 2017 12:24:36 UTC+5:30, Priyanka Thakur wrote: > > I am using Django rest 3.6.2 version . > > The model class is having a ForeignKey relationship as : > > class Deliverable(model.Model): > architectureattribute = models.ForeignKey(Architectureattribute, > blank=True, null=True) > > > > class DeliverableSerializer(serializers.ModelSerializer): > > class Meta: > > model = Deliverable > fields = tuple([getattr(x, 'name') for x in > Deliverable._meta.fields]) > > > > In Django Rest , the serializer object is decoded as for the foreign key as: > > > architectureattribute = PrimaryKeyRelatedField(allow_null=True, > queryset=Architectureattribute.objects.all(), required=False) > > With a put request i am updating only some fields and since I'm doing > migration, Database contains null value for the architectureattribute. > > > But with "null" value , serializer validation is failing. > > > On debugging I found that the PrimaryKeyRelatedField is not handling the > "null" value, even though allow_null property is set. > > > Please explain or guide, as to what I'm doing wrong here . > > > -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-rest-framework+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
