We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The automatic highlighting when editing the SQL command text does not recognize multipoint and multipolygon as valid field types.
Steps to reproduce the behavior:
CREATE TABLE `test1` ( `amultipoint` multipoint DEFAULT NULL, `amultipolygon` multipolygon DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4
multipoint and multipolygon are accepted keywords for fieldtypes in mysql8. Neverless the entry is accepted when executing the query.
For testing here a table definition with all field types:
CREATE TABLE `test1` ( `aintunsignedauto` int(10) unsigned NOT NULL AUTO_INCREMENT, `aintsigned` int(10) NOT NULL DEFAULT -100, `afloat` float NOT NULL DEFAULT 123.4, `adouble` double NOT NULL DEFAULT 100000.12345, `adecimal` decimal(5,2) NOT NULL DEFAULT 999.99, `atinyint` tinyint(4) DEFAULT NULL, `asmallint` smallint(6) DEFAULT NULL, `amediumint` mediumint(9) DEFAULT NULL, `abigint` bigint(20) DEFAULT NULL, `adate` date DEFAULT NULL, `adatetime` datetime DEFAULT NULL, `atimestamp` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), `atime` time DEFAULT NULL, `ayear` year(4) DEFAULT NULL, `aintnull` int(11) DEFAULT NULL, `acharutf8mb4generalci` char(10) DEFAULT NULL, `avarcharascii` varchar(20) CHARACTER SET ascii NOT NULL, `atinytext` tinytext DEFAULT NULL, `atext` text DEFAULT NULL, `amediumtext` mediumtext DEFAULT NULL, `alongtext` longtext DEFAULT NULL, `ajson` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL, `aenum` enum('a','b','c') DEFAULT NULL, `aset` set('x','y','z') DEFAULT NULL, `abit` bit(1) NOT NULL, `abinary` binary(1) DEFAULT NULL, `avarbinary` varbinary(10000) DEFAULT NULL, `atinyblob` tinyblob DEFAULT NULL, `ablob` blob DEFAULT NULL, `amediumblob` mediumblob DEFAULT NULL, `alongblob` longblob DEFAULT NULL, `ageometry` geometry DEFAULT NULL, `apoint` point DEFAULT NULL, `alinestring` linestring DEFAULT NULL, `apolygon` polygon DEFAULT NULL, `amultipoint` multipoint DEFAULT NULL, `amultilinestring` multilinestring DEFAULT NULL, `amultipolygon` multipolygon DEFAULT NULL, `ageometrycollection` geometrycollection DEFAULT NULL, `aintwidedisplay` int(20) DEFAULT NULL, PRIMARY KEY (`aintunsignedauto`) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4
The text was updated successfully, but these errors were encountered:
I moved this issue here as it is the right place to be fixed.
Sorry, something went wrong.
multipoint
multipolygon
e29ed1e
williamdes
Successfully merging a pull request may close this issue.
Describe the bug
The automatic highlighting when editing the SQL command text does not recognize multipoint and multipolygon as valid field types.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
multipoint and multipolygon are accepted keywords for fieldtypes in mysql8. Neverless the entry is accepted when executing the query.
For testing here a table definition with all field types:
The text was updated successfully, but these errors were encountered: