CN113094384B

CN113094384B - SQL file configuration method and device and terminal equipment

Info

Publication number: CN113094384B
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: 2024-07-02
Anticipated expiration: 2039-12-23
Also published as: CN113094384A

Abstract

The application is applicable to the technical field of databases, and provides an SQL file configuration method, an SQL file configuration device and terminal equipment, wherein the SQL file configuration method comprises the following steps: acquiring the dependency relationship among the first SQL files in the target database; selecting at least one first SQL file from the first SQL files based on preset SQL file selection conditions and dependency relationships 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 adopting a preset variable to generate a plurality of second SQL files; executing the plurality of second SQL files. The application can rapidly configure the SQL file to be configured in the database, and can repeatedly configure the SQL file by changing the preset variable, thereby reducing codes and improving the efficiency of configuring the SQL file.

Description

SQL file configuration method and device and terminal equipment

Technical Field

The application belongs to the technical field of databases, and particularly relates to a SQL file configuration method, a SQL file configuration device and terminal equipment.

Background

Conventional database version control tools can only control the version of an SQL (Structured Query Language ) file at the level of a database, but cannot flexibly configure the SQL file at a single database, and generally, in order to realize the function of flexibly configuring the SQL file at a single database, only a plurality of databases can be defined, which leads to a large redundancy amount of codes.

Disclosure of Invention

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

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 the SQL files of each first structured query language in the target database;

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;

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;

executing the plurality of second SQL files.

Illustratively, the first target SQL file is an SQL file that is independent of 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 relationship 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 depending on the first target SQL file and a first SQL file indirectly depending 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 sequence of the first target SQL file and each second target SQL file in the directed acyclic graph, so as to generate the SQL file set.

Optionally, the replacing the file name of each first SQL file in the SQL file set and the content of the preset location in the file content with the preset variable generates a plurality of second SQL files, including:

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

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

The file name of the SQL file includes version information and file name information, and the replacing the content of the preset position in the file name of each SQL file in the SQL file set with the file name variable specifically includes:

And replacing file name information in file names of the SQL files 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 SQL files of each first structured query language in the target database;

the SQL file set generation 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 relationships to generate an SQL file set;

The variable replacement 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 aspects when the processor executes the computer program.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program which, when executed by a processor, implements the SQL file configuration method according to any of the first aspects.

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

It will be appreciated that the advantages of the second to fifth aspects may be found in the relevant description of the first aspect, and are not described here again.

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

According to the method, the device and the system, the dependency relationship among the first SQL files in the target database is obtained, at least one first SQL file is selected from the first SQL files based on the preset SQL file selection conditions and the dependency relationship to generate an SQL file set, and then the file names of the SQL files and the contents of preset positions in file contents in the SQL file set are replaced by preset variables to generate a plurality of second SQL files, so that the SQL files needing to be configured can be selected from the target database through the preset SQL file selection conditions, then the variables of the file names and the file contents of the SQL files needing to be configured are replaced by preset variables to generate new SQL files, the SQL files needing to be configured can be configured quickly in the target database, the SQL files can be configured repeatedly by changing the preset variables, codes are reduced, and the efficiency of SQL file configuration 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 disclosure.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

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

FIG. 2 is a flow chart of a method for configuring SQL files according to an embodiment of the application;

FIG. 3 is a flow chart of a method for configuring SQL files according to an embodiment of the application;

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

FIG. 5 is a flow chart of a method for configuring SQL files according to an embodiment of the application;

FIG. 6 is a flow chart of a method for configuring SQL files according to an embodiment of the application;

FIG. 7 is a flow chart of a method for configuring SQL files according to an embodiment of the application;

FIG. 8 is a flow chart of an SQL file configuration device according to an embodiment of the application;

FIG. 9 is a schematic diagram of a SQL file configuration device according to an embodiment of the 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 applicable.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, 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 should 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 the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in the present description and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

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

Reference in the 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 application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

Based on the above problems, the embodiment of the application provides a method for configuring an SQL file, which comprises the steps of firstly obtaining the dependency between each SQL file in a target database, then selecting a required SQL file from each SQL file in the target database according to preset SQL file selection conditions and the dependency, replacing the file name of the selected SQL file and the content of a set position in file content by adopting preset variables, generating a new SQL file and executing, thereby configuring the SQL file required to be configured in the target database rapidly, and repeatedly configuring the SQL file by changing preset variables, thereby reducing codes and improving the efficiency of configuring the SQL file.

