CN113094384A

CN113094384A - SQL (structured query language) file configuration method and device and terminal equipment

Info

Publication number: CN113094384A
Application number: CN201911354268.4A
Authority: CN
Inventors: 夏登成
Original assignee: Shenzhen Intellifusion Technologies Co Ltd
Current assignee: Shenzhen Intellifusion Technologies Co Ltd
Priority date: 2019-12-23
Filing date: 2019-12-23
Publication date: 2021-07-09
Anticipated expiration: 2039-12-23
Also published as: CN113094384B

Abstract

The application is applicable to the technical field of databases, and provides a method, a device and a terminal device for configuring an SQL (structured query language) file, wherein the method for configuring the SQL file comprises the following steps: acquiring a dependency relationship between first SQL files in a target database; selecting at least one first SQL file from the first SQL files based on preset SQL file selection conditions and dependency relations to generate an SQL file set; replacing the file name of each SQL file in the SQL file set and the content of a preset position in the file content by using a preset variable to generate a plurality of second SQL files; and executing the plurality of second SQL files. According to the method and the system, the SQL file to be configured can be rapidly configured in the database, and the SQL file can be repeatedly configured by changing the preset variable, so that codes are reduced, and the efficiency of SQL file configuration is improved.

Description

SQL (structured query language) file configuration method and device and terminal equipment

Technical Field

The application belongs to the technical field of databases, and particularly relates to a method and a device for configuring an SQL (structured query language) file and terminal equipment.

Background

The traditional database version control tool can only control the version of an SQL (Structured Query Language) file at the database level, but cannot flexibly configure the SQL file in a single database.

Disclosure of Invention

In order to overcome the problems in the related art, the embodiment of the application provides a method and a device for configuring an SQL file and a terminal device.

The application is realized by the following technical scheme:

in a first aspect, an embodiment of the present application provides a method for configuring an SQL file, including:

acquiring the dependency relationship among all first Structured Query Language (SQL) files in a target database;

selecting at least one first SQL file from the first SQL files based on a preset SQL file selection condition and the dependency relationship to generate an SQL file set;

replacing the file name of each first SQL file in the SQL file set and the content of a preset position in the file content by a preset variable to generate a plurality of second SQL files; the preset variables comprise file name variables corresponding to file names and content variables corresponding to file contents;

and executing the plurality of second SQL files.

Illustratively, the first target SQL file is an SQL file that is not dependent on other first SQL files.

Optionally, the determining, according to the dependency relationship, a second target SQL file having a dependency relationship with the first target SQL file includes:

selecting a second target SQL file with a dependency relation with the first target SQL file based on the topological structure of the directed acyclic graph;

wherein the second target SQL file comprises a second target SQL file directly dependent on the first target SQL file and a first SQL file indirectly dependent on the target SQL file through other first SQL files.

Optionally, the generating the SQL file set according to the association sequence of the association relationship between the first target SQL file and each second target SQL file includes:

and sequencing the first target SQL file and each second target SQL file according to the topological order of the first target SQL file and each second target SQL file in the directed acyclic graph to generate the SQL file set.

Optionally, the replacing, by using a preset variable, the file name of each first SQL file in the SQL file set and the content of a preset position in the file content to generate a plurality of second SQL files includes:

replacing the content of the preset position in the file name of each SQL file in the SQL file set by using the file name variable;

and replacing the content at the preset position in the file content of each SQL file in the SQL file set by using the content variable.

Illustratively, the file name of the SQL file includes version information and file name information, and the content at the preset position in the file name of each SQL file in the SQL file set is replaced by the file name variable specifically:

and replacing the file name information in the file name of each SQL file in the SQL file set by adopting the file name variable.

In a second aspect, an embodiment of the present application provides an SQL file configuration apparatus, including:

the dependency relationship acquisition module is used for acquiring the dependency relationship among the first Structured Query Language (SQL) files in the target database;

the SQL file set generating module is used for selecting at least one first SQL file from the first SQL files based on preset SQL file selection conditions and the dependency relationship to generate an SQL file set;

the variable replacing module is used for replacing the file name of each first SQL file in the SQL file set and the content of a preset position in the file content by adopting a preset variable to generate a plurality of second SQL files; the preset variables comprise file name variables corresponding to file names and content variables corresponding to file contents;

and the execution module is used for executing the plurality of second SQL files.

In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the SQL file configuration method according to any one of the first aspect when executing the computer program.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the SQL file configuration method according to any of the first aspect is implemented.

In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a terminal device, causes the terminal device to execute the SQL file configuration method according to any of the foregoing first aspects.

It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.

Compared with the prior art, the embodiment of the application has the advantages that:

in the embodiment of the application, the dependency relationship between the first SQL files in the target database is obtained, and then based on the preset SQL file selection condition and the dependency relationship, selecting at least one first SQL file in the first SQL files to generate an SQL file set, then, the preset variables are adopted to replace the file names of all SQL files in the SQL file set and the content of the preset positions in the file content, thereby generating a plurality of second SQL files, thereby selecting the SQL file to be configured in the target database through the preset SQL file selection condition, then, the preset variables are adopted to replace the file name of the SQL file to be configured and the variables of the file content to generate a new SQL file, the SQL file to be configured can be rapidly configured in the target database, and the SQL file can be repeatedly configured by changing the preset variable, so that codes are reduced, and the SQL file configuration efficiency is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic view of an application scenario of an SQL file configuration method according to an embodiment of the present application;

fig. 2 is a schematic flowchart of an SQL file configuration method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of an SQL file configuration method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a topology of a directed acyclic graph according to an embodiment of the present application;

fig. 5 is a schematic flowchart of an SQL file configuration method according to an embodiment of the present application;

fig. 6 is a schematic flowchart of an SQL file configuration method according to an embodiment of the present application;

FIG. 7 is a flowchart illustrating a method for configuring an SQL file according to an embodiment of the present application;

fig. 8 is a schematic flowchart of an SQL file configuring apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an SQL file configuring apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a computer to which the SQL file configuration method according to an embodiment of the present application is applied.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

Based on the above problems, embodiments of the present application provide an SQL file configuration method, first obtain a dependency relationship between SQL files in a target database, then select a desired SQL file from the SQL files in the target database according to a preset SQL file selection condition and the dependency relationship, replace a file name of the selected SQL file and content of a set position in file content with a preset variable, generate a new SQL file, and execute the new SQL file, so that the SQL file to be configured can be rapidly configured in the target database, and the SQL file can be configured repeatedly by changing the preset variable, thereby reducing codes and improving the efficiency of SQL file configuration.

For example, the embodiment of the present application can be applied to the exemplary scenario shown in fig. 1. In this scenario, the terminal 10 may receive a preset SQL file selection condition, a preset variable, and an SQL file configuration request input by a user, and upload the SQL file selection condition, the preset variable, and the SQL file configuration request to the server 20; the server 20 may obtain a dependency relationship between the SQL files in the target database according to the SQL file configuration request, select a required SQL file from the SQL files in the target database according to a preset SQL file selection condition and the dependency relationship, replace a file name of the selected SQL file and content of a set position in the file content with a preset variable, generate a new SQL file, and execute the new SQL file.

In the above scenario, the terminal 10 may be a computer, a tablet computer, a notebook computer, a netbook, a Personal Digital Assistant (PDA), a smart phone, or other terminals, and the specific type of the terminal is not limited in this embodiment of the application.

It should be noted that the application scenarios described above are used as an exemplary illustration, and are not used to limit the application scenarios in the embodiments of the present application, and in fact, the embodiments of the present application may also be applied to other application scenarios. For example, in other exemplary application scenarios, information such as a preset SQL file selection condition, a preset variable, and an SQL file configuration request may also be sent to the server 20 through the cloud.

In order to make the technical solutions of the present invention better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to fig. 1, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 2 is a schematic flow chart of an SQL file configuration method according to an embodiment of the present application, and with reference to fig. 2, the SQL file configuration method is described in detail as follows:

in step 101, the dependency relationship between the first structured query language SQL files in the target database is obtained.

Each first SQL file in the target database may be all the SQL files stored in the target database, or may be an SQL file in a certain set in the target database, which is not limited in this embodiment of the present application.

In general, the file name of the SQL file may include version information and file name information. For example, the file name of the SQL file may be v [ version ] _[ desc ]. SQL, where the former "version" is version information, the version information may be sorted by dictionary, and the larger the version number is, the newer the SQL file is; the following "desc" is file name information, ". SQL" characterizes the format of the SQL file.

In this embodiment, other SQL files having a dependency relationship with the current SQL file may be recorded at a set position in the file content of the SQL file. For example, other SQL files having a dependency relationship with the current SQL file may be recorded in the first row of the file content of the SQL file, and of course, other SQL files having a dependency relationship with the current SQL file may also be recorded in other positions of the file content of the SQL file.

In addition, the expression form of the dependency relationship in the embodiment of the present application is also not limited, and for example, the expression form may record the dependency relationship in a text form, may record the dependency relationship in an annotation form, or may record the dependency relationship in another form.

Referring to fig. 3, in some embodiments, based on the embodiment shown in fig. 2, step 101 may be specifically implemented by the following steps:

in step 1011, the annotation content in the file content of each of the first SQL files is obtained, and the annotation content records the SQL file that the current SQL file depends on.

In this embodiment, other SQL files having a dependency relationship with the current first SQL file are recorded in the file content of the first SQL file in the form of annotations. For example, the dependency relationship may be other SQL files on which the current first SQL file depends.

Specifically, the dependency relationship is illustrated by taking two SQL files, i.e., "V20191020 _ $ { table1}. SQL" and "V20191030 _ $ { table1}. SQL". For "V20191030 _ $ { table1}. SQL" SQL file, "V20191030" is the version number of the SQL file, and for example, the generation date of the SQL file may be the version number of the SQL file, and "table 1" is the file name of the SQL file.

In the file content of the "V20191030 _ $ { table1}. SQL" SQL file, a content representing that the "V20191030 _ $ { table1}. SQL" SQL file depends on the "V20191020 _ $ { table1}. SQL" SQL file may be recorded in a comment form. For the "V20191020 _ $ { table1}. SQL" SQL file, since it does not depend on other SQL files, the content related to the dependency relationship may not be recorded in the file content of the "V20191020 _ $ { table1}. SQL" SQL file.

In step 1012, the dependency relationship between the first SQL files is determined according to the annotation content.

For example, for the a1 file, the a2 file and the A3 file, if the a2 file depends on the a1 file and the A3 file depends on the a2 file, the a1 file, the a2 file and the A3 file have a dependency relationship therebetween; for the a1 file, the a2 file, and the B1 file, if the a2 file depends on the a1 file, neither the a1 file nor the a2 file depends on the B1 file, and neither the B1 file depends on the a1 file or the a2 file, there is a dependency between the a1 file and the a2 file, and there is no dependency between the B1 file and both the a1 file and the a2 file.

Specifically, a dependency relationship exists between two SQL files, namely "V20191020 _ $ { table1}. SQL" and "V20191030 _ $ { table1}. SQL", and specifically, the dependency relationship between the two SQL files is "V20191030 _ $ { table1}. SQL" and depends on the "V20191020 _ $ { table1}. SQL".

In addition, if a "V20191031 _ $ { table1}. SQL" SQL file exists, wherein a "V20191031 _ $ { table1}. SQL" SQL file depends on the content of the "V20191030 _ $ { table1}. SQL" SQL file, which is recorded in a form of a comment in the file content, a dependency relationship exists among the "V20191020 _ $ { table1}. SQL" SQL file, "V20191030 _ $ { table1}. SQL" SQL file and the "V20191031 _ $ { table1}. SQL" SQL file, specifically, the "V20191031 _ $ { table1}. sq9126 }. SQL file depends on the" V201919120191201913 _ $ 201913 _, SQL } SQL file, which is dependent on the "V20191919120191031 _ $ { table1}. SQL } SQL file, which is dependent on the" SQL file, which is V201914 _ $ 20191493 _.

Optionally, step 101 may further include:

generating a directed acyclic graph according to the dependency relationship among the first SQL files;

and each node of the directed acyclic graph is the first SQL file.

Illustratively, for "V20191020 _ $ { table1}. SQL" SQL file, "V20191030 _ $ { table1}. SQL" SQL file, "V20191031 _ $ { table1}. SQL" SQL file, "V20191020 _ $ { table2}. SQL" SQL file, "V20191030 _ $ { table2}. SQL" SQL file, and "V20191030 _ view. SQL" SQL file, a directed acyclic graph is generated as shown in fig. 4.

Wherein the "V20191031 _ $ { table1}. SQL" SQL file depends on the "V20191030 _ $ { table1}. SQL" SQL file, the "V20191030 _ $ { table1}. SQL" SQL file depends on the "V20191020 _ $ { table1}. SQL" SQL file, the "V20191030 _ $ { table2}. SQL" SQL file depends on the "V20191020 _ $ { table2}. SQL" SQL file, and the "V20191030 _ view.sql" SQL file depends on the "V20191020 _ $ { table1}. SQL" SQL file and the "V20191020 _ $ { table 91 2}. SQL" SQL file.

In step 102, based on a preset SQL file selection condition and the dependency relationship, at least one first SQL file is selected from the first SQL files, and an SQL file set is generated.

The preset SQL file selection condition may be included in a configuration file, and the configuration file may be sent to a database of the server through a terminal or a cloud.

In this embodiment, through the preset SQL file selection condition and the dependency relationship, the server can select a required SQL file from the first SQL file to perform configuration in subsequent steps.

Referring to fig. 5, in some embodiments, based on the embodiment shown in fig. 2, step 102 may be specifically implemented by the following processes:

in step 1021, a first target SQL file is determined in the first SQL file based on the preset SQL file selection condition and the dependency relationship.

Illustratively, the first target SQL file may be an SQL file that is not dependent on other first SQL files. For example, for the five SQL files in fig. 4, one or both of "V20191020 _ $ { table1}. SQL" SQL file and "V20191020 _ $ { table2}. SQL" SQL file may be the first target SQL file, specifically, which SQL file or both SQL files are the first target SQL file, and the preset SQL file selection condition is used to determine the target SQL file.

In a possible implementation manner, the preset SQL file selection condition may specifically be that an SQL file without dependency is specified, an SQL file having a dependency relationship with the SQL file is determined according to the SQL file, and the SQL file having a dependency relationship with the SQL file are used as the required SQL file. The preset SQL file selection condition in this embodiment may be implemented by a regular expression, and under the condition that there are many SQL files, the file name of each required SQL file does not need to be input, which is convenient to implement.

In addition, when the number of SQL files is small, the required file name of each SQL file may be directly used as the preset SQL file selection condition, that is, the required SQL file may be determined directly according to the file name of each SQL file.

In step 1022, at least one second target SQL file is selected from the first SQL file based on the first target SQL file and the dependency relationship, generating a SQL file set.

Specifically, an SQL file dependent on the first target SQL file may be used as the SQL file set. The SQL file dependent on the first target SQL file may include an SQL file directly dependent on the first target SQL file, or may include an SQL file indirectly dependent on the first target SQL file through another first SQL file.

Illustratively, step 1022 may include the steps of:

in step a, according to the dependency relationship, a second target SQL file having a dependency relationship with the first target SQL file is determined.

Taking fig. 4 as an example, if the first target SQL file is a "V20191020 _ $ { table1}. SQL" SQL file, the determined second target SQL file may include a "V20191030 _ $ { table1}. SQL" SQL file and a "V20191031 _ $ { table1}. SQL" SQL file;

if the first target SQL file is a "V20191020 _ $ { table2}. SQL" SQL file, the determined second target SQL file may include a "V20191030 _ $ { table2}. SQL" SQL file;

if the first target SQL file is "V20191020 _ $ { table1}. SQL" SQL file and V20191020_ $ { table2}. SQL "SQL file, the determined second target SQL file may include" V20191030_ $ { table1}. SQL "SQL file," V20191031_ $ { table1}. SQL "SQL file," V20191030_ $ { table2}. SQL "SQL file and" V20191030_ view.

In some embodiments, the step a may specifically be:

wherein the second target SQL file can comprise a second target SQL file directly dependent on the first target SQL file and a first SQL file indirectly dependent on the target SQL file through other first SQL files.

Specifically, a second target SQL file having a dependency relationship with the first target SQL file may be selected according to the topology structure of the directed acyclic graph. For example, the "V20191020 _ $ { table1}. SQL" SQL file may be used as the first target SQL file, and each second target SQL file may be determined according to the topology structure of the directed acyclic graph shown in fig. 4.

In step B, the SQL file set is generated according to the association sequence of the association relationship between the first target SQL file and each second target SQL file.

Taking the first target SQL file as "V20191020 _ $ { table1}. SQL" SQL file as an example, the SQL file set generated according to the association sequence may include an SQL file list, and the SQL file list sequentially includes "V20191020 _ $ { table1}. SQL", "V20191030 _ $ { table1}. SQL" and "V20191031 _ $ { table1}. SQL".

In some embodiments, the step B may specifically be:

Specifically, the first target SQL file and each second target SQL file may be sorted according to the topological order of the directed acyclic graph shown in fig. 4 and in the direction of the arrow, so as to generate the SQL file set.

In this embodiment, a first target SQL file is determined based on a preset SQL file selection condition and the dependency relationship, a second target SQL file having a dependency relationship with the first target SQL file is selected, and an SQL file set is generated, where the preset SQL file selection condition may specify an independent SQL file to be configured as the first target SQL file, and one or more second target SQL files directly or indirectly dependent on the first target SQL file may be determined according to the dependency relationship, so as to obtain the SQL file set.

In step 103, the file name of each SQL file in the SQL file set and the content of the preset position in the file content are replaced by a preset variable, and a plurality of second SQL files are generated.

The preset variables may include a file name variable corresponding to a file name and a content variable corresponding to file content.

In some embodiments, step 103 may specifically include:

replacing the content of the preset position in the file name of each SQL file in the SQL file set by adopting the file name variable;

In the embodiment, the content of the preset position in the file name of each SQL file in the SQL file set is replaced by the file name variable, and the content of the preset position in the file content of each SQL file in the SQL file set is replaced by the content variable, so that a new SQL file can be generated quickly, the implementation is convenient and simple, the next configuration of the SQL file can be performed by changing the file name variable and the content variable, and the efficiency of the SQL file configuration can be improved.

Illustratively, the file name of the SQL file may include version information and file name information, and the replacing of the content at the preset position in the file name of each SQL file in the SQL file set with the file name variable may specifically be:

For example, the filename variable may be "table 3", the content variable may be "XXX", and for a "V20191020 _ $ { table1}. SQL" SQL file, the filename variable "table 3" is used to replace filename information "table 1" in the filename of the "V20191020 _ $ { table1}. SQL" SQL file, and the content variable "XXX" is used to replace content at a preset position in the file content of the "V20191020 _ $ { table1}. SQL" SQL file, so that the obtained SQL file has a filename of "V20191020 _ $ { table3}. SQL", and the content at the preset position is "XXX".

For the "V20191030 _ $ { table1}. SQL" SQL file, the file name information "table 1" in the file name of the "V20191030 _ $ { table1}. SQL" SQL file is replaced by the file name variable "table 3", the content at the preset position in the file content of the "V20191030 _ $ { table1}. SQL" SQL file is replaced by the content variable "XXX", the obtained SQL file has the file name of "V20191030 _ $ { table3}. SQL", and the content at the preset position is "XXX".

For the "V20191031 _ $ { table1}. SQL" SQL file, the file name information "table 1" in the file name of the "V20191031 _ $ { table1}. SQL" SQL file is replaced by a file name variable "table 3", the content at the preset position in the file content of the "V20191031 _ $ { table1}. SQL" SQL file is replaced by a content variable "XXX", the file name of the obtained SQL file is "V20191031 _ $ { table3}. SQL", and the content at the preset position is "XXX".

In step 104, the plurality of second SQL files are executed.

After the second SQL files are obtained through steps 101 to 103, the SQL files may be executed.

Referring to fig. 6, in some embodiments, step 104 may specifically include the following processes:

in step 1041, sequentially executing each second SQL file according to the association sequence.

Because each second SQL file has a dependency relationship, each second SQL file needs to be sequentially executed according to the association sequence corresponding to the dependency relationship.

For example, for the generated three second SQL files "V20191020 _ $ { table3}. SQL", "V20191020 _ $ { table3}. SQL" and "V20191020 _ $ { table3}. SQL", the order of executing the three second SQL files in this step is "V20191020 _ $ { table3}. SQL" SQL file, "V20191020 _ $ { table3}. SQL" SQL file and "V20191020 _ $ { table3}. SQL" SQL file.

In step 1042, after the execution of each second SQL file is completed, each second SQL file is recorded.

After the execution of each second SQL file is completed, the file name of each executed second SQL file may be recorded in the target database, so that the executed SQL files may be prevented from being repeatedly executed.

Optionally, in some embodiments, before step 104, the SQL file configuration method may also include a step of removing duplicates of each second SQL file according to existing SQL files in the database.

Specifically, referring to fig. 7, based on the embodiment shown in fig. 2, before step 104, the SQL file configuration method may further include:

in step 105, the target database is searched for whether a first SQL file identical to the plurality of second SQL files exists, and if a first SQL file identical to one or more of the second SQL files exists in the target database, the corresponding second SQL file is deleted.

In this step, before executing each second SQL file obtained in step 103, a target database may be searched for whether there is a first SQL file that is the same as the plurality of second SQL files, and if there is a first SQL file that is the same as one or more second SQL files in the target database, it indicates that the second SQL file has been executed before, and this time, it is not necessary to execute again, and the corresponding second SQL file may be deleted, so as to avoid repeatedly executing the SQL files.

The SQL file configuration method comprises the steps of obtaining the dependency relationship among all first SQL files in a target database, selecting at least one first SQL file in the first SQL files to generate an SQL file set based on a preset SQL file selection condition and the dependency relationship, replacing the file name of each SQL file in the SQL file set and the content of a preset position in the file content by a preset variable to generate a plurality of second SQL files, selecting an SQL file to be configured in the target database according to the preset SQL file selection condition, replacing the file name of the SQL file to be configured and the variable of the file content by the preset variable to generate a new SQL file, rapidly configuring the SQL file to be configured in the target database, and repeatedly configuring the SQL file by changing the preset variable, reducing the code and improving the efficiency of SQL file configuration.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Corresponding to the SQL file configuration method described in the foregoing embodiment, fig. 8 shows a structural block diagram of the SQL file configuration apparatus provided in the embodiment of the present application, and for convenience of description, only the relevant parts to the embodiment of the present application are shown.

Referring to fig. 8, the SQL file configuration apparatus in the embodiment of the present application may include a dependency relationship obtaining module 201, an SQL file set generating module 202, a variable replacing module 203, and an executing module 204.

The dependency relationship obtaining module 201 is configured to obtain a dependency relationship between each first structured query language SQL file in the target database;

the SQL file set generating module 202 is configured to select at least one first SQL file from the first SQL files based on a preset SQL file selection condition and the dependency relationship, and generate an SQL file set;

the variable replacing module 203 is configured to replace the file name of each first SQL file in the SQL file set and the content of a preset position in the file content with a preset variable, so as to generate a plurality of second SQL files; the preset variables comprise file name variables corresponding to file names and content variables corresponding to file contents;

the executing module 204 is configured to execute the plurality of second SQL files.

Referring to fig. 9, in some embodiments, based on the SQL file configuration apparatus shown in fig. 8, the dependency relationship obtaining module 201 may include an obtaining unit 2011 and a dependency relationship determining unit 2012.

The obtaining unit 2011 is configured to obtain annotation content in the file content of each first SQL file, where the annotation content records an SQL file on which a current SQL file depends;

a dependency relationship determining unit 2012, configured to determine a dependency relationship between the first SQL files according to the annotation content.

Referring to fig. 9, in some embodiments, based on the SQL file configuration apparatus shown in fig. 8, the dependency relationship obtaining module 201 may further include:

a directed acyclic graph generating unit 2013, configured to generate a directed acyclic graph according to a dependency relationship between the first SQL files;

and each node of the directed acyclic graph is the first SQL file.

Referring to fig. 9, in some embodiments, based on the SQL file configuration apparatus shown in fig. 8, the SQL file set generating module 202 may include a file determining unit 2021 and a file set generating unit 2022.

The file determining unit 2021 is configured to determine a first target SQL file in the first SQL file based on the preset SQL file selection condition and the dependency relationship;

the file set generating unit 2022 is configured to select at least one second target SQL file from the first SQL file based on the first target SQL file and the dependency relationship, and generate an SQL file set.

