CN111291226B - System and method for auditing design document table and database table - Google Patents
System and method for auditing design document table and database table Download PDFInfo
- Publication number
- CN111291226B CN111291226B CN202010103515.XA CN202010103515A CN111291226B CN 111291226 B CN111291226 B CN 111291226B CN 202010103515 A CN202010103515 A CN 202010103515A CN 111291226 B CN111291226 B CN 111291226B
- Authority
- CN
- China
- Prior art keywords
- database
- module
- xml document
- sub
- path
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
- G06F16/84—Mapping; Conversion
- G06F16/86—Mapping to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the technical field of computers, in particular to a system and a method for auditing a design document table and a database table. Compared with the prior art, the system for auditing the design document table and the database table comprises a configuration basic information module, an XML and database table structure analysis module and an audit report generation module which are connected in sequence; the configuration basic information module comprises a configuration XML document path sub-module and a configuration database access information sub-module, wherein the configuration XML document path sub-module is used for testing whether a document exists or not, and the configuration database access information sub-module is used for testing whether the document can be connected with a database or not. The invention compares and analyzes the design document table structure and the database table structure, quickly discovers the difference, saves manual inspection, improves the inspection efficiency and accuracy, and has good popularization value.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a system and a method for auditing a design document table and a database table.
Background
Software systems have been functioning in a wide range of operating environments for the past few decades. The number of industries that use software systems in everyday operations is limited, including manufacturing, financial, information service, medical service, and construction industries.
Version iterations are often performed during the software development process for developers, but during the software version iterations, the parts modified during the development process are not synchronized into the design document. When the software project is completed, the software end product is found to be very different from the prototype design. Particularly, in the data table, the problem is considered to be incomplete in the process of prototype design, which can lead to the continuous addition of fields or deletion of fields to the table of the database in the development process, and the table difference between the data table and the database in the prototype design is increased over time.
On the other hand, for the software maintenance phase, especially for software systems that have been running for years or decades, replacement by personnel of the software maintenance will result in increasingly difficult and costly software maintenance if the table structure in the database is inconsistent with the table structure in the document.
Please refer to CN201811084361.3, the patent name is a method for converting XML and relational database, which converts the table structure in the XML document into the table structure of the database, which is a tedious and time-consuming repetitive task, and how to use a computer program to replace the manual processing task is a urgent issue in the prior art.
Disclosure of Invention
The present invention is directed to the above-mentioned problems
The system for auditing the design document table and the database table has reasonable design, safety and applicability.
The invention further aims at providing a method for auditing a design document table and a database table with high practicability.
The technical scheme adopted for solving the technical problems is as follows:
a system for auditing a design document table and a database table comprises a configuration basic information module, an XML and database table structure analysis module and an audit report generation module which are connected in sequence;
the configuration basic information module comprises a configuration XML document path submodule and a configuration database access information submodule, wherein the configuration XML document path submodule is used for testing whether a document exists or not, and the configuration database access information submodule is used for testing whether the document can be connected with a database or not;
the analysis XML and database table structure module comprises a creation data field entity sub-module, an analysis XML document table structure sub-module, an analysis corresponding database table structure sub-module and a table structure auditing sub-module, wherein the creation data field entity sub-module is used for creating column structure entities of a table and using column names as unique identifiers to create column entities, the analysis XML document table structure sub-module is used for analyzing the XML document by using DOM4J, the analysis corresponding database table structure sub-module is used for analyzing the table in the database by using APIs (application program interface) in Java, and the table structure auditing sub-module is used for taking all table names from the two table structures to form a list only comprising the table names, and the table names are searched in the analysis XML document table structure sub-module and the analysis corresponding database table structure sub-module respectively;
the audit report generation module comprises a difference evaluation generation sub-module, a detailed audit report generation sub-module and a preview and download sub-module, wherein the difference evaluation generation sub-module is used for counting the generated audit result and giving the audit score, the detailed audit report generation sub-module is used for displaying the audit result in more detail on an audit result detail page and indicating the existing position and the missing position, and the preview and download sub-module is used for previewing and downloading information.
Further, in the configuration XML document path submodule, an XML document in the design file is on a local or remote server;
if the XML document is locally dragged to the working area or the path of the XML document is configured, the path of the XML document is configured to comprise a local path and a remote path;
if the XML file is a remote path, starting with the IP port of the host computer, defaulting to a local path, and after the path is configured, testing whether the XML file exists on the corresponding path;
the configuration database access information sub-module configures basic information of a database to be checked, comprises an IP port of data and access authorization information, and tests whether connection is established with the configured database.
Preferably, in the create data field entity sub-module, the entity field includes a column name, a column type, a length, a default value, whether a primary key is a foreign key, whether a null and an explanation are possible, and the attribute of the column is described in detail.
Further, the table structure sub-module analyzes the XML document by using DOM4J, and the table name, field type and length, default value, constraint condition and field description of each table in the analyzed XML document are generated, and corresponding column objects are generated, and the analyzed table objects are stored by using a Map set with the table name as a key and the columns as a list;
and analyzing the table structure sub-module in the corresponding database, obtaining the table name, the field type and the length of each table in the database, the default value, the constraint condition and the field description, generating a corresponding column object, and storing the analyzed table object by using a Map set which takes the table name as a key and the column as a list.
Further, the table structures take out the used table names from the two table structures respectively in the audit sub-module to form a list only containing the table names, take out one table name from the table name list of the XML document, go to the database list set to search, if the taken out table names cannot find out the matching in the database table name list, mark the difference of database table deletion;
if the table names can be matched, entering a column comparison link, and marking the rest tables in the database table name set as abnormal table deletion in the XML document;
if the table names are matched, the fields of the two tables are compared, including field names, field types, field lengths, default values, constraints and field description comparison, and if any item is not matched, the corresponding item is marked as not matched abnormal.
A method for auditing a design document table and a database table comprises the following steps,
1) Configuration basic information:
101 A) configuring an XML document path,
102 A configuration database access information);
2) Parsing XML and database table structure:
201 A data field entity is created and,
202 Parsing the table structure in the XML document,
203 Analyzing the table structure in the corresponding database,
204 Checking the table structure;
3) Generating an audit report:
301 A score for the difference is generated,
302 A detailed audit report is generated,
303 Preview and download).
Further, in step 101), the XML document in the design file is local or on a remote server, if the XML document is locally supported to be dragged to the workspace, or the path in which the XML document is located is configured, the path in which the XML document is configured includes a local path and a remote path;
if the XML document is a remote path, starting with an IP port of a host computer, defaulting to a local path, and testing whether the XML document exists on the corresponding path after the path is configured;
in step 102), configuring basic information of a database to be audited, including an IP port of data and access authorization information, and testing whether to establish a connection with the configured database.
Further, in step 201), a column structure entity of the creation table is defined according to the conventional database, and a column entity is created by using a column name as a unique identifier, wherein the entity field includes a column name, a column type, a length, a default value, whether the column is a primary key, whether the column can be empty or not, and a description is given in detail of the attribute of the column;
in step 202), the XML document is parsed by using DOM4J, firstly, the table name, field type and length, default value, constraint condition and field description of each table in the XML document are parsed, and corresponding column objects are generated, then, a Map set with the table name as a key and finally, the parsed table objects are stored by using the Map set with the table name as a list.
Further, in step 203), the self-contained API in Java is used to parse the table in the database, obtain the table name, field type and length, default value, constraint condition and field description of each table in the database, generate a corresponding column object, and finally store the parsed table object by using a Map set with the table name as a key and the column as a list;
step 204), firstly, respectively taking out the used table names from the two table structures to form a list only comprising the table names, taking out one table name from the table name list of the XML document, searching in the database list set, and marking the difference of database table deletion if the taken out table names cannot find matching in the database table name list;
if the table names can be matched, entering a column comparison link, and marking the rest tables in the database table name set as abnormal table deletion in the XML document;
if the table names are matched, the fields of the two tables are compared, including field names, field types, field lengths, default values, constraints and field description comparison, and if any item is not matched, the corresponding item is marked as not matched abnormal.
Further, in step 301), statistics is performed to generate a table auditing result, including the number of table differences and the difference duty ratio, the number of field differences and the duty ratio, and auditing scores are given;
in step 302), in the audit result detail page, the audit result, the table name with the difference, the field name and the type of the difference are displayed in more detail, and for the table with only one position, the table name and the field attribute are listed completely, and the position with the position and the position with the absence are indicated; preview and download in step 303).
Compared with the prior art, the method and the system for data migration of the collapse platform have the following outstanding beneficial effects:
(1) The invention compares and analyzes the design document table structure and the database table structure, and rapidly discovers the difference, saves manual inspection, and improves the inspection efficiency and accuracy.
(2) The method is beneficial to standardizing the change of the database table structure in the system development and maintenance process, and is convenient for project iteration development.
(3) The maintainability of the database is improved, and the modification of the table structure in the database in the project maintenance process is avoided without synchronizing the table structure into the design document, so that the maintenance difficulty of the software system is reduced, and the stability of the software system is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of the present invention.
Detailed Description
In order to provide a better understanding of the aspects of the present invention, the present invention will be described in further detail with reference to specific embodiments. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
A preferred embodiment is given below:
the system for auditing the design document table and the database table in the embodiment comprises a configuration basic information module, an XML and database table structure analysis module and an audit report generation module which are connected in sequence.
The configuration basic information module comprises a configuration XML document path submodule and a configuration database access information submodule, wherein the configuration XML document path submodule is used for testing whether a document exists or not, and the configuration database access information submodule is used for testing whether the document can be connected with a database or not;
the analysis XML and database table structure module comprises a creation data field entity sub-module, an analysis XML document table structure sub-module, an analysis corresponding database table structure sub-module and a table structure auditing sub-module, wherein the creation data field entity sub-module is used for creating column structure entities of a table and using column names as unique identifiers to create column entities, the analysis XML document table structure sub-module is used for analyzing the XML document by using DOM4J, the analysis corresponding database table structure sub-module is used for analyzing the table in the database by using an API (application program interface) in Java, and the table structure auditing sub-module is used for taking all table names from the two table structures to form a list only comprising the table names and searching in the analysis XML document table structure sub-module and the analysis corresponding database table structure sub-module respectively;
the audit report generation module comprises a difference evaluation generation sub-module, a detailed audit report generation sub-module and a preview and download sub-module, wherein the difference evaluation generation sub-module is used for counting and generating audit results and giving audit scores, the detailed audit report generation sub-module is used for displaying the audit results in more detail on an audit result detail page and indicating the existence position and the deletion position, and the preview and download sub-module is used for previewing and downloading information.
In the XML document path configuration sub-module, XML documents in the design file are on a local or remote server;
if the XML document is locally dragged to the working area or the path of the XML document is configured, the path of the XML document is configured to comprise a local path and a remote path;
if the XML file is a remote path, starting with the IP port of the host computer, defaulting to a local path, and after the path is configured, testing whether the XML file exists on the corresponding path;
the configuration database access information sub-module configures basic information of a database to be checked, comprises an IP port of data and access authorization information, and tests whether connection is established with the configured database.
The entity fields in the create data field entity sub-module include column name, column type, length, default value, primary key, foreign key, null and description, detailing the attributes of the column.
The parsing XML document table structure sub-module parses the XML document by using DOM4J, the table name, field type and length, default value, constraint condition and field description of each table in the parsed XML document are generated, corresponding column objects are generated, and the parsed table objects are stored by using a Map set with the table name as a key and the columns as a list;
and analyzing the table structure sub-module in the corresponding database, obtaining the table name, the field type and the length of each table in the database, the default value, the constraint condition and the field description, generating a corresponding column object, and storing the analyzed table object by using a Map set which takes the table name as a key and the column as a list.
The table structure carries out audit on the table names in the sub-module, respectively takes out the used table names from the two table structures to form a list only comprising the table names, takes out one table name from the table name list of the XML document, goes to the database list set for searching, and marks the difference of database table deletion if the taken out table names cannot find matching in the database table name list;
if the table names can be matched, entering a column comparison link, and marking the rest tables in the database table name set as abnormal table deletion in the XML document;
if the table names are matched, the fields of the two tables are compared, including field names, field types, field lengths, default values, constraints and field description comparison, and if any item is not matched, the corresponding item is marked as not matched abnormal.
As shown in fig. 1, the operation method based on the system comprises the following steps:
a method for auditing a design document table and a database table comprises the following steps,
1) Configuration basic information:
101 A) configuring an XML document path,
102 A configuration database access information);
2) Parsing XML and database table structure:
201 A data field entity is created and,
202 Parsing the table structure in the XML document,
203 Analyzing the table structure in the corresponding database,
204 Checking the table structure;
3) Generating an audit report:
301 A score for the difference is generated,
302 A detailed audit report is generated,
303 Preview and download).
In step 101), the XML document in the design file is local or on a remote server, if the XML document is locally supported to be dragged to a working area, or a path where the XML document is located is configured, the path where the XML document is configured comprises a local path and a remote path;
if the XML document is a remote path, starting with an IP port of a host computer, defaulting to a local path, and testing whether the XML document exists on the corresponding path after the path is configured;
in step 102), configuring basic information of a database to be audited, including an IP port of data and access authorization information, and testing whether to establish a connection with the configured database.
In step 201), a column structure entity of a creation table is defined according to a traditional database, and a column entity is created by taking a column name as a unique identifier, wherein an entity field comprises the column name, the column type, the length, a default value, whether the default value is a primary key, whether the default value can be null or not and whether the default value can be described or not, and the attribute of the column is described in detail;
in step 202), the XML document is parsed by using DOM4J, firstly, the table name, field type and length, default value, constraint condition and field description of each table in the XML document are parsed, and corresponding column objects are generated, then, a Map set with the table name as a key and finally, the parsed table objects are stored by using the Map set with the table name as a list.
In step 203), the self-contained API in Java is used to parse the table in the database, obtain the table name, field type and length, default value, constraint condition and field description of each table in the database, generate a corresponding column object, and finally store the parsed table object by using a Map set with the table name as a key and the column as a list;
step 204), firstly, respectively taking out the used table names from the two table structures to form a list only comprising the table names, taking out one table name from the table name list of the XML document, searching in the database list set, and marking the difference of database table deletion if the taken out table names cannot find matching in the database table name list;
if the table names can be matched, entering a column comparison link, and marking the rest tables in the database table name set as abnormal table deletion in the XML document;
if the table names are matched, the fields of the two tables are compared, including field names, field types, field lengths, default values, constraints and field description comparison, and if any item is not matched, the corresponding item is marked as not matched abnormal.
In step 301), a table auditing result is generated through statistics, wherein the table auditing result comprises the number of table differences and the difference duty ratio, the number of field differences and the duty ratio, and auditing scores are given;
in step 302), in the audit result detail page, the audit result, the table name with the difference, the field name and the type of the difference are displayed in more detail, and for the table with only one position, the table name and the field attribute are listed completely, and the position with the position and the position with the absence are indicated; preview and download in step 303).
The above-mentioned specific embodiments are merely specific examples of the present invention, and the scope of the present invention includes, but is not limited to, any suitable changes or substitutions made by those skilled in the art, which are included in the present invention, in accordance with the system and method claims of the present invention for auditing the design document table and the database table.
Although embodiments of the present invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made therein without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (10)
1. The system for auditing the design document table and the database table is characterized by comprising a configuration basic information module, an XML and database table structure analysis module and an audit report generation module which are connected in sequence;
the configuration basic information module comprises a configuration XML document path submodule and a configuration database access information submodule, wherein the configuration XML document path submodule is used for testing whether a document exists or not, and the configuration database access information submodule is used for testing whether the document can be connected with a database or not;
the analysis XML and database table structure module comprises a creation data field entity sub-module, an analysis XML document table structure sub-module, an analysis corresponding database table structure sub-module and a table structure auditing sub-module, wherein the creation data field entity sub-module is used for creating column structure entities of a table and using column names as unique identifiers to create column entities, the analysis XML document table structure sub-module is used for analyzing the XML document by using DOM4J, the analysis corresponding database table structure sub-module is used for analyzing the table in the database by using APIs (application program interface) in Java, and the table structure auditing sub-module is used for taking all table names from the two table structures to form a list only comprising the table names, and the table names are searched in the analysis XML document table structure sub-module and the analysis corresponding database table structure sub-module respectively;
the audit report generation module comprises a difference evaluation generation sub-module, a detailed audit report generation sub-module and a preview and download sub-module, wherein the difference evaluation generation sub-module is used for counting the generated audit result and giving the audit score, the detailed audit report generation sub-module is used for displaying the audit result in more detail on an audit result detail page and indicating the existing position and the missing position, and the preview and download sub-module is used for previewing and downloading information.
2. The system for auditing a design document table and a database table according to claim 1, wherein in the configuration XML document path sub-module, the XML document in the design document is on a local or remote server;
if the XML document is locally dragged to the working area or the path of the XML document is configured, the path of the XML document is configured to comprise a local path and a remote path;
if the XML file is a remote path, starting with the IP port of the host computer, defaulting to a local path, and after the path is configured, testing whether the XML file exists on the corresponding path;
the configuration database access information sub-module configures basic information of a database to be checked, comprises an IP port of data and access authorization information, and tests whether connection is established with the configured database.
3. The system for auditing a design document table and a database table according to claim 1, wherein the entity fields in the create data field entity sub-module include column name, column type, length, default value, primary key, foreign key, null and description, detailing the attributes of the column.
4. The system for auditing a design document table and a database table according to claim 1, wherein the parsing XML document table structure sub-module parses the XML document using DOM4J, parses table names, field types and lengths, default values, constraint conditions and field descriptions of each table in the XML document, generates corresponding column objects, and stores the parsed table objects using a Map set with table names as keys and columns as a list;
and analyzing the table structure sub-module in the corresponding database, obtaining the table name, the field type and the length of each table in the database, the default value, the constraint condition and the field description, generating a corresponding column object, and storing the analyzed table object by using a Map set which takes the table name as a key and the column as a list.
5. The system for auditing the design document table and the database table according to claim 1, wherein the table structure performs the auditing, and the table names used are respectively extracted from the two table structures in the nuclear module to form a list only containing the table names, one table name is extracted from the table name list of the XML document, the table names are removed from the database list set and are searched, and if the extracted table names cannot find a match in the database table name list, the difference of database table deletion is marked;
if the table names can be matched, entering a column comparison link, and marking the rest tables in the database table name set as abnormal table deletion in the XML document;
if the table names are matched, the fields of the two tables are compared, including field names, field types, field lengths, default values, constraints and field description comparison, and if any item is not matched, the corresponding item is marked as not matched abnormal.
6. A method for auditing a design document table and a database table, which is applied to the system for auditing the design document table and the database table according to any one of claims 1-5, and is divided into the following steps,
1) Configuration basic information:
101 A) configuring an XML document path,
102 A configuration database access information);
2) Parsing XML and database table structure:
201 A data field entity is created and,
202 Parsing the table structure in the XML document,
203 Analyzing the table structure in the corresponding database,
204 Checking the table structure;
3) Generating an audit report:
301 A score for the difference is generated,
302 A detailed audit report is generated,
303 Preview and download).
7. The method of auditing a design document table and a database table according to claim 6, characterized in that in step 101), the XML document in the design document is local or on a remote server, if the XML document is locally supported to be dragged to a workspace, or the path of the XML document is configured, the path of the XML document is configured to include a local path and a remote path;
if the XML document is a remote path, starting with an IP port of a host computer, defaulting to a local path, and testing whether the XML document exists on the corresponding path after the path is configured;
in step 102), configuring basic information of a database to be audited, including an IP port of data and access authorization information, and testing whether to establish a connection with the configured database.
8. The method for auditing a design document table and a database table according to claim 7, wherein in step 201), a column structure entity of the creation table is defined according to a conventional database, and a column entity is created with a column name as a unique identifier, and the entity field includes a column name, a column type, a length, a default value, whether a primary key, whether a null and a description can be made, and the attribute of the column is described in detail;
in step 202), the XML document is parsed by using DOM4J, firstly, the table name, field type and length, default value, constraint condition and field description of each table in the XML document are parsed, and corresponding column objects are generated, then, a Map set with the table name as a key and finally, the parsed table objects are stored by using the Map set with the table name as a list.
9. The method for auditing a design document table and a database table according to claim 8, wherein in step 203), the table in the database is parsed by using an API in Java, the table name, field type and length, default value, constraint condition and field description of each table in the database are obtained, and corresponding column objects are generated, and finally a Map set with the table name as a key and the columns as a list is used to store the parsed table objects;
step 204), firstly, respectively taking out the used table names from the two table structures to form a list only comprising the table names, taking out one table name from the table name list of the XML document, searching in the database list set, and marking the difference of database table deletion if the taken out table names cannot find matching in the database table name list;
if the table names can be matched, entering a column comparison link, and marking the rest tables in the database table name set as abnormal table deletion in the XML document;
if the table names are matched, the fields of the two tables are compared, including field names, field types, field lengths, default values, constraints and field description comparison, and if any item is not matched, the corresponding item is marked as not matched abnormal.
10. The method for auditing a design document table and a database table according to claim 9, wherein in step 301), a table auditing result is statistically generated, including a table difference number and a difference duty ratio, a field difference number and a duty ratio, and an auditing score is given;
in step 302), in the audit result detail page, the audit result, the table name with the difference, the field name and the type of the difference are displayed in more detail, and for the table with only one position, the table name and the field attribute are listed completely, and the position with the position and the position with the absence are indicated; preview and download in step 303).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010103515.XA CN111291226B (en) | 2020-02-20 | 2020-02-20 | System and method for auditing design document table and database table |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010103515.XA CN111291226B (en) | 2020-02-20 | 2020-02-20 | System and method for auditing design document table and database table |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111291226A CN111291226A (en) | 2020-06-16 |
| CN111291226B true CN111291226B (en) | 2023-08-11 |
Family
ID=71021791
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010103515.XA Active CN111291226B (en) | 2020-02-20 | 2020-02-20 | System and method for auditing design document table and database table |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111291226B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111752546A (en) * | 2020-06-30 | 2020-10-09 | 武汉虹信技术服务有限责任公司 | Excel-based database object design management platform, system and method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139296A (en) * | 2013-01-31 | 2013-06-05 | 中国人民解放军信息工程大学 | Binding method of security marking and data objects based on extensive markup language (XML) |
| CN105068805A (en) * | 2015-08-07 | 2015-11-18 | 北京思特奇信息技术股份有限公司 | Method and system for auditing data in data transplantation process |
| CN105278961A (en) * | 2015-10-28 | 2016-01-27 | 广州华多网络科技有限公司 | Method and system for generating database table structure document |
| CN106600302A (en) * | 2015-10-19 | 2017-04-26 | 玺阅信息科技（上海）有限公司 | Hadoop-based commodity recommendation system |
| CN108769103A (en) * | 2018-04-04 | 2018-11-06 | 卓望数码技术（深圳）有限公司 | A kind of control method and system for checking result displaying based on communication service data |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040024662A1 (en) * | 2002-08-02 | 2004-02-05 | David Gray | Equipment documentation management system, method, and software tools |
-
2020
- 2020-02-20 CN CN202010103515.XA patent/CN111291226B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139296A (en) * | 2013-01-31 | 2013-06-05 | 中国人民解放军信息工程大学 | Binding method of security marking and data objects based on extensive markup language (XML) |
| CN105068805A (en) * | 2015-08-07 | 2015-11-18 | 北京思特奇信息技术股份有限公司 | Method and system for auditing data in data transplantation process |
| CN106600302A (en) * | 2015-10-19 | 2017-04-26 | 玺阅信息科技（上海）有限公司 | Hadoop-based commodity recommendation system |
| CN105278961A (en) * | 2015-10-28 | 2016-01-27 | 广州华多网络科技有限公司 | Method and system for generating database table structure document |
| CN108769103A (en) * | 2018-04-04 | 2018-11-06 | 卓望数码技术（深圳）有限公司 | A kind of control method and system for checking result displaying based on communication service data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111291226A (en) | 2020-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP3842577B2 (en) | Structured document search method, structured document search apparatus and program | |
| He et al. | Transform-data-by-example (TDE) an extensible search engine for data transformations | |
| Nguyen et al. | Clone management for evolving software | |
| JP3842573B2 (en) | Structured document search method, structured document management apparatus and program | |
| US7509538B2 (en) | Systems and methods for automated classification and analysis of large volumes of test result data | |
| US9507848B1 (en) | Indexing and querying semi-structured data | |
| EP2527991B1 (en) | Analysis method, analysis device, and analysis program | |
| US20060048109A1 (en) | Enhanced compiled representation of transformation formats | |
| CN102073640B (en) | Method, system and server for testing structured query language (SQL) statements | |
| US20180121326A1 (en) | Provision of position data for query runtime errors | |
| US7792851B2 (en) | Mechanism for defining queries in terms of data objects | |
| US20120143893A1 (en) | Pattern Matching Framework for Log Analysis | |
| CN101739335A (en) | Recommended application evaluation system | |
| KR101505858B1 (en) | A templet-based online composing system for analyzing reports or views of big data by providing past templets of database tables and reference fields | |
| US20110208692A1 (en) | Generation of star schemas from snowflake schemas containing a large number of dimensions | |
| CN110989991B (en) | Method and system for detecting source code clone open source software in application program | |
| JP2006268118A (en) | Application environment checking device and method and program thereof | |
| CN111488314A (en) | Simulation log analysis method based on Python | |
| CN112256577A (en) | Configuration file difference checking method, device, equipment and storage medium | |
| CN111291226B (en) | System and method for auditing design document table and database table | |
| Chevalier et al. | Structural analysis and visualization of c++ code evolution using syntax trees | |
| CN116881512A (en) | Cross-system metadata blood-edge automatic analysis method | |
| US20180060404A1 (en) | Schema abstraction in data ecosystems | |
| JP2003281149A (en) | Method of setting access right and system of structured document management | |
| Ishida et al. | Automatically Refactoring Application Transactions for Microservice-Oriented Architecture |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230718 Address after: 214125 1101, 1102, 1103, 1104, 1105, 1106, 1107 and 1108, No. 15, first financial street, Wuxi Economic Development Zone, Wuxi City, Jiangsu Province Applicant after: Chaozhou Zhuoshu Big Data Industry Development Co.,Ltd. Address before: Room 3110, S01 / F, Inspur building, 1036 Inspur Road, hi tech Zone, Jinan City, Shandong Province 250100 Applicant before: Shandong Aicheng Network Information Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |