Mysql Workbench整数数据类型错误(INT更改>(11)) [英] Mysql Workbench integer datatype bug(INT changes > (11) )

查看:660
本文介绍了Mysql Workbench整数数据类型错误(INT更改>(11))的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我设置列的"INT"数据类型时,它看起来像Mysql Workbench alter table上的(11)". 所以我不能设置自动增量,外键...但是输入整数这样的数据没有问题.那是个错误吗?

When I set a "INT" datatype of a column, It's looking like this "(11)" on Mysql Workbench alter table. So I can't set auto increment, foreign key... But There is no issue for enter a data like integer. Is that a bug?

Mysql Workbench版本:6.1(6.1.4.117773内部版本1454)

Mysql Workbench Version: 6.1 (6.1.4.117773 build 1454)

操作系统:Windows 7 64位

OS: Windows 7 64 bit

Mysql Server版本:5.6

Mysql Server Version: 5.6

推荐答案

我假设 aleblebi 是土耳其语成员.但是我想,这个问题也可以在其他地区看到.首先,我将尝试解释问题,然后最后编写解决方案.

I assume aleblebi is a Turkish member. But I suppose, the problem can be seen on other locales too. First I will try to explain the problem and then I will write my solution in the end.

当您尝试使用Workbench GUI(我正在使用8.0.15版)更改表时,您会看到问题.网格的数据类型"列和数据类型:"文本框将显示(11)而不是INT(11),在DATETIME列中也可以看到相同的问题,但是这次数据类型框将完全为空.

You can see the problem when you try to alter table using Workbench GUI (I am using version 8.0.15). "Datatype" column of the grid and "Data Type:" text box will show (11) instead of INT(11), same problem can be seen in DATETIME columns but this time data type boxes will completely be empty.

问题.在向导结束时,您会看到类似以下内容的

Problem also can be seen if you try to use "Synchronize With any Source..." wizard of the Workbench. At the end of the wizard you can see something like:

ALTER TABLE `TEST_1`.`TABLE_1` 
CHANGE COLUMN `ID` `ID` (11) NULL DEFAULT NULL ,
DROP PRIMARY KEY;

代替:

ALTER TABLE `TEST_1`.`TABLE_1` 
CHANGE COLUMN `ID` `ID` INT(11) NULL DEFAULT NULL ,
DROP PRIMARY KEY;

我遇到了同样的问题,我在网上搜索了几天,却找不到解决方案( camadan 对我而言并不成功).最后,我意识到,不仅是INT数据类型,而且BIGINTDATETIME数据类型也有同样的问题.

I had the very same problem and I searched the web for a few days and couldn't find a solution (solution of camadan was not a success for me). At last I realized that it is not just INT data type but also BIGINT and DATETIME data types has the very same problem.

因此,我得出结论,每个以大写"I"字母开头的数据类型都存在相同的问题.并且在土耳其语字母中有点缀的大写字母İ和普通字母I,仅当您在Windows OS中选择土耳其语(土耳其)"作为区域格式"时,它们才会以某种方式破坏工作台. (我的操作系统是Windows 10英文)

So I concluded that every data type having an capital "I" letter in it has the very same problem. And in Turkish alphabet there are dotted capital letter İ and normal letter I which somehow breaks the Workbench only if you choose "Turkish (Turkey)" in Windows OS as "Regional format". (My OS is Windows 10 English)

因此,我仅通过将Windows 10的区域格式"设置从土耳其语(土耳其)"更改为英语(美国)"就解决了该问题.

So I solved the issue with just changing the "Regional format" setting of Windows 10 from "Turkish (Turkey)" to "English (United states)".

顺便说一句,我原样保留了国家或地区"选项(在Windows 10中仍为土耳其"),并且我始终将英语(美国)"用作非Unicode程序的语言" Windows 10开发环境中的选项.

By the way, I left the "Country or Region" option as it is (it is still "Turkey" in Windows 10) and I always use "English (United States)" as "Language for non-Unicode programs" option in my Windows 10 development environment.

我希望这一信息有一天能对某人有所帮助...

I hope this information will help somebody some day...

这篇关于Mysql Workbench整数数据类型错误(INT更改>(11))的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