CN109977104B - Data management method and device - Google Patents
Data management method and device Download PDFInfo
- Publication number
- CN109977104B CN109977104B CN201910259922.7A CN201910259922A CN109977104B CN 109977104 B CN109977104 B CN 109977104B CN 201910259922 A CN201910259922 A CN 201910259922A CN 109977104 B CN109977104 B CN 109977104B
- Authority
- CN
- China
- Prior art keywords
- database
- preset
- operation instruction
- flow meter
- analysis
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a data management method and device, and relates to the technical field of data management. The data management method comprises the following steps: receiving a front-end table, wherein the front-end table comprises input database operation instructions. And analyzing the front-end meter to obtain a flow meter which can be identified by a preset database, wherein the flow meter is used for indicating an operation instruction of the database. And writing the flow table into a preset database, wherein the database operation instruction is used for indicating the execution of target operation on the preset database. The method and the system realize that non-professional database personnel can manage and maintain the database, are simple and convenient to operate, and improve the efficiency of managing and maintaining the database.
Description
Technical Field
The invention relates to the technical field of data management, in particular to a data management method and device.
Background
Data management is very important work for many enterprises, but the management and maintenance of databases are relatively complex work and often need a system to learn Structured Query Language (SQL) to complete.
There are currently some software that simplifies data management, e.g., Navicat Premium 12, DataGrip, Sequel Pro, etc., but using these software requires having basic SQL syntax knowledge. And when a plurality of data tables are created and maintained in batch, complex SQL sentences need to be written for implementation.
Therefore, the prior art can not meet the management and maintenance requirements of non-professional database personnel, and has high operation difficulty and low efficiency.
Disclosure of Invention
The invention aims to provide a data management method and a data management device aiming at the defects in the prior art, so as to solve the problems that the prior art cannot meet the management and maintenance requirements of non-professional database personnel, and is high in operation difficulty and low in efficiency.
In order to achieve the above purpose, the embodiment of the present invention adopts the following technical solutions:
in a first aspect, an embodiment of the present invention provides a data management method, including: receiving a front-end table, wherein the front-end table comprises input database operation instructions. And analyzing the front-end meter to obtain a flow meter which can be identified by a preset database, wherein the flow meter is used for indicating an operation instruction of the database. And writing the flow table into a preset database, wherein the database operation instruction is used for indicating the execution of target operation on the preset database.
Optionally, parsing the front-end meter to obtain a flow meter recognizable by the preset database includes: analyzing a database operation instruction in the front-end table through an analysis table, and loading a flow meter which can be identified by a preset database, wherein the analysis table comprises: and mapping relation between the database operation instruction of the front-end table and the database operation instruction in the flow table.
Optionally, the front-end table includes a plurality of operation attributes, and different operation attributes of the database operation instruction are written into corresponding operation attribute positions in the front-end table; the analysis table comprises: and mapping relation between each operation attribute in the front end table and the operation attribute in the flow meter. Through the database operating instruction in the analysis table analysis front end table, load and preset the distinguishable water flow meter of database, include: and analyzing a plurality of operation attributes of the database operation instruction in the front-end table through the analysis table to obtain a plurality of operation attributes which can be identified by a preset database in the corresponding flow meter. And loading the flow meter which can be identified by the preset database according to a plurality of operation attributes which can be identified by the preset database.
Optionally, after the flow table is written into the preset database, identifying a target operation indicated by the obtained database operation instruction is further included. And executing target operation on the preset database.
Optionally, if the target operation includes a deletion operation, before the target operation is performed on the preset database, the method further includes updating the name of the file to be deleted into a renamed name according to a preset naming rule, and storing the current time information and the renamed name into the file to be deleted, where the database operation instruction includes an identifier of the file to be deleted. And if the preset duration is waited according to the current time information and the instruction of canceling the deletion operation is not received, deleting the file to be deleted.
In a second aspect, an embodiment of the present invention further provides a data management apparatus, including a receiving module, configured to receive a front-end table, where the front-end table includes an input database operation instruction. And the analysis module is used for analyzing the front-end meter and acquiring a flow meter which can be identified by a preset database, wherein the flow meter is used for indicating an operation instruction of the database. And the writing module is used for writing the flow table into a preset database, wherein the database operation instruction is used for indicating the execution of target operation on the preset database.
Optionally, the parsing module is specifically configured to parse a database operation instruction in the front-end table through a parsing table, and load a flow meter identifiable by a preset database, where the parsing table includes: and mapping relation between the database operation instruction of the front-end table and the database operation instruction in the flow table.
Optionally, the front-end table includes a plurality of operation attributes, and different operation attributes of the database operation instruction are written into corresponding operation attribute positions in the front-end table; the analysis table comprises: and mapping relation between each operation attribute in the front end table and the operation attribute in the flow meter. And the analysis module is specifically used for analyzing a plurality of operation attributes of the database operation instruction in the front-end table through the analysis table to obtain a plurality of operation attributes which can be identified by a preset database in the corresponding flow meter. And loading the flow meter which can be identified by the preset database according to a plurality of operation attributes which can be identified by the preset database.
Optionally, the apparatus further includes an execution module, configured to identify a target operation indicated by the get database operation instruction. And executing target operation on the preset database.
Optionally, if the target operation includes a deletion operation, the apparatus further includes a deletion module, configured to update a name of the file to be deleted into a renamed name according to a preset naming rule, and store the current time information and the renamed name into the file to be deleted, where the database operation instruction includes an identifier of the file to be deleted. And if the preset duration is waited according to the current time information and the instruction of canceling the deletion operation is not received, deleting the file to be deleted.
The invention has the beneficial effects that: the method comprises the steps of receiving a front-end table comprising input database operation instructions, wherein the database operation instructions in the front-end table are visual instructions and can be filled without learning SQL language. And analyzing the front-end meter, acquiring a flow meter which can be identified by the preset database, and indicating the preset database to execute target operation by using the flow meter. The method and the system realize that non-professional database personnel can manage and maintain the database, are simple and convenient to operate, and improve the efficiency of managing and maintaining the database.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a schematic view of an application scenario of a data management method provided in the present application;
fig. 2 is a schematic flow chart of a data management method according to an embodiment of the present application;
FIG. 3 is a front end representation provided in accordance with an embodiment of the present application;
fig. 4 is a schematic diagram of a mapping relationship of an analysis table according to an embodiment of the present application;
FIG. 5 is a representation of a pipeline provided in accordance with an embodiment of the present application;
fig. 6 is a schematic flowchart of a data management method according to another embodiment of the present application;
fig. 7 is a schematic diagram of an analysis table mapping relationship of type analysis according to an embodiment of the present application;
fig. 8 is a schematic diagram of an analysis table mapping relationship of constraint analysis according to an embodiment of the present application;
FIG. 9 is a flowchart illustrating a data management method according to another embodiment of the present application;
FIG. 10 is a flowchart illustrating a data management method according to another embodiment of the present application;
fig. 11 is a schematic structural diagram of a data management apparatus according to an embodiment of the present application;
fig. 12 is a schematic structural diagram of a data management apparatus according to another embodiment of the present application;
fig. 13 is a schematic structural diagram of a data management apparatus according to another embodiment of the present application;
fig. 14 is a schematic structural diagram of an electronic device provided in the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention.
Fig. 1 is a schematic view of an application scenario of a data management method provided in the present application. As shown in fig. 1, an application scenario of the method may include: the system comprises a front-end table, a processing system, a database and a feedback system. The form of the front-end table may be an Excel table, a web page table, a table window in software, and the like, and the form is not limited thereto.
The front-end table, the processing system, the database and the feedback system can be positioned at the same terminal or different terminals. The type of the terminal may include a notebook computer, a desktop computer, a tablet computer, a server, a cloud server, and other devices capable of performing parsing management on data. For example, the front-end table may be filled in a notebook computer of the user, the processing system and the feedback system may be run on a server, the database may be run on a cloud, and the like; alternatively, the front-end table may be filled in on the user's desktop, and the processing system, the database, and the feedback system all run on the user's desktop, without limitation.
In one possible implementation, the front-end table may be generated by a front-end system, where the front-end system is an interactive system with a compact interface and easy operation for a user, such as an applet, a web page, a software interface, and the like; the front-end table may also be a form file directly filled by the user, such as an Excel file, which is not limited herein. After the user fills the front-end table, the front-end table is submitted to the processing system, for example, by clicking a one-key table building button of the front-end system, sending an Excel file to a preset address, and the like, after the processing system receives the front-end table, the processing system is triggered to read the table, analyze and process the table, and instruct the database to execute corresponding operations. It should be noted that the database may be one or a combination of commonly used databases such as MySQL, maridb, supercona Server, PostgreSQL, Microsoft Access, Microsoft SQL Server, Google Fusion Tables, FileMaker, Oracle database, Sybase, dBASE, Clipper, FoxPro, fosshub, etc., but is not limited thereto.
Fig. 2 is a schematic flow chart of a data management method according to an embodiment of the present application. The execution main body of the method can be a notebook computer, a desktop computer, a tablet computer, a server, a cloud server and other equipment capable of analyzing and managing data.
As shown in fig. 2, the method includes:
s101, receiving a front end table.
The front end table comprises input database operation instructions.
The database operation instructions filled in the front-end table of the application can be divided into different levels according to different types of users, for example, for general-level users without database knowledge, general-level database operation instructions can be used, for basic-level users with basic database knowledge, basic-level database operation instructions can be used, and for professional-level users with professional database management knowledge, professional-level database operation instructions can also be used.
In some embodiments, for general-purpose users, the database operation instructions in the front-end table are easy-to-understand visualization instructions, and the visualization instructions can be represented by non-program statements. For example, the user may directly select the corresponding operation category from the menu, or fill in the operation category with preset characters, and complete the input of the database operation command according to other instruction information in the front-end table, but not limited thereto.
S102, analyzing the front-end meter to obtain the flow meter which can be identified by the preset database.
The flow table is used for indicating database operation instructions.
In some embodiments, the database operation command in the front-end table is parsed into a database operation command recognizable by the preset database, and the flow table is used for indicating the database operation command recognizable by the preset database.
S103, writing the flow table into a preset database.
The database operation instruction is used for indicating the execution of target operation on a preset database.
In one possible implementation, the preset database parses and identifies the database operation command that is recognizable by the preset database and indicated by the flow chart, and executes the target operation corresponding to the database operation command.
In this embodiment, the front-end table including the input database operation instruction is received, where the database operation instruction in the front-end table is a visual instruction and can be filled without learning the SQL language. And analyzing the front-end meter, acquiring a flow meter which can be identified by the preset database, and indicating the preset database to execute target operation by using the flow meter. The method and the system realize that non-professional database personnel can manage and maintain the database, are simple and convenient to operate, and improve the efficiency of managing and maintaining the database.
Optionally, parsing the front-end meter to obtain a flow meter recognizable by the preset database includes: analyzing a database operation instruction in the front-end table through an analysis table, and loading a flow meter which can be identified by a preset database, wherein the analysis table comprises: and mapping relation between the database operation instruction of the front-end table and the database operation instruction in the flow table.
Fig. 3 is a front-end representation provided in accordance with an embodiment of the present application.
In one possible implementation, as shown in fig. 3, the front-end table may include: operation type, table name, new table name, field name, new field name, field comment, data content, word number, size, etc., but not limited thereto.
For different database operation instructions, different operation categories need to be filled, and other items need to be filled according to the types of the operation categories, for example, table building operation is performed, table building needs to be filled in the operation categories, table names are given in the table names, and other items are not filled; adding fields to the specified table, filling 'adding fields' in the operation category, filling the table name of the specified table in the 'table name' item, filling the field name specified in the table in the 'field name' item, and filling the related content of the field annotation in the 'field annotation' item if the field needs annotation. Meanwhile, in the item of 'field content', the data form stored in the field needs to be explained, for example, if the data is stored, the 'number' is filled in, and the 'character' is filled in, wherein when the 'number' is filled in, the items of 'integer or decimal' and 'number size' need to be filled in, and when the 'character' is filled in, the items of 'number of characters' need to be filled in.
Fig. 4 is a schematic diagram of an analysis table mapping relationship according to an embodiment of the present application, and fig. 5 is a flow chart representation diagram according to an embodiment of the present application.
In one possible implementation, as shown in fig. 3, 4 and 5, the flow table establishes a mapping relationship with the database operation instruction in the front-end table according to one item of meaning according to the resolution table.
Taking the mapping relation of the operation types as an example, when the database operation instruction in the front-end table indicates that the operation type is the modification table name, referring to the mapping relation diagram of fig. 4, the corresponding meaning is the modification table name, and at this time, the database operation instruction which can be identified by the preset database and corresponds to the modification table name is correspondingly loaded at the meaning position of the operation type in the flow meter.
In fig. 4, the analysis table is shown in a table form, but the type of the analysis table is not limited to this, and may be, for example, a corresponding algorithm, a preset rule, or the like.
Fig. 6 is a schematic flow chart of a data management method according to another embodiment of the present application.
Optionally, the front-end table includes a plurality of operation attributes, and different operation attributes of the database operation instruction are written into corresponding operation attribute positions in the front-end table; the analysis table comprises: and mapping relation between each operation attribute in the front end table and the operation attribute in the flow meter.
Each operation attribute of the front-end table corresponds to one analysis type, and a mapping relation is established between the corresponding analysis table and the corresponding operation attribute in the flow meter.
Correspondingly, as shown in fig. 6, the loading the flow meter identifiable by the preset database through analyzing the database operation instruction in the front-end table by the analysis table includes:
and S1021, analyzing a plurality of operation attributes of the database operation instruction in the front-end table through the analysis table, and acquiring a plurality of operation attributes which can be identified by a preset database in the corresponding flow meter.
In one possible implementation, since there are multiple operation attributes in the front-end table, each operation attribute corresponds to a different parsing rule. Therefore, the processing system can read the analysis table through the reading module, split the plurality of operation attributes according to the database operation instruction, for example, split the plurality of operation attributes into corresponding operation attributes through the naming standard module, the type analysis module, the constraint analysis module and the like, and then analyze the operation attributes according to the analysis table corresponding to the operation attributes to obtain a plurality of operation attributes which can be identified by the preset database in the corresponding flow water meter.
Fig. 7 is a schematic diagram of an analysis table mapping relationship of type analysis according to an embodiment of the present application, and fig. 8 is a schematic diagram of an analysis table mapping relationship of constraint analysis according to an embodiment of the present application.
For example, table building operation, field adding operation, checking operation of a user for specifying a table name and a field name, renaming the table name and the field name according to rules predefined by the user in advance, and analyzing through an analysis table corresponding to a naming specification; as shown in fig. 7, according to the "data content" in the front-end table and in combination with the items such as "number of words", "size", "integer or decimal", the type analysis table corresponding to the type analysis is used to perform analysis, and the field type and length meeting the requirements are obtained; as shown in fig. 8, the added field is analyzed by an analysis table corresponding to constraint analysis, but the present invention is not limited thereto.
And S1022, loading the flow meter which can be identified by the preset database according to a plurality of operation attributes which can be identified by the preset database.
In one possible implementation manner, the processing system loads a plurality of operation attributes which can be identified by a preset database in the acquired corresponding flow meter through the loading module to obtain the flow meter. The obtained flow meter form is shown in fig. 5, and the loaded flow meter includes an attribute name and a system value code corresponding to the attribute, such as an operation type code, a corresponding system value, and the like, which is not limited herein.
The operation type code is used to indicate different operation types in the flow meter, for example, the operation system value corresponding to the batch _ ID is 1052, and the operation type code corresponding to the operation _ type is 1000, then the flow meter can be shown as the following table:
| batch_ID | operation_type | …… |
| 1052 | 1000 | …… |
it should be noted that the flow table may further include other attributes and values corresponding to the attributes, for example, for an operation _ type item, other operations may also be included, such as an operation on a table, where 0000 may be used to represent a modified table name, 0001 may represent a modified table authority, 0002 may represent a modified table comment, 0003 may represent a deleted table, and 0004 may represent a created table; operations on fields can use 1000 to represent adding fields, 1001 to represent modifying field types, 1002 to represent modifying field names, 1003 to represent modifying field notes, 1004 to represent deleting fields; for the operation of the database, 2000 may be used to represent creation of a library, 2001 may be used to represent deletion of a library, 2003 may be used to represent a backup library, 2004 may be used to represent restoration of a backup library, and the like, but the present invention is not limited thereto.
Fig. 9 is a schematic flowchart of a data management method according to another embodiment of the present application.
Optionally, as shown in fig. 9, after the writing the running water table into the preset database, the method further includes:
and S104, identifying and acquiring the target operation indicated by the database operation instruction.
In a possible implementation manner, the preset database may monitor whether the flow meter is inserted into the preset database through a trigger, and when the trigger detects that the flow meter is inserted, the preset storage process may be called to send the flow meter to the preset storage process, where the preset storage process is a storage process with parameters, and is used to receive the parameters sent by the trigger, and the parameter content is data in the flow meter. And after receiving the parameters sent by the trigger in the preset storage process, analyzing the target operation indicated in the parameters to obtain the target operation type and data.
And S105, executing target operation on the preset database.
In a possible implementation manner, in the preset storage process, after the target operation type and the data are obtained, corresponding operations are performed on the database to complete the target operation.
Optionally, after the target operation is completed, the preset storage process acquires the state of the target operation, such as success or failure. And returning the target operation state and the corresponding state annotation to the flow water meter in the preset storage process, and writing the target operation state and the corresponding state annotation into a field corresponding to the operation state in the flow water meter.
In some embodiments, since the user cannot directly read the operation state written into the flow water meter or the user is difficult to understand, a feedback system may be further included, which is configured to analyze the operation state in the flow water meter and convert the operation state into a state prompt message that can be read by the target user according to different user levels, and display the state prompt message to the user, for example, for a general-purpose user, if the target operation is successfully executed, "success" is displayed, and if the target operation is failed, the "failure" is displayed, and a reason for the target operation failure is displayed.
Fig. 10 is a schematic flow chart of a data management method according to another embodiment of the present application.
Optionally, as shown in fig. 10, if the target operation includes a delete operation, before the target operation is performed on the preset database, the method further includes:
s201, updating the name of the file to be deleted into a renamed name according to a preset naming rule, and storing the current time information and the renamed name into the file to be deleted, wherein the database operation instruction comprises an identifier of the file to be deleted.
In some embodiments, the delete operation may include deleting a database, deleting a table. Firstly, the name of the file to be deleted needs to be updated to be a renamed name according to a preset naming rule, for example, for deleting a database, the naming rule can be that a suffix of ToDelDb is added after the name of the database; for deleting a table, the naming rule may be, but is not limited to, adding a "toDelTb" suffix after the "table name". And after renaming according to a preset naming rule is completed, storing the current time information and the renaming name into the file to be deleted.
It should be noted that the preset database locates the file to be deleted according to the identifier of the file to be deleted included in the database operation instruction, where the identifier of the file to be deleted may be a characteristic value, a file name, and the like of the file to be deleted, and is not limited herein.
S202, if the preset time length is waited according to the current time information and the command of canceling the deleting operation is not received, deleting the file to be deleted.
In some embodiments, the preset duration may be a user-defined time period, such as 48 hours, 7 days, a month, etc., without limitation.
Optionally, the delete operation may further include deleting the field, and when the delete operation is performed, a field delete data cache table and a field delete time table need to be created first, for example, the field delete data cache table may be as shown in the following table:
the field deletion schedule may be as follows:
after the creation is completed, the field with the same type as the field to be deleted is written in the field deletion data cache table, the naming rule is 'delete field name n _ sequence number', and the sequence number can be a self-increment sequence. And then writing a sequence number value and corresponding deletion time in the field deletion time table, wherein the deletion time can be determined according to the preset time length. And the field deletion data cache table and the field deletion time table establish a mapping relation through the sequence numbers. At this time, the field in the field deletion data cache table, which is the same as the type of the field to be deleted, is an empty field, the data in the field to be deleted is inserted into the corresponding empty field in the field deletion data cache table, and then the field to be deleted is deleted.
Optionally, before the time preset by the field deletion schedule is reached, the user may restore the deleted field according to the field deletion data cache table and the field deletion schedule through a preset instruction. And after the preset time of the field deleting time table is reached, the preset database clears the data in the corresponding field deleting data cache table.
Through the deletion operation, the deletion can be slowly realized, the data loss caused by the misoperation of a user is prevented, and the data safety is enhanced.
Optionally, the slow deletion may also be implemented by backing up the file to be deleted on the backup device. The file to be deleted may be backed up to a local or remote backup end, for example, a local hard disk, a backup server, a backup hard disk, a backup cloud disk, or the like, to generate a backup file. And after the backup is finished, deleting the file to be deleted, and if the instruction of canceling the deletion operation is not received after the preset time length, deleting the corresponding backup file, but not limited to this.
Fig. 11 is a schematic structural diagram of a data management device according to an embodiment of the present application.
As shown in fig. 11, the apparatus specifically includes:
the receiving module 301 is configured to receive a front-end table, where the front-end table includes an input database operation instruction.
And the analysis module 302 is configured to analyze the front-end table and obtain a flow meter recognizable by the preset database, where the flow meter is used to indicate an operation instruction of the database.
The writing module 303 is configured to write the flow table into a preset database, where the database operation instruction is used to instruct to execute a target operation on the preset database.
Optionally, the parsing module 302 is specifically configured to parse a database operation instruction in the front-end table through a parsing table, and load a flow meter identifiable by a preset database, where the parsing table includes: and mapping relation between the database operation instruction of the front-end table and the database operation instruction in the flow table.
Optionally, the front-end table includes a plurality of operation attributes, and different operation attributes of the database operation instruction are written into corresponding operation attribute positions in the front-end table; the analysis table comprises: and mapping relation between each operation attribute in the front end table and the operation attribute in the flow meter. The analysis module 301 is specifically configured to analyze a plurality of operation attributes of the database operation instruction in the front-end table through the analysis table, and obtain a plurality of operation attributes that can be identified by a preset database in the corresponding flow meter. And loading the flow meter which can be identified by the preset database according to a plurality of operation attributes which can be identified by the preset database.
Fig. 12 is a schematic structural diagram of a data management device according to another embodiment of the present application.
Optionally, as shown in fig. 12, an execution module 304 is further included for identifying a target operation indicated by the get database operation instruction. And executing target operation on the preset database.
Fig. 13 is a schematic structural diagram of a data management device according to another embodiment of the present application.
Optionally, as shown in fig. 13, if the target operation includes a delete operation, the method further includes a delete module 305, configured to update the name of the file to be deleted into a rename name according to a preset naming rule, and store the current time information and the rename name into the file to be deleted, where the database operation instruction includes an identifier of the file to be deleted. And if the preset duration is waited according to the current time information and the instruction of canceling the deletion operation is not received, deleting the file to be deleted.
The above-mentioned apparatus is used for executing the method provided by the foregoing embodiment, and the implementation principle and technical effect are similar, which are not described herein again.
These above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
The present application provides an electronic device, as shown in fig. 14, including:
a processor 401, a computer readable storage medium 402 and a bus 403, the computer readable storage medium 402 storing machine readable instructions executable by the processor 401, the processor 401 and the computer readable storage medium 402 communicating via the bus 403 when the electronic device is operating, the processor 401 executing the machine readable instructions to perform the steps of the data management method described above.
The memory 401 is used for storing programs, and the processor 402 calls the programs stored in the memory 401 to execute the above-mentioned method embodiments. The specific implementation and technical effects are similar, and are not described herein again.
Optionally, the invention also provides a program product, for example a computer-readable storage medium, comprising a program which, when being executed by a processor, is adapted to carry out the above-mentioned method embodiments.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. 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.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Claims (6)
1. A method for managing data, comprising:
receiving a front-end table, wherein the front-end table comprises an input database operation instruction;
analyzing the front-end meter to obtain a flow meter which can be identified by a preset database, wherein the flow meter is used for indicating the database operation instruction;
writing the flow table into the preset database, wherein the database operation instruction is used for indicating to execute target operation on the preset database;
the front end table is analyzed, and the flow meter which can be identified by a preset database is obtained, wherein the analysis comprises the following steps:
analyzing the database operation instruction in the front-end table through an analysis table, and loading the flow meter which can be identified by the preset database, wherein the analysis table comprises: mapping relation between the database operation instruction of the front-end table and the database operation instruction in the flow table;
the front end table comprises a plurality of operation attributes, and different operation attributes of the database operation instruction are written into corresponding operation attribute positions in the front end table; the resolution table includes: mapping relation between each operation attribute in the front end table and the operation attribute in the flow meter;
the database operation instruction in the front-end table is analyzed through the analysis table, and the flow meter which can be identified by the preset database is loaded, and the method comprises the following steps:
analyzing a plurality of operation attributes of the database operation instruction in the front-end table through an analysis table to obtain a plurality of operation attributes which can be identified corresponding to the preset database in the flow meter;
loading the flow meter which can be identified by the preset database according to a plurality of operation attributes which can be identified by the preset database; the loaded flow meter comprises: attribute names and corresponding system numerical codes;
the analyzing the plurality of operation attributes of the database operation instruction in the front-end table through the analysis table comprises:
and splitting the plurality of operation attributes according to the database operation instruction, and analyzing the split plurality of attribute operations through the corresponding analysis table.
2. The method of claim 1, wherein after writing the pipeline table to the predetermined database, further comprising:
identifying the target operation indicated by the obtained database operation instruction;
and executing the target operation on the preset database.
3. The method of claim 2, wherein if the target operation comprises a delete operation, before performing the target operation on the predetermined database, further comprising:
updating the name of the file to be deleted into a renamed name according to a preset naming rule, and storing the current time information and the renamed name into the file to be deleted, wherein the database operation instruction comprises an identifier of the file to be deleted;
and if the instruction for canceling the deleting operation is not received after waiting for the preset time length according to the current time information, deleting the file to be deleted.
4. A data management apparatus, comprising:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a front-end table, and the front-end table comprises an input database operation instruction;
the analysis module is used for analyzing the front-end meter and acquiring a flow meter which can be identified by a preset database, wherein the flow meter is used for indicating the database operation instruction;
the writing module is used for writing the flow table into the preset database, wherein the database operation instruction is used for indicating the execution of target operation on the preset database;
the analysis module is specifically used for analyzing the database operation instruction in the front-end table through an analysis table and loading the flow meter which can be identified by the preset database, wherein the analysis table comprises: mapping relation between the database operation instruction of the front-end table and the database operation instruction in the flow table;
the front end table comprises a plurality of operation attributes, and different operation attributes of the database operation instruction are written into corresponding operation attribute positions in the front end table; the resolution table includes: mapping relation between each operation attribute in the front end table and the operation attribute in the flow meter;
the analysis module is specifically configured to analyze a plurality of operation attributes of the database operation instruction in the front-end table through an analysis table, and obtain a plurality of operation attributes identifiable to the preset database in the flow meter;
loading the flow meter which can be identified by the preset database according to a plurality of operation attributes which can be identified by the preset database; the loaded flow meter comprises: attribute names and corresponding system numerical codes;
the analysis module is further specifically configured to split the plurality of operation attributes according to the database operation instruction, and analyze the split plurality of attribute operations through the corresponding analysis table.
5. The apparatus of claim 4, further comprising:
the execution module is used for identifying and acquiring the target operation indicated by the database operation instruction;
and executing the target operation on the preset database.
6. The apparatus of claim 5, wherein if the target operation comprises a delete operation, further comprising:
the deleting module is used for updating the name of the file to be deleted into a renamed name according to a preset naming rule and storing the current time information and the renamed name into the file to be deleted, wherein the database operation instruction comprises an identifier of the file to be deleted;
and if the instruction for canceling the deleting operation is not received after waiting for the preset time length according to the current time information, deleting the file to be deleted.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910259922.7A CN109977104B (en) | 2019-04-01 | 2019-04-01 | Data management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910259922.7A CN109977104B (en) | 2019-04-01 | 2019-04-01 | Data management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109977104A CN109977104A (en) | 2019-07-05 |
| CN109977104B true CN109977104B (en) | 2021-04-16 |
Family
ID=67082291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910259922.7A Active CN109977104B (en) | 2019-04-01 | 2019-04-01 | Data management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109977104B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111143355B (en) * | 2019-12-10 | 2023-04-25 | 北京字节跳动网络技术有限公司 | Data processing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103853803A (en) * | 2013-06-26 | 2014-06-11 | 携程计算机技术（上海）有限公司 | Database configuration file encapsulation method and operation method as well as operation device thereof |
| CN105224544A (en) * | 2014-05-30 | 2016-01-06 | 北大方正集团有限公司 | A kind of data editing method of database and device |
| CN107301186A (en) * | 2016-04-15 | 2017-10-27 | 中国移动通信集团重庆有限公司 | A kind of recognition methods of invalid data and device |
| CN108304463A (en) * | 2017-12-26 | 2018-07-20 | 中国广核电力股份有限公司 | A kind of data managing method and its database application component for database |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102520963B (en) * | 2011-12-26 | 2014-10-01 | 重庆新媒农信科技有限公司 | Method and system for realizing service logic processing based on strongly-typed relation mapping |
| US9087105B2 (en) * | 2012-10-04 | 2015-07-21 | Adobe Systems Incorporated | Rule-based extraction, transformation, and loading of data between disparate data sources |
| CN103473367B (en) * | 2013-09-27 | 2017-05-03 | 北京奇虎科技有限公司 | Method for using local application program in browser and web browser |
-
2019
- 2019-04-01 CN CN201910259922.7A patent/CN109977104B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103853803A (en) * | 2013-06-26 | 2014-06-11 | 携程计算机技术（上海）有限公司 | Database configuration file encapsulation method and operation method as well as operation device thereof |
| CN105224544A (en) * | 2014-05-30 | 2016-01-06 | 北大方正集团有限公司 | A kind of data editing method of database and device |
| CN107301186A (en) * | 2016-04-15 | 2017-10-27 | 中国移动通信集团重庆有限公司 | A kind of recognition methods of invalid data and device |
| CN108304463A (en) * | 2017-12-26 | 2018-07-20 | 中国广核电力股份有限公司 | A kind of data managing method and its database application component for database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109977104A (en) | 2019-07-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108536761B (en) | Report data query method and server | |
| JP2022141957A (en) | Metadata snapshot method and snap device thereof | |
| CN105144080B (en) | System for metadata management | |
| US8805777B2 (en) | Data record collapse and split functionality | |
| CN114282129A (en) | Information system page generation method, system, electronic equipment and storage medium | |
| US20230012642A1 (en) | Method and device for snapshotting metadata, and storage medium | |
| CN109977104B (en) | Data management method and device | |
| CN110555185A (en) | Page customization method and system based on PC client | |
| CN106503186A (en) | A kind of data managing method, client and system | |
| CN113010208A (en) | Version information generation method, version information generation device, version information generation equipment and storage medium | |
| CN113760600B (en) | Database backup method, database restoration method and related devices | |
| CN115329150A (en) | Method and device for generating search condition tree, electronic equipment and storage medium | |
| JP2018109898A (en) | Data migration system | |
| CN109992573B (en) | Method and system for realizing automatic monitoring of HDFS file occupancy rate | |
| CN114168119A (en) | Code file editing method and device, electronic equipment and storage medium | |
| CN113868138A (en) | Method, system, equipment and storage medium for acquiring test data | |
| CN113343649A (en) | File annotation method and device, storage medium and computing equipment | |
| CN112328668A (en) | Data visualization implementation method, device, equipment and storage medium | |
| US12056447B2 (en) | System and method for document branching | |
| CN110727677A (en) | Method and device for tracing blood relationship of table in data warehouse | |
| US11544451B2 (en) | System and method for maintaining links and revisions | |
| US11704094B2 (en) | Data integrity analysis tool | |
| CN118035210A (en) | Data dictionary management method, storage medium, device and product of database | |
| CN117932098A (en) | Service request processing method, device and storage medium for history chat record | |
| CN114780561A (en) | Entity attribute editing method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |