Python django-TypeError:应为字符串或缓冲区
您好,我在模型中添加了一个字段,当我尝试在终端中执行Python django-TypeError:应为字符串或缓冲区,python,django,Python,Django,您好,我在模型中添加了一个字段,当我尝试在终端中执行migrate时,它会给我这个错误,有人知道这可能是什么吗 ========================================================================= File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/Users/Derek/.virtualenvs
migrate
时,它会给我这个错误,有人知道这可能是什么吗
=========================================================================
File "manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
utility.execute()
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/core/management/__init__.py", line 377, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/core/management/base.py", line 288, in run_from_argv
self.execute(*args, **options.__dict__)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/core/management/base.py", line 338, in execute
output = self.handle(*args, **options)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 161, in handle
executor.migrate(targets, plan, fake=options.get("fake", False))
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/migrations/executor.py", line 68, in migrate
self.apply_migration(migration, fake=fake)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/migrations/executor.py", line 102, in apply_migration
migration.apply(project_state, schema_editor)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/migrations/migration.py", line 108, in apply
operation.database_forwards(self.app_label, schema_editor, project_state, new_state)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/migrations/operations/fields.py", line 139, in database_forwards
schema_editor.alter_field(from_model, from_field, to_field)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/backends/schema.py", line 454, in alter_field
self._alter_field(model, old_field, new_field, old_type, new_type, old_db_params, new_db_params, strict)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/backends/sqlite3/schema.py", line 199, in _alter_field
self._remake_table(model, alter_fields=[(old_field, new_field)])
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/backends/sqlite3/schema.py", line 137, in _remake_table
self.create_model(temp_model)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/backends/schema.py", line 212, in create_model
definition, extra_params = self.column_sql(model, field)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/backends/schema.py", line 124, in column_sql
default_value = self.effective_default(field)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/backends/schema.py", line 187, in effective_default
default = field.get_db_prep_save(default, self.connection)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/models/fields/__init__.py", line 627, in get_db_prep_save
prepared=False)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/models/fields/__init__.py", line 1290, in get_db_prep_value
value = self.get_prep_value(value)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/models/fields/__init__.py", line 1269, in get_prep_value
value = super(DateTimeField, self).get_prep_value(value)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/models/fields/__init__.py", line 1171, in get_prep_value
return self.to_python(value)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/db/models/fields/__init__.py", line 1228, in to_python
parsed = parse_datetime(value)
File "/Users/Derek/.virtualenvs/tasks/lib/python2.7/site-packages/django/utils/dateparse.py", line 70, in parse_datetime
match = datetime_re.match(value)
TypeError: expected string or buffer
我相信您在以下行的
default=False
中有错误:
completion_date = models.DateTimeField(blank=False, null=True, default=False)
False
不是有效日期default
expected。使用default=datetime。现在改为。Django的DateTimeField
通常用于Pythondatetime
和date
对象,但是。在您的DateTimeField
声明中
default=False
既不是datetime
也不是date
。因此,Django尝试为您自动解析它。如果做不到这一点,它就会发出神秘的信息
根据您的具体需要,您应该替换或删除default=False
参数。我以前也遇到过同样的问题。我尝试了default=False,但没有做任何更改。然后我添加default=timezone。现在,它可以正常工作了。唯一的问题是日期字段不显示在管理部分
更改此字段:
best_day_to_contact = models.DateTimeField(blank=False, null=True)
from django.utils import timezone
best_day_to_contact = models.DateTimeField(default=timezone.now)
对于此字段:
best_day_to_contact = models.DateTimeField(blank=False, null=True)
from django.utils import timezone
best_day_to_contact = models.DateTimeField(default=timezone.now)
我想这个解决方案可能会解决你的问题。我只是想参与进来,因为这个问题让我很头疼。在我添加了models.DateField之后,Django发现了一个错误的迁移。直到我删除了所有迁移并重新运行makemigrations,它才自行修复
/* Example Model */
class user(models.Model):
created = models.DateField(auto_now_add=True)
def __str__(self):
return str(self.id)
/*When you generate migrations file then it will add (default=1)
*Remove default=1
*field=models.DateField(default=1, auto_now_add=True),
*To
*field=models.DateField(auto_now_add=True)
*Then do sqlmigrate or migrate.
*/
希望这有帮助 要解决此问题,可能需要返回文本编辑器并删除所有迁移。这通常发生在django在恶劣的迁徙中着陆时。然后重新进行新的迁移。希望这能很好地解决您的问题<代码>值
不是所需的字符串或缓冲区。执行它的代码是什么,和/或传递给导致错误的函数的值是什么?发布您的模型code@oke1:你能把你的models.py课程发到这里吗?我以前也有同样的问题。我尝试了default=False
,但没有做任何更改。然后我添加了default=timezone。现在它可以正常工作了。唯一的问题是日期字段没有显示在管理部分。是的,我以前也有同样的问题。我尝试了default=False
它没有做任何更改。然后我添加了default=timezone。现在它就可以正常工作了。唯一的问题是日期字段没有显示在管理部分。通过添加auto_now_add=True并删除默认值,它帮助我解决了带有DateTime的Django命令的问题。谢谢,谢谢。我试着用这种方式执行,它对我有效。