SQL dialect conversion method, device and system and storage medium

Abstract

The embodiment of the invention relates to an SQL dialect conversion method, device and system and a storage medium. The method comprises the steps that a to-be-converted SQL dialect and configuration information corresponding to the to-be-converted SQL dialect are obtained; analyzing the SQL dialect to be converted to generate a first grammar analysis model; processing the first grammar analysis model according to the configuration information to obtain a second grammar analysis model; and generating a target SQL dialect according to the configuration information and the second grammar analysis model. In the process, business codes used for being compatible with SQL languages of different databases do not need to be written. And the SQL dialect to be converted does not need to be converted into a specific SQL language, so that the database maintenance script and other development costs are greatly reduced.

Description

technical field [0001] Embodiments of the present invention relate to the field of computer technologies, and in particular, to a method, device, system, and storage medium for SQL dialect conversion. Background technique [0002] When developers develop applications, they can usually support one type of database to implement functions such as data storage and invocation. However, in the prior art, based on different databases used by different users, the application program needs to have the ability to support flexible switching between different database types. [0003] In order to realize the conversion of SQL dialects, that is, to realize the conversion between SQL languages ​​of different types of databases, in the prior art, the adopted means include: firstly, using the database ID (databaseID) provided by the persistence layer framework Mybatis to write different SQL (Structured Query Language, referred to as SQL) language to achieve switching between data types. Th...

AI Technical Summary

Problems solved by technology

[0005] 1) For different databases, there are differences in the SQL language written by database manufacturers (different SQL language expressions, applicable syntax, etc., and some may also have fields, functions, and table names customized by database manufacturers, etc.), If you need to switch between different databases, in order to achieve SQL language compatibility, you need to write multiple sets of codes that have nothing to do with the business. In addition, you need to write SQL adaptation codes, which makes the maintenance cost of database scripts too high.

2) The databaseID provided by Mybatis does not support custom mapping functions for various fields, functions, and table names, etc.

Some fields defined by the user cannot be directly called during the running of the application, resulting in running failure

3) The business code coupling in the database is serious, which leads to high cost when upgrading and optimizing the database table

[0006] However, the implementation of JOOQ software has the problem of charging, and there is also the problem of not supporting the custom mapping function of various fields, functions and table names.

[0007] That is, the above two SQL dialect conversion methods all have their inherent defects, so how to obtain a SQL dialect conversion method that can overcome the above defects has become a technical problem to be solved urgently in this application

Images