【问题标题】:How to fix "Truncated incorrect INTEGER value: 'UUID'" in Django如何在 Django 中修复“截断不正确的整数值:'UUID'”
【发布时间】:2019-09-30 07:55:01
【问题描述】:

我正在为我的网络应用程序创建一个应用程序,当我尝试将我的模型迁移到 MySQL 数据库时,Django 引发了如下所示的错误。

之前所有迁移都运行良好。我发现 CarInstance id 与主键 (pk) 相关联,这与我要使用的简单 url 模式 int:pk/> 不兼容,即 (showroom/car/2)。

我尝试通过简单的复制/粘贴将“id”变量移动到另一个类,该类将链接到 CarInstance 作为外键,类似于 MDN 对他们的 book 和 BookInstance 模型所做的操作。我认为这将有助于创建一个单独的主键,但我在这里。 :-)

urls.py

    path('', views.index, name='index'),
    path('cars/', views.CarListView.as_view(), name="cars"),
    path('car/<slug:uuid>/', views.CarDetailView.as_view(), name="car-detail"),
],

Models.py 代码(其他代码省略):

class CarInstance(models.Model):
    manufacturer = models.ForeignKey('Manufacturer', on_delete=models.SET_NULL, null=True)
    car_model = models.CharField('Model', max_length=50, null=True)
    description = models.TextField(max_length=4000)
    vin = models.CharField('VIN', max_length=17, help_text='Enter the 17 character VIN number.', blank=True, null=True)
    mileage = models.IntegerField(verbose_name='Mileage')
    car_images = models.ImageField(help_text='Upload pictures', upload_to=image_directory_path, storage=image_storage)
    date_added = models.DateField(auto_now_add=True)
    engine_displacement = models.CharField(default=2.0, max_length=3, help_text="Engine displacement in Liters (E.g. 2.0, 4.2, 6.3)")
    price = models.IntegerField(default=0)

    id = models.UUIDField(primary_key=True, default=uuid.uuid4,
    help_text="Unique ID for this car.", editable=False)

异常错误

我预计迁移会正常进行,但它会引发此错误。我不确定断点在哪里,所以我只是在这里发布了整个块。

C:\code\torque>py manage.py migrate
Operations to perform:
  Apply all migrations: admin, auth, contenttypes, sessions, showroom
Running migrations:
  Applying showroom.0012_auto_20190930_0701...Traceback (most recent call last):
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\mysql\base.py", line 71, in execute
    return self.cursor.execute(query, args)
  File "C:\Users\USER\Envs\torque\lib\site-packages\MySQLdb\cursors.py", line 209, in execute
    res = self._query(query)
  File "C:\Users\USER\Envs\torque\lib\site-packages\MySQLdb\cursors.py", line 315, in _query
    db.query(q)
  File "C:\Users\USER\Envs\torque\lib\site-packages\MySQLdb\connections.py", line 226, in query
    _mysql.connection.query(self, query)
MySQLdb._exceptions.OperationalError: (1292, "Truncated incorrect INTEGER value: '6ec1fa4ccc0b44f5b51269ff3c831929                                                                '")

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "manage.py", line 21, in <module>
    main()
  File "manage.py", line 17, in main
    execute_from_command_line(sys.argv)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\core\management\__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\core\management\__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\core\management\base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\core\management\base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\core\management\base.py", line 83, in wrapped
    res = handle_func(*args, **kwargs)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\core\management\commands\migrate.py", line 234, in handle
    fake_initial=fake_initial,
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\migrations\executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\migrations\executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\migrations\executor.py", line 245, in apply_migration
    state = migration.apply(state, schema_editor)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\migrations\migration.py", line 124, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\migrations\operations\fields.py", line 249, in database_forwards
    schema_editor.alter_field(from_model, from_field, to_field)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\base\schema.py", line 535, in alter_field
    old_db_params, new_db_params, strict)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\base\schema.py", line 685, in _alter_field
    params,
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\base\schema.py", line 137, in execute
    cursor.execute(sql, params)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\utils.py", line 99, in execute
    return super().execute(sql, params)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\utils.py", line 67, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\utils.py", line 76, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\utils.py", line 89, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "C:\Users\USER\Envs\torque\lib\site-packages\django\db\backends\mysql\base.py", line 71, in execute
    return self.cursor.execute(query, args)
  File "C:\Users\USER\Envs\torque\lib\site-packages\MySQLdb\cursors.py", line 209, in execute
    res = self._query(query)
  File "C:\Users\USER\Envs\torque\lib\site-packages\MySQLdb\cursors.py", line 315, in _query
    db.query(q)
  File "C:\Users\USER\Envs\torque\lib\site-packages\MySQLdb\connections.py", line 226, in query
    _mysql.connection.query(self, query)
django.db.utils.OperationalError: (1292, "Truncated incorrect INTEGER value: '6ec1fa4ccc0b44f5b51269ff3c831929                                                                '")

请注意,在 id (29) 的末尾和右引号之间有一个巨大的差距

更新:

过去几个小时我一直在处理这个问题,但我仍然无法进行迁移。我发现特定 CarInstances 的 url 使用 UUID,(例如 showroom/cars/6ec1fa4c-cc0b-44f5-b512-69ff3c831929)这是不雅观的。而且,即使语法正确,并且它们链接到正确的 id,页面仍然无法正常工作。他们抛出了一个 404 page not found 错误。

我正在尝试将 slug 方法合并到 url 中,但由于原始问题,我无法对模型进行任何更改。

如果您需要任何其他信息,请告诉我。

【问题讨论】:

  • 我真的不明白为什么你想要一个 UUID 但你不想在 URL 中使用它,但没关系。在这一点上,我认为你的迁移已经不同步了;我认为您应该将它们全部删除并删除数据库,然后重新开始。
  • 1.为了更好看的 url(showroom/cars/2/ 比 car/6ec1fa4c-cc0b-44f5-b512-69ff3c831929/ 干净得多) 2. 我读到在 url 中使用 uuid 会将数据暴露给安全漏洞。这只是关于以正确的方式设置它。你的意思是删除整个数据库,还是只删除对象本身?
  • 1) 是的,那你为什么要一个 uuid 呢? 2) 不,这是反过来。 URL 中的顺序 ID 是潜在的安全漏洞,uuid 不是
  • 删除表效果很好!我已经在下面回答了。至于为什么,我使用的两个教程都包含 UUID,而 pk 保持得很好,所以我只是接受它作为强制性的。无论如何,我会继续使用它们来保证安全。谢谢丹尼尔!

标签: mysql django database error-handling migration


【解决方案1】:

由于 Django/Mariadb 组合很少出现此问题,因此我采取了以下步骤来解决此问题。供未来的读者阅读。

  1. 打开 MySQL 客户端命令。
  2. 输入我的密码,然后更改我的数据库

MariaDB [(none)]&gt; use torquedb

  1. 已删除数据库,并创建了一个新数据库。
MariaDB [torquedb]> DROP database torquedb;
Query OK, 12 rows affected (0.089 sec)

MariaDB [(none)]> CREATE database torquedb
    -> ;
Query OK, 1 row affected (0.001 sec)

MariaDB [(none)]> show tables
    -> ;
ERROR 1046 (3D000): No database selected
MariaDB [(none)]> use torquedb
Database changed


  1. 然后我重新运行迁移
(torque) C:\code\torque> py manage.py makemigrations
torque) C:\code\torque> py manage.py migrate

幸运的是,该网站正在建设中,我只有三个对象进行测试。 :-)

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 2015-08-07
    • 2022-11-27
    • 2015-02-23
    • 1970-01-01
    • 1970-01-01
    • 2020-06-02
    • 1970-01-01
    相关资源
    最近更新 更多