By way of example, the embodiments of the present application may be applied to an exemplary scenario as 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 same to the server 20; the server 20 may obtain the dependency relationship between the SQL files in the target database according to the SQL file configuration request, then select a required SQL file from the SQL files in the target database according to the preset SQL file selection condition and the dependency relationship, and replace the file name of the selected SQL file and the content of the set position in the file content with the preset variable, so as to 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 the like, and the embodiment of the present application does not limit the specific type of the terminal.

It should be noted that the above application scenario is taken as an exemplary illustration, and is not intended to limit the application scenario when the embodiment of the present application is implemented, and in fact, the embodiment of the present application may 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 be sent to the server 20 through the cloud.

In order to better understand the solution of the present application, the following description will clearly and completely describe the solution of the embodiment of the present application with reference to fig. 1, and it is obvious that the described embodiment is only a part of the embodiment of the present application, not all the embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

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

in step 101, the dependency relationships between each of the first structured query language SQL files in the target database are obtained.

The first SQL files in the target database may be all the SQL files stored in the target database, or may be SQL files in a certain set in the target database, which is not limited in the 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 previous "version" is version information, the version information may be ordered by dictionary, and a larger version number indicates a newer SQL file; the latter "desc" is file name information, ".sql" characterizes the format of an 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 in the file content of the SQL file, or other SQL files having a dependency relationship with the current SQL file may be recorded in other positions in the file content of the SQL file.

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

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

in step 1011, annotation content in file content of each of the first SQL files is acquired, where the annotation content records an SQL file on which the current SQL file depends.

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

Specifically, the above-described dependency relationship is described by taking two SQL files of "V20191020_ $ { table1}, SQL" and "V20191030_ $ { table1}, SQL" as examples. For "V20191030_ $ { table1}, SQL" SQL file, "V20191030" is the version number of the SQL file, for example, the date of generation of the SQL file may be used as the version number of the SQL file, and "table1" is the file name of the SQL file.

The file content of the "V20191030_ $ { table1}. SQL" SQL file can be recorded with the content of the "V20191030_ $ { table1}. SQL" SQL file in the form of comments, wherein the content of the "V20191020_ $ { table1}. SQL" SQL file is characterized. In 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, a dependency relationship between each of the first SQL files is determined according to the annotation content.

For an A1 file, an A2 file and an A3 file, if the A2 file depends on the A1 file and the A3 file depends on the A2 file, a dependency relationship exists among the A1 file, the A2 file and the A3 file; for the A1 file, the A2 file and the B1 file, if the A2 file depends on the A1 file, the A1 file and the A2 file do not depend on the B1 file, and the B1 file does not depend on the A1 file or the A2 file, a dependency relationship exists between the A1 file and the A2 file, and a dependency relationship does not exist between the B1 file and the A2 file.

Specifically, "V20191020_ $ { table1}, SQL" and "V20191030_ $ { table1}, SQL" have a dependency relationship between two SQL files, specifically "V20191030_ $ { table1}, SQL" SQL files depend on "V20191020_ $ { table1}, SQL" SQL files.

In addition, if the "V20191031_ $ { table1}. SQL" SQL file also exists, wherein the "V20191031_ $ { table1}. SQL" SQL file is recorded with the file content of the representation "V20191031_ $ { table1}. SQL" SQL file in the form of comments, the content of the "V20191030_ $ { table1}. SQL" SQL file is relied on, the "V20191020_ $ { table1}. SQL" SQL file, the "V20191030_ $ { table1}. SQL" SQL file and the "V20191031_ $ { table1} SQL" SQL file have a dependency relationship, in particular the "V20191031_ $ { table1}. SQL" SQL file is relied on the "V20191030_ $ { table1}. SQL" file, the "V20191030_ table1} { SQL" file is relied on the "V20191020 } table1}, the" SQL file is relied on.

Optionally, step 101 may further include:

Generating a directed acyclic graph according to the dependency relationship between the first SQL files;

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

Exemplary, for the "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, the resulting directed acyclic graph is shown in FIG. 4.

Where "V20191031_ $ { Table1}. SQL" SQL file depends on "V20191030_ $ { Table1}. SQL" SQL file, "V20191030_ $ { Table1}. SQL" SQL file depends on "V20191020_ $ { Table1}. SQL" SQL file, "V20191030_ $ { Table2}. SQL" SQL file depends on "V20191020_ $ { Table2}. SQL" SQL file, and "V20191030_ view. SQL" SQL file depends on "V20191020_ $ { Table1} SQL" SQL file and "V20191020_ { Table2}. SQL" SQL file.

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

The preset SQL file selection conditions 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 conditions and the dependency relationships, the server can select a required SQL file from the first SQL file to perform configuration of subsequent steps.

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

In step 1021, a first target SQL file is determined from the first SQL files based on the preset SQL file selection conditions and the dependency relationships.

The first target SQL file may be an SQL file that is not dependent on other first SQL files. For example, for five SQL files in FIG. 4, one or both of the "V20191020_ $ { Table1}, SQL" SQL file and the "V20191020_ $ { Table2}, SQL" SQL file may be used as the first target SQL file, specifically, which SQL file or two SQL files are used as the first target SQL file, and the preset SQL file selection conditions may be determined.

In one possible implementation manner, the preset SQL file selection condition may specifically be that an SQL file without dependency is specified, an SQL file with dependency relationship with the SQL file is determined according to the SQL file, and the SQL file with dependency relationship with the SQL file are used as the required SQL file. The preset SQL file selection conditions in the embodiment can be realized through regular expressions, and under the condition that the SQL files are more, the file name of each required SQL file is not required to be input, so that the realization is convenient.

In addition, under the condition that the number of SQL files is small, the file name of each required SQL file can be directly used as the preset SQL file selection condition, namely the required SQL file can be directly determined 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 files based on the first target SQL file and the dependency relationship, and an SQL file set is generated.

Specifically, an SQL file that depends on the first target SQL file may be used as the SQL file set. The above-mentioned 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 other first SQL files.

For example, step 1022 may include the steps of:

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

Taking the example shown in 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 comprise a "V20191030_ $ { table2}. SQL" SQL file;

If the first target SQL file is a "V20191020_ $ { table1}, SQL" SQL file and a V20191020_ $ { table2}, SQL "SQL file, the determined second target SQL file may include a" V20191030_ $ { table1}, SQL "SQL file, a" V20191031_ $ { table1}, SQL "SQL file, a" V20191030_ $ { table2}, SQL "SQL file and a" 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 depending on the first target SQL file and a first SQL file indirectly depending 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 of the directed acyclic graph. For example, a "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 of the directed acyclic graph as shown in FIG. 4.

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

Taking the first target SQL file as a V20191020_ $ { table1}. SQL "SQL file as an example, the SQL file set generated according to the association sequence can comprise an SQL file list, wherein the SQL file list sequentially comprises '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 ordered according to the topological order of the directed acyclic graph as shown in fig. 4, and the SQL file set may be generated according to the direction of the arrow.

In this embodiment, a first target SQL file is determined based on a preset SQL file selection condition and the above dependency relationship, and then a second target SQL file having a dependency relationship with the first target SQL file is selected, so as to generate an SQL file set, where the preset SQL file selection condition may be to 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 above dependency relationship, so as to obtain an SQL file set, which is convenient and simple to implement, and the configuration of the SQL file may be performed next by changing the preset SQL file selection condition, so as to improve the efficiency of the SQL file configuration.

In step 103, a preset variable is used to replace the file name of each SQL file in the SQL file set and the content of a preset position in the file content, so as to generate a plurality of second SQL files.

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:

In this 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 quickly generated.

For example, the file name of the SQL file may include version information and file name information, and the replacing the content of the preset location in the file name of each SQL file in the SQL file set with the file name variable may specifically be:

For example, the file name variable may be "table3", the content variable may be "XXX", for "V20191020_ $ { table1}. SQL" SQL file, "table3" is used to replace "V20191020_ $ { table1}. SQL" file name information "table1" in the file name of the SQL file, and "XXX" is used to replace "V20191020_ $ { table1}. SQL" file name "in the file content of the preset location of" V20191020_ $ { table3}. SQL "file.

For the SQL file of 'V20191030 _ $ { table1}. SQL', the file name variable 'table 3' is adopted to replace 'V20191030 _ $ { table1}. SQL' the file name information 'table 1' in the file name of the SQL file, the content variable 'XXX' is adopted to replace the content of the preset position in the file content of 'V20191030 _ $ { table1}. SQL' the file name of the obtained SQL file is 'V20191030 _ $ { table3}. SQL', and the content of the preset position is 'XXX'.

