Matching blank entries in django queryset for optional field with corresponding ones in a required field

» python » Matching blank entries in django queryset for optional field with corresponding ones in a required field

By : user3863374

Date : January 02 2021, 06:48 AM

I hope this helps you . I have a django queryset in my views whose values I pack before passing to my template. There is a problem when the queryset returns none since associated values are not unpacked. the quersyet is called comments. , You could just do this:

code :

Share :

Django - How to make an optional field required based on request

By : user3862140

Date : March 29 2020, 07:55 AM

fixed the issue. Will look into that further Solved my problem by subclassing my forms as follows :
My form based on my model with null and blank = True

code :

class RegionForm(forms.ModelForm):
    class Meta:
        model = Region
        fields = ['region_name',
                  'region_description'
                  ]

    def __init__(self, *args, **kwargs):
        super(RegionForm, self).__init__(*args, **kwargs)
        for field in self.fields:
            self.fields[field].required = True

class RegionDraftForm(RegionForm):
    class Meta(RegionForm.Meta):
        pass

    def __init__(self, *args, **kwargs):
        super(RegionDraftForm, self).__init__(*args, **kwargs)
        for field in self.fields:
            self.fields[field].required = False

Django: Email field in form returning 'this field cannot be null/this field cannot be blank' even though there's an addr

By : Ahmed Mohsen

Date : March 29 2020, 07:55 AM

I wish this help you You've commented out the last line of the clean_email method, where it returns the value, so it returns None instead. The return value from that method is used as the value of the field, so you really need to return the actual email value.
(Really, when you're debugging something like this and it says "email cannot be blank", you should start by investigating why the field is being reported as blank, rather than fixing the model so that it can be.)

Correct way to set optional Django field to blank?

By : Cloud

Date : March 29 2020, 07:55 AM

seems to work fine You may pass None as the field value because your field has the attribute null set to True.
So you can have:

code :

club = Club.objects.create(hostname=form.cleaned_data['hostname'], co_hostname=None)

Retrieving Django QuerySet matching field in reverse query (related_name)

By : user2442005

Date : March 29 2020, 07:55 AM

To fix the issue you can do You was near the right answer, when you create the filter based on related models you should not use the set postfix, for example, for the models:

code :

class UserProfile(models.Model):
    username = models.CharField(max_length=200)

class SalesOrder(models.Model):
    pass

class InvDetail(models.Model):
    sales_order = models.ForeignKey('SalesOrder', on_delete=models.SET_NULL, null=True)

class SOSeller(models.Model):
    sales_order = models.ForeignKey('SalesOrder', on_delete=models.CASCADE)
    salesperson = models.ForeignKey('UserProfile', on_delete=models.CASCADE)

InvDetail.objects.filter(
    sales_order__soseller__salesperson__username__contains='tom'
)

A required field in form must now be made optional with a new field becoming required while having an optional relations

By : shridharbee

Date : October 06 2020, 11:00 AM

like below fixes the issue If you absolutely cannot migrate parts_number to any reasonable value, an option could be to create an STI model where you define the type for your records. Keep in mind the naming should not be Old and New - make them descriptive so they map to something from your domain.
Once you have STI in place: