Django porting error: expected string TypeError or byte-like object

If you have changed the fields in the models. after that you run makemigrations, this time asking like this

^C(api_env)nyros@nyros:~/Desktop/santhi_projects/sample_api/sample_api$ python manage.py makemigrations
You are trying to add a non-nullable field 'provider' to content without a default; we can't do that (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)
 2) Quit, and let me add a default in models.py
Select an option: 1

      

        
        
        
      

    

We choose 1 option, then it will display like this

Please enter the default value now, as valid Python
The datetime and django.utils.timezone modules are available, so you can do e.g. timezone.now()
>>> timezone.now()

      

        
        
        
      

    

We provided timezone.now () and then the mocking was done.

Look at the latest migration file, there is

class Migration(migrations.Migration):

dependencies = [
    migrations.swappable_dependency(settings.AUTH_USER_MODEL),
    ('providers', '0023_remove_content_provider'),
]

operations = [
    migrations.AddField(
        model_name='content',
        name='provider',
        field=models.ForeignKey(related_name='library', default=datetime.datetime(2016, 11, 1, 7, 15, 12, 655838, tzinfo=utc), to=settings.AUTH_USER_MODEL),
        preserve_default=False,
    ),
]

      

        
        
        
      

    

In the above code, observe this line

default=datetime.datetime(2016, 11, 1, 7, 15, 12, 655838, tzinfo=utc)

      

        
        
        
      

    

In this line, the default forgeinkey is datetime, is the value correct?

No, so you need to provide some string or default object for this field.

Now you need to edit this value in the appropriate migration file, for example

default='some string'

      

        
        
        
      

    

then save and run the migrate command.

Give it a try and let me know if it works or not. thank

Just delete all files in the migration folder except "init.py" and delete "db.sqlite3" in your database, now make the changes you want and migrate. Hope This helps :)

Same problem when starting with adding placeholders to my date fields, I accidentally entered "1" where it should be "django.utils.timezone.now" ie for the default date. Go to your last jump and find "default = xxx" which is not like the others and paste in "django.utils.timezone.now"

Go to folder migrations

" migrations

"

go to your migration file, for example "0054_comment_date.py"

change 'default'

in linefield=models.DateTimeField(auto_now_add=True, default=0)

from 0 or there is

by default='2012-09-04 06:00:00.000000-08:00

'

I faced the same problem. The solution was to remove all default spaces in the 'migrations' folder.

while you are typing 'python manage.py migrate' go to terminal and find exactly where the file in 'migrations' is stopping the migration. Then find all default arguments for DateField or DateTimeField and remove it. These models are not processed with a default argument.

migrations.AlterField(
        model_name='order',
        name='start_date',
        field=models.DateField(auto_now_add=True, ***BUG default=False BUG***),
        preserve_default=False,
    ),

      

        
        
        
      

    

See the log in your terminal:

Running migrations:
  Applying ang.0003_poll_end_date...Traceback (most recent call last):

      

        
        
        
      

    

there is an error in this file. Go there and remove the default argument from DateField

I faced the same problem. The solution was to remove all default spaces in the 'migrations' folder.

while you are typing 'python manage.py migrate' go to terminal and find exactly where the file in 'migrations' is stopping the migration. Then find all default arguments for DateField or DateTimeField and remove it. These models are not processed with a default argument.

Look at the log in your terminal: Running migrations: applying ang.0003_poll_end_date ... Traceback (last call was last):

there is an error in this file. Go there and remove the default argument from DateField