For the SQL file of 'V20191031 _ $ { table1}. SQL', the file name variable 'table 3' is adopted to replace 'V20191031 _ $ { table1}. SQL' the file name information 'table 1' in the file name of the SQL file, the content variable 'XXX' is adopted to replace the content of the preset position in the file content of 'V20191031 _ $ { table1}. SQL' the file name of the obtained SQL file is 'V20191031 _ $ { table3}. SQL', and the content of the preset position is 'XXX'.

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

After the steps 101 to 103 are performed to obtain the plurality of second SQL files, the plurality of SQL files may be executed.

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

in step 1041, each of the second SQL files is executed sequentially according to the association order.

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

For example, for the three second SQL files "V20191020_ $ { Table3}, SQL", "V20191020_ $ { Table3}, SQL" and "V20191020_ $ { Table3}, SQL" generated, the order in which the three second SQL files are executed in this step is in turn "V20191020_ $ { Table3}, SQL" SQL file, "V20191020_ $ { Table3}, SQL" SQL file and "V20191020_ $ { Table3}, SQL" SQL file.

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

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

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

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

In step 105, searching whether a first SQL file identical to the plurality of second SQL files exists in the target database, and deleting the corresponding second SQL file if the first SQL file identical to one or more second SQL files exists in the target database.

In this step, before executing each second SQL file obtained in step 103, whether a first SQL file identical to the plurality of second SQL files exists in the target database may be searched, if the first SQL file identical to one or more second SQL files exists in the target database, it is indicated that the second SQL file has been executed before, and this time, the second SQL file corresponding to the first SQL file does not need to be executed again, and may be deleted, so as to avoid repeated execution of the SQL files.

According to the SQL file configuration method, the dependency relationship among the first SQL files in the target database is obtained, at least one first SQL file is selected from the first SQL files based on the preset SQL file selection conditions and the dependency relationship to generate an SQL file set, and then the file names of the SQL files and the contents of preset positions in the file contents in the SQL file set are replaced by preset variables, so that a plurality of second SQL files are generated, the SQL files needing to be configured can be selected from the target database through the preset SQL file selection conditions, then the variables of the file names and the file contents of the SQL files needing to be configured are replaced by preset variables to generate new SQL files, the SQL files needing to be configured can be configured quickly in the target database, repeated configuration can be performed on the SQL files through changing the preset variables, codes can be reduced, and the efficiency of SQL file configuration can be improved.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.

Corresponding to the SQL file configuration method described in the above embodiments, fig. 8 shows a block diagram of the SQL file configuration device provided in the embodiment of the present application, and for convenience of explanation, only the portions related 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 acquisition module 201, an SQL file set generation module 202, a variable replacement module 203, and an execution module 204.

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

The SQL file set generation 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;

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

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

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

and 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 each first SQL file.

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

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;

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

Alternatively, the above-described 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 relation between the first target SQL file and each second target SQL file.

Referring to fig. 9, in some embodiments, based on the SQL file configuration 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 execute each of the second SQL files sequentially according to the association order;

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

Referring to fig. 9, in some embodiments, based on the SQL file configuration apparatus shown in fig. 8, the SQL file configuration apparatus may further include a deduplication module 205, where 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 when the first SQL file which is the same as one or the plurality of second SQL files exists in the database.

It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein.

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

The embodiment of the present application also provides a terminal device, 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 executable on the at least one processor 310, the processor 310, when executing the computer program, implementing the steps of any of the various method embodiments described above, such as steps S101 to S104 in the embodiment shown in fig. 2. Or the processor 310, when executing the computer program, performs 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.

By way of example, a computer program may be partitioned into one or more modules/units that are stored in memory 320 and executed by processor 310 to perform the present application. The one or more modules/units may be a series of computer program segments capable of performing specific functions for describing the execution of the computer program in the terminal device 300.

It will be appreciated by those skilled in the art that fig. 10 is merely an example of a terminal device and is not limiting of the terminal device and may include more or fewer components than shown, or may combine certain components, or different components, such as input-output devices, network access devices, buses, etc.

