Re: It is impossible to add a non-nullable field 'details1' to feature without specifying a default. This is because the database needs something to populate existing rows.

That means you have done some changes in your model python file. So you have to drop your data base, delete the migration files, recreate the database with the same name as in your configuration python file and do migrations again. This will work or you can add default parameter with a value after max_length parameter for example default="" this will work too but if you take a look to your sql codes, you have define a default behavior if the user type nothing in the input field.

I'm sorry, i speak a little bit english i'm from a french country.

Yours sincerely 

Le sam. 25 mars 2023 à 19:57, Patricia Medina <patriciamedinameneses@gmail.com> a écrit :

Thats because you have values in the database...

If you don't need the data... eliminate the 001, 002, etc files of the migration folder...(this folder is in each application folder) and applicate the migrations again.

On Sat, Mar 25, 2023, 09:00 Ebenezer Otchere <swazyman1994@gmail.com> wrote:

Am new in django and have been getting errors in migrations, i need help

when i try to do migrations it keeps telling me this

it is impossible to add a non-nullable field 'details' to feature without specifying a default. This is because the database needs something to populate existing rows.
Please select a fix:
 1) Provide a one-off default now (will be set on all existing rows with a null value for this column)
 2) Quit and manually define a default value in models.py.

Thank you  in advance

from django.db import models

# Create your models here.

class feature(models.Model) :

   

    name = models.CharField(max_length=100)

    extra = models.CharField(max_length=100)

    details1 = models.CharField(max_length=500)

   

class art(models.Model):

   

    name = models.CharField(max_length=100)

    details = models.CharField(max_length=500)

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/06f462e2-3e1d-4a1a-8a97-b183586e5663n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2BMr2uxho70iCFjaPryhNx3AY0fXV4aKD5sKR%3DxGgNqo38rF7g%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAPy9iJL6JMat%3D7OGUmyuYe-PLC4GPcbdEuF7eSSo3tvd7BObhQ%40mail.gmail.com.