Optionally, the file set generating unit 2022 may specifically be configured to:

determining a second target SQL file with a dependency relationship with the first target SQL file according to the dependency relationship;

and generating the SQL file set according to the association sequence of the association relationship between the first target SQL file and each second target SQL file.

Referring to fig. 9, in some embodiments, based on the SQL file configuring apparatus shown in fig. 8, the execution module 204 may include an execution unit 2041 and a recording unit 2042.

The execution unit 2041 is configured to sequentially execute each second SQL file according to the association sequence;

the recording unit 2042 is configured to record each second SQL file after the execution of each second SQL file is completed.

Referring to fig. 9, in some embodiments, based on the SQL file configuring apparatus shown in fig. 8, the SQL file configuring apparatus may further include a deduplication module 205, and the deduplication module 205 may be configured to:

searching whether a first SQL file which is the same as the plurality of second SQL files exists in the database, and deleting the corresponding second SQL file under the condition that the first SQL file which is the same as one or more second SQL files exists in the database.

It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

An embodiment of the present application further provides a terminal device, and referring to fig. 10, the terminal device 300 may include: at least one processor 310, a memory 320, and a computer program stored in the memory 320 and operable on the at least one processor 310, wherein the processor 310, when executing the computer program, implements the steps of any of the above-mentioned method embodiments, such as the steps S101 to S104 in the embodiment shown in fig. 2. Alternatively, the processor 310, when executing the computer program, implements the functions of the modules/units in the above-described device embodiments, such as the functions of the modules 201 to 204 shown in fig. 8.

Illustratively, the computer program may be divided into one or more modules/units, which are stored in the memory 320 and executed by the processor 310 to accomplish the present application. The one or more modules/units may be a series of computer program segments capable of performing specific functions, which are used to describe the execution of the computer program in the terminal device 300.

Those skilled in the art will appreciate that fig. 10 is merely an example of a terminal device and is not limiting of terminal devices and may include more or fewer components than shown, or some components may be combined, or different components such as input output devices, network access devices, buses, etc.

The Processor 310 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 320 may be an internal storage unit of the terminal device, or may be an external storage device of the terminal device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like. The memory 320 is used for storing the computer programs and other programs and data required by the terminal device. The memory 320 may also be used to temporarily store data that has been output or is to be output.

The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, the buses in the figures of the present application are not limited to only one bus or one type of bus.

The SQL file configuration method provided by the embodiment of the present application may be applied to terminal devices such as a smart phone, a computer, a tablet computer, a notebook computer, a netbook, a Personal Digital Assistant (PDA), and the like, and the specific type of the terminal device is not limited in any way in the embodiment of the present application.

Take the terminal device as a computer as an example. Fig. 11 is a block diagram showing a partial structure of a computer provided in an embodiment of the present application. Referring to fig. 11, the computer includes: communication circuit 410, memory 420, input unit 430, display unit 440, audio circuit 450, wireless fidelity (WiFi) module 460, processor 470, and power supply 480. Those skilled in the art will appreciate that the computer architecture shown in FIG. 11 is not intended to be limiting of computers, and may include more or fewer components than those shown, or some components in combination, or a different arrangement of components.

The following describes each component of the computer in detail with reference to fig. 11:

the communication circuit 410 may be used for receiving and transmitting signals during the process of receiving and transmitting information or communicating, and in particular, for processing the received image samples transmitted by the image capturing device to the processor 470; in addition, the image acquisition instruction is sent to the image acquisition device. Typically, the communication circuit includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the communication circuit 410 may also communicate with networks and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), and the like.

The memory 420 may be used to store software programs and modules, and the processor 470 performs various functional applications of the computer and data processing by operating the software programs and modules stored in the memory 420. The memory 420 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the computer, etc. Further, the memory 420 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 430 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the computer. Specifically, the input unit 430 may include a touch panel 431 and other input devices 432. The touch panel 431, also called a touch screen, may collect touch operations of a user on or near the touch panel 431 (e.g., operations of the user on or near the touch panel 431 using any suitable object or accessory such as a finger or a stylus) and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 431 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts it to touch point coordinates, and sends the touch point coordinates to the processor 470, and can receive and execute commands sent from the processor 470. In addition, the touch panel 431 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 430 may include other input devices 432 in addition to the touch panel 431. In particular, other input devices 432 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 440 may be used to display information input by a user or information provided to the user and various menus of the computer. The Display unit 440 may include a Display panel 441, and optionally, the Display panel 441 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch panel 431 may cover the display panel 441, and when the touch panel 431 detects a touch operation thereon or nearby, the touch panel is transmitted to the processor 470 to determine the type of the touch event, and then the processor 470 provides a corresponding visual output on the display panel 441 according to the type of the touch event. Although in fig. 11, the touch panel 431 and the display panel 441 are two separate components to implement the input and output functions of the computer, in some embodiments, the touch panel 431 and the display panel 441 may be integrated to implement the input and output functions of the computer.

The audio circuit 450 may provide an audio interface between a user and a computer. The audio circuit 450 may transmit the received electrical signal converted from the audio data to a speaker, and convert the electrical signal into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 450 and converted into audio data, which is processed by the audio data output processor 470 and transmitted to, for example, another computer via the communication circuit 410, or the audio data is output to the memory 420 for further processing.

WiFi belongs to short distance wireless transmission technology, and the computer can help the user to send and receive e-mail, browse web page and access streaming media etc. through WiFi module 460, which provides wireless broadband internet access for the user. Although fig. 10 shows the WiFi module 460, it is understood that it does not belong to the essential constitution of the computer, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 470 is a control center of the computer, connects various parts of the entire computer using various interfaces and lines, performs various functions of the computer and processes data by operating or executing software programs and/or modules stored in the memory 420 and calling data stored in the memory 420, thereby monitoring the entire computer. Alternatively, processor 470 may include one or more processing units; preferably, the processor 470 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 470.

The computer also includes a power supply 480 (e.g., a battery) for powering the various components, and preferably, the power supply 480 is logically coupled to the processor 470 via a power management system that provides management of charging, discharging, and power consumption.

The embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program can implement the steps in the embodiments of the SQL file configuration method described above.

The embodiment of the application provides a computer program product, and when the computer program product runs on a mobile terminal, the steps in each embodiment of the SQL file configuration method can be realized when the mobile terminal executes the computer program product.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. A SQL file configuration method is characterized by comprising the following steps:

acquiring a dependency relationship between first SQL files in a target database;

replacing the file name of each SQL file in the SQL file set and the content of a preset position in the file content by a preset variable to generate a plurality of second SQL files; the preset variables comprise file name variables corresponding to file names and content variables corresponding to file contents;

and executing the plurality of second SQL files.

2. The SQL file configuration method according to claim 1, wherein the obtaining the dependency relationship between the first structured query language SQL files in the target database comprises:

obtaining the annotation content in the file content of each first SQL file, wherein the annotation content records the SQL file which the current SQL file depends on;

and determining the dependency relationship among the first SQL files according to the annotation content.

3. The SQL file configuration method according to claim 2, wherein the obtaining of the dependency relationship between the first structured query language SQL files in the target database further comprises:

and each node of the directed acyclic graph is the first SQL file.

4. The SQL file configuration method according to claim 1, wherein the selecting at least one of the first SQL files from the first SQL files based on a preset SQL file selection condition and the dependency relationship to generate an SQL file set comprises:

determining a first target SQL file in the first SQL file based on the preset SQL file selection condition and the dependency relationship;

and selecting at least one second target SQL file from the first SQL file based on the first target SQL file and the dependency relationship to generate an SQL file set.

5. The SQL file configuration method according to claim 4, wherein the selecting at least one second target SQL file among the first SQL files based on the first target SQL file and the dependency relationship to generate a SQL file set comprises:

6. The SQL file configuration method according to claim 5, wherein the executing the plurality of second SQL files comprises:

executing each second SQL file in sequence according to the association sequence;

and after the execution of each second SQL file is completed, recording each second SQL file.

7. The SQL file configuration method according to any of claims 1 to 6, wherein prior to the executing the plurality of second SQL files, the method further comprises:

searching whether a first SQL file which is the same as the plurality of second SQL files exists in the target database, and deleting the corresponding second SQL file under the condition that the first SQL file which is the same as one or more second SQL files exists in the target database.

8. An SQL file configuration apparatus, comprising:

9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.