The Processor 310 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), off-the-shelf Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. 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 memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD), or the like. The memory 320 is used for storing the computer program 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 (Industry Standard Architecture, ISA) bus, an external device interconnect (PERIPHERAL COMPONENT, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or to one type of bus.

The SQL file configuration method provided by the embodiment of the application can be applied to terminal equipment such as smart phones, computers, tablet computers, notebook computers, netbooks, personal Digital Assistants (PDAs) and the like, and the embodiment of the application does not limit the specific type of the terminal equipment.

Taking the terminal device as a computer as an example. Fig. 11 is a block diagram showing a part of the structure of a computer provided with an embodiment of the present application. Referring to fig. 11, a computer includes: communication circuitry 410, memory 420, input unit 430, display unit 440, audio circuitry 450, wireless fidelity (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 limiting and that more or fewer components than shown may be included, or that certain components may be combined, or that different arrangements of components may be utilized.

The following describes the components 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 communication, in particular, after receiving the image sample transmitted by the image acquisition device, the signal is processed by the processor 470; in addition, an image acquisition instruction is sent to the image acquisition apparatus. Typically, the communication circuitry includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, LNA), a duplexer, and the like. In addition, the communication circuit 410 may also communicate with networks and other devices through wireless communication. The wireless communication may use any communication standard or protocol including, but not limited to, global System for Mobile communications (Global System of Mobile communication, GSM), general Packet Radio Service (GPRS), code division multiple Access (Code Division Multiple Access, CDMA), wideband code division multiple Access (Wideband Code Division Multiple Access, WCDMA), long term evolution (Long Term Evolution, LTE), email, short message Service (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 and data processing of the computer by executing 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 (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like; the storage data area may store data created according to the use of the computer (such as audio data, phonebooks, etc.), and the like. In addition, 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 to generate key signal inputs related to user settings and function control of the computer. In particular, the input unit 430 may include a touch panel 431 and other input devices 432. The touch panel 431, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 431 or thereabout using any suitable object or accessory such as a finger, a stylus, etc.), and drive the corresponding connection device according to a predetermined 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 azimuth 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 detection device and converts it into touch point coordinates, which are then sent to the processor 470 and can receive commands from the processor 470 and execute them. In addition, the touch panel 431 may be implemented in various types such as resistive, capacitive, infrared, and 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, mouse, joystick, etc.

The display unit 440 may be used to display information input by a user or information provided to the user as well as various menus of a 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 (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 operation 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 independent components to implement the input and input 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.

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

WiFi belongs to a short-distance wireless transmission technology, and a computer can help a user to send and receive emails, browse webpages, access streaming media and the like through the WiFi module 460, so that wireless broadband Internet access is provided for the user. Although fig. 10 shows a WiFi module 460, it is understood that it does not belong to the essential constitution of a computer, and can be omitted entirely as required within the scope of not changing the essence of the invention.

Processor 470 is the control center of the computer, and uses various interfaces and lines to connect the various parts of the entire computer, and by running or executing software programs and/or modules stored in memory 420, and invoking data stored in memory 420, performs various functions of the computer and processes the data, thereby performing overall monitoring of the computer. Optionally, the processor 470 may include one or more processing units; preferably, the processor 470 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily 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 can be logically connected to the processor 470 via a power management system so as to perform functions such as managing charge, discharge, and power consumption via the power management system.

Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements steps for implementing the embodiments of the above-described SQL file configuration method.

Embodiments of the present application provide a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps in the embodiments of the above-described SQL file configuration method when executed.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, 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 device/terminal apparatus, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

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 solution. 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 manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A method for configuring an SQL file, comprising:

acquiring the dependency relationship among the first SQL files in the target database;

Replacing the file names of all SQL files in the SQL file set and the contents of preset positions in the file contents by adopting preset variables 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;

Executing the plurality of second SQL files;

the step of 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 includes:

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

selecting at least one second target SQL file from the first SQL files based on the first target SQL file and the dependency relationship, and generating an SQL file set;

the step of selecting at least one second target SQL file from the first SQL files based on the first target SQL file and the dependency relationship to generate an SQL file set comprises the following steps:

2. The method for configuring SQL files according to claim 1, wherein the obtaining the dependency relationship between each first SQL file in the target database comprises:

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

And determining the dependency relationship between the first SQL files according to the annotation content.

3. The method for configuring SQL files according to claim 2, wherein the obtaining the dependency relationship between each first SQL file in the target database further comprises:

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

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

sequentially executing the second SQL files according to the association sequence;

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

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

Searching whether the first SQL files which are the same as the second SQL files exist in the target database, and deleting the corresponding second SQL files when the first SQL files which are the same as one or more second SQL files exist in the target database.

6. An SQL file configuration apparatus, comprising:

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

The SQL file set generation module comprises a file determination unit and a file set generation unit;

The file determining unit is used for determining 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 is used for selecting at least one second target SQL file from the first SQL files based on the first target SQL file and the dependency relationship to generate an SQL file set;

the file set generating unit is specifically configured to:

7. 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 5 when executing the computer program.

8. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method according to any one of claims 1 to 5.