manual/english/Integration/DBeaver.md
NOTE: The integration with DBeaver requires Manticore Buddy. If it doesn't work, make sure Buddy is installed.
DBeaver is a SQL client software application and a database administration tool. For MySQL databases, it applies the JDBC application programming interface to interact with them via a JDBC driver.
Manticore allows you to use DBeaver for working with data stored in Manticore tables the same way as if it was stored in a MySQL database. Currently, version 25.2.0 is tested and recommended. Other versions may work but could introduce issues.
To start working with Manticore in DBeaver, follow these steps:
New database connection option in DBeaver's UISQL -> MySQL as DBeaver's database driverServer host and Port options corresponding to the host and port of your Manticore instance (keep the database field empty)root/<empty password> as authentication credentialsSince Manticore does not fully support MySQL, only a part of DBeaver's functionality is available when working with Manticore.
You will be able to:
You will not be able to:
MyISAM will be set as the only storage engine available)Some MySQL data types are not currently supported by Manticore and, therefore, cannot be used when creating a new table with DBeaver. Also, a few of the supported data types are converted to the most similar Manticore types with type precision being ignored in such conversion. Below is the list of supported MySQL data types as well as the Manticore types they are mapped to:
BIGINT UNSIGNED => bigintBOOL => booleanDATE, DATETIME, TIMESTAMP => timestampFLOAT => floatINT => intINT UNSIGNED, SMALLINT UNSIGNED, TINYINT UNSIGNED, BIT => uintJSON => jsonTEXT, LONGTEXT, MEDIUMTEXT, TINYTEXT, BLOB, LONGBLOB, MEDIUMBLOB, TINYBLOB => textVARCHAR, LONG VARCHAR, BINARY, CHAR, VARBINARY, LONG VARBINARY => stringYou can find more details about Manticore data types here.
Manticore is able to handle the DATE, DATETIME and TIMESTAMP data types, however, this reqiures Manticore's Buddy enabled. Otherwise, an attempt to operate with one of these types will result in an error.
Note that the TIME type is not supported.
DBeaver's Preferences -> Connections -> Client identification option must not be turned off or overridden.
To work correctly with DBeaver, Manticore needs to distinguish its requests from others. For this, it uses client notification info sent by DBeaver in request headers. Disabling client notification will break that detection and, therefore, Manticore's correct functionality.
When trying to update data in your table for the first time, you'll see the No unique key popup message and will be asked to define a custom unique key.
When you get this message, perform the following steps:
Custom Unique Key optionid column in the columns listOkAfter that, you'll be able to update your data safely.