The database is happy by default bin-log mode, and there are many requirements for custom events, so I won’t go into details here.Problems that may be encountered in the import operation "This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA …" is thrown when importing custom events After that, the following picture will appear, select the database to import data to.Just click the right mouse button in the document, the following menu appears, choose Run 'pts.sql' to.If the file is too large, the following prompt may appear, don’t care.In fact, you only need to drag the exported SQL file directly from the outside to DataGrip.As shown in the figure below, there is a Run SQL Script option in the right-click menu, but it always fails in actual operation, so far.You can get them by cloning the dumps repository. For illustration purposes, we will use Sakila dump files. Alternatively, you can attach a folder with these scripts to the Files tool window and run them from here. When the export operation is specified, it will not be exported together, and manual operation is required. To run SQL scripts, you can right-click the data source and select Run SQL script. As shown in the figure below, there are custom events in the database.Unable to export custom events during export Reference from the interpretation of the column_statistics, as well as specific solutions.column-statistics=0 Can ignore this table Add at the bottom of the export interface above.In fact, the database is currently connected and used, so MySQL believes that direct export will cause data inconsistency.Problems that may be encountered in the export operation "Does not exist when using LOCK TABLES" error is thrown when exporting For example, pts.sql in the figure below is the manually entered
#DATAGRIP RUN SQL FILE DRIVER#
DataGrip advanced tab fields In the General tab, click the plus sign in the Driver Files field.