CN116991692A - Verification method based on database reading and writing - Google Patents
Verification method based on database reading and writing Download PDFInfo
- Publication number
- CN116991692A CN116991692A CN202311257041.4A CN202311257041A CN116991692A CN 116991692 A CN116991692 A CN 116991692A CN 202311257041 A CN202311257041 A CN 202311257041A CN 116991692 A CN116991692 A CN 116991692A
- Authority
- CN
- China
- Prior art keywords
- read
- database
- write
- result
- attribute
- 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.)
- Granted
Links
- 238000012795 verification Methods 0.000 title claims abstract description 65
- 238000000034 method Methods 0.000 title claims abstract description 28
- 238000013507 mapping Methods 0.000 claims abstract description 119
- 238000012216 screening Methods 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 9
- 238000013524 data verification Methods 0.000 claims description 8
- 238000001914 filtration Methods 0.000 claims description 3
- 238000004590 computer program Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 238000010606 normalization Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
-
- 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/2228—Indexing structures
-
- 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)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a verification method based on database reading and writing, and belongs to the technical field of information. The verification method based on database reading and writing comprises the steps of obtaining the reading and writing data attribute requirements of a database; obtaining a mapping template of a database according to the read-write data attribute requirements; obtaining a read-write result of the database by utilizing the read-write data attribute requirement according to the mapping template; and verifying the read-write result according to the mapping template to obtain a verification result. The application uses the mode of combining the relational database and the non-relational database in the use of the database, greatly improves the access speed while improving the storage capacity, verifies the read-write data by using the storage connection of the relational database and the non-relational database, and ensures the accuracy of the read-write of the database.
Description
Technical Field
The application belongs to the technical field of information, and particularly relates to a verification method based on database reading and writing.
Background
The main difference between relational and non-relational databases is the way data is stored. Relational data is naturally in table format and is therefore stored in rows and columns of a data table. The data tables can be cooperatively stored in association with each other and the data can be easily extracted, whereas the non-relational data is not suitable for being stored in the rows and columns of the data tables but is combined together in large blocks. The non-relational data are usually stored in a data set, just like a document, a key value pair or a graph structure, and the relational database and the non-relational database have respective characteristics and application scenes, so that the close combination of the relational database and the non-relational database brings new ideas for the development of the databases.
In the prior art, relational databases are focused on relationships, and non-relational databases are focused on storage. The database can not be stored in large quantity and in close relation, the accuracy of data reading and writing can not be guaranteed in the process of access, and the stability of the database after data reading and writing can not be guaranteed.
Disclosure of Invention
The application aims to: a database read-write based verification method is provided to solve the above problems in the prior art.
The technical scheme is as follows: a database read-write based verification method comprises the following steps:
s1, acquiring the read-write data attribute requirement of a database;
s2, obtaining a mapping template of the database according to the read-write data attribute requirements;
s3, obtaining a read-write result of the database by utilizing the read-write data attribute requirement according to the mapping template;
s4, verifying the read-write result according to the mapping template to obtain a verification result;
the read-write data attribute requirements include a read-write data attribute requirement.
Further, the obtaining the mapping template of the database according to the read-write data attribute requirement includes:
screening the read-write data by utilizing a relational database according to the read-write data attribute requirement to obtain a read-write data table set;
acquiring a data index corresponding to a read-write data table in the read-write data table set;
obtaining a non-relational database corresponding to the read-write data table in the read-write data table set according to the data index;
obtaining a mapping template of the database according to the non-relational database and the relational database;
the data index comprises attributes and corresponding relation addresses of data in a data table.
Further, the step of filtering the read-write data table set by using a relational database according to the read-write data attribute requirement includes:
screening out an initial read-write data table corresponding to the read-write data attribute requirement from a relational database according to the read-write data attribute requirement, and establishing an initial read-write data table set;
acquiring initial data table data attributes corresponding to each initial read-write data table in the initial read-write data table set;
judging whether the data attribute of the initial data table corresponds to the demand of the read-write data attribute, if so, obtaining a read-write data table set according to the initial read-write data table corresponding to the data attribute of the initial data table, otherwise, giving up processing.
Further, the obtaining the mapping template of the database according to the non-relational database and the relational database includes:
acquiring a non-relational address set corresponding to a read-write data table in the non-relational database;
acquiring the attribute type number of the data in the non-relational database as the number of the non-relational sub-databases;
obtaining an attribute mapping template of a database by using a relation address corresponding to the attribute of each data in a read-write data table and the number of non-relation sub-databases corresponding to the relation address;
acquiring non-relational addresses corresponding to the attribute data in the non-relational database;
obtaining an address mapping template of the database by utilizing the corresponding relation address and the corresponding non-relation address of the attribute of each data in the read-write data table;
and mapping templates according to the attributes of the database and the address of the database as mapping templates of the database.
Further, the obtaining the read-write result of the database according to the mapping template by using the read-write data attribute requirement includes:
screening a required data table from a relational database according to the read-write data attribute requirements of the data;
obtaining a non-relational sub-database in the non-relational database by using a mapping template according to the required data table;
and taking the read-write data of the required data table and the non-relational sub-database as the read-write result of the database.
Further, the verifying the read-write result according to the mapping template to obtain a verification result includes:
s4-1, acquiring read-write data attributes of the read-write result;
s4-2, judging whether the read-write data attribute corresponds to the read-write data attribute requirement, if so, executing S4-3, otherwise, returning to S3;
s4-3, obtaining an attribute mapping matching result of the read-write result according to the attribute mapping template corresponding to the mapping template;
s4-4, obtaining an address mapping matching result of the read-write result according to the address mapping template corresponding to the mapping template;
s4-5, obtaining a data verification result of the read-write result according to the attribute mapping matching result and the address mapping matching result;
s4-6, acquiring database address information and database index information corresponding to the read-write result as first database address information and first database index information respectively;
s4-7, obtaining a database verification result of the read-write result according to the first database address information and the first database index information;
s4-8, taking the data verification result and the database verification result according to the read-write result as the verification result of the read-write result.
Further, the obtaining the attribute mapping matching result of the read-write result according to the attribute mapping template corresponding to the mapping template includes:
acquiring a relation address corresponding to each attribute data in a read-write result and the number of non-relation sub-databases corresponding to the relation address as a first attribute mapping;
judging whether the first attribute mapping is corresponding to an attribute mapping template corresponding to the mapping template, if so, judging that the attribute mapping matching result of the read-write result is successful, otherwise, judging that the attribute mapping matching result of the read-write result is unsuccessful.
Further, the obtaining the address mapping matching result of the read-write result according to the address mapping template corresponding to the mapping template includes:
acquiring a relation address and a non-relation address corresponding to each attribute data in a read-write result as a first address mapping;
and judging whether the first address mapping is corresponding to an address mapping template corresponding to the mapping template, if so, the address mapping matching result of the read-write result is successful, otherwise, the address mapping matching result of the read-write result is unsuccessful.
Further, the data verification result obtaining the read-write result according to the attribute mapping matching result and the address mapping matching result includes:
and judging whether the attribute mapping matching result and the address mapping matching result are successful, if so, verifying the data of the read-write result, and if not, verifying the data of the read-write result.
Further, the obtaining the database verification result of the read-write result according to the first database address information and the first database index information includes:
acquiring database address information corresponding to the read-write data attribute requirement as second database address information;
judging whether the first database address information is the same as the second database address information, if so, determining that the database address information verification result is passed, and if not, determining that the database address information verification result is not passed;
acquiring database index information corresponding to the read-write data attribute requirement as second database index information;
judging whether the first database index information is the same as the second database index information, if so, determining that the database index information verification result is passed, and if not, determining that the database index information verification result is not passed;
judging whether the database address information verification result and the database index information verification result are verification passing or not, if so, judging that the database verification result of the read-write result is verification passing, otherwise, judging that the database verification result of the read-write result is not verification passing.
The beneficial effects are that: 1. the application uses the mode of combining the relational database and the non-relational database in the use of the database, greatly improves the access speed while improving the storage capacity, verifies the read-write data by using the storage connection of the relational database and the non-relational database, and ensures the accuracy of the read-write of the database.
2. The method and the device verify the state of the database after the completion of the reading and writing of the database, avoid the influence of the damage of the database caused by the data reading in the database on the accuracy of the subsequent data reading, and improve the stability of the database.
Drawings
Fig. 1 is a flowchart of a database read-write based verification method provided by the application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a more thorough understanding of the present application. It will be apparent, however, to one skilled in the art that the application may be practiced without one or more of these details. In other instances, well-known features have not been described in detail in order to avoid obscuring the application.
As shown in fig. 1, a database read-write based verification method includes:
s1, acquiring the read-write data attribute requirement of a database;
s2, obtaining a mapping template of the database according to the read-write data attribute requirements;
s3, obtaining a read-write result of the database by utilizing the read-write data attribute requirement according to the mapping template;
s4, verifying the read-write result according to the mapping template to obtain a verification result;
the step S2 specifically comprises the following steps:
s3-1, screening by utilizing a relational database according to the read-write data attribute requirements to obtain a read-write data table set;
s4-2, acquiring a data index corresponding to the read-write data table in the read-write data table set;
s5-3, obtaining a non-relational database corresponding to the read-write data table in the read-write data table set according to the data index;
s2-4, obtaining a mapping template of the database according to the non-relational database and the relational database;
the data index comprises attributes and corresponding relation addresses of data in a data table.
In this embodiment, the relational database may be any one of Oracle, DB2, postgreSQL, microsoft SQL Server, microsoft Access, mySQL, langchao K-DB, mariaDB, sqLite, etc., which is convenient and flexible to use: using the standard query language SQL allows users to access information from one product to another almost indiscriminately. The application software of the interface with the relational database has a similar program access mechanism, provides a large number of standard data access methods, has a simple structure and is easy to maintain: the table structure is used, and the formats are consistent; the database design and normalization process is also simple and easy to implement and easy to understand. However, in the normalization of relational databases, an entity may be divided into many parts and stored in different tables of the database, and thus, a query process of such complex information usually generates a large number of simple tables. In this case, the queries generated by accessing the information must deal with a large number of tables and complex code associations and poor read-write capability of the join operations. The non-relational database can be used for outputting the database and the table without depending on a specific model in real life, and is flexible and convenient. Therefore, the method of combining the relational database and the non-relational database is adopted in the application to improve the storage capacity and greatly improve the access speed.
The data index includes attribute information of data in the data table and address information of each attribute data.
The step S2-1 specifically comprises the following steps:
s2-1-1, screening an initial read-write data table corresponding to the read-write data attribute requirement from a relational database according to the read-write data attribute requirement, and establishing an initial read-write data table set;
s2-1-2, acquiring initial data table data attributes corresponding to each initial read-write data table in the initial read-write data table set;
s2-1-3, judging whether the data attribute of the initial data table corresponds to the demand of the read-write data attribute, if so, obtaining a read-write data table set according to the initial read-write data table corresponding to the data attribute of the initial data table, otherwise, discarding the processing.
In this embodiment, the step of performing filtering processing by using a relational database according to the read-write data attribute requirement to obtain the initial read-write data table set specifically includes: and screening the data table containing the data attribute corresponding to the data attribute requirement of the read-write data attribute requirement from the relational database according to the data attribute requirement of the read-write data attribute requirement to obtain an initial read-write data table set, and further screening the data table only containing the data attribute corresponding to the data attribute of the read-write data attribute requirement from the initial read-write data table set to serve as the read-write data table set.
The step S2-4 specifically comprises the following steps:
s2-4-1, acquiring a non-relational address set corresponding to a read-write data table in the non-relational database;
s2-4-2, acquiring the attribute type number of the data in the non-relational database as the number of the non-relational sub-databases;
s2-4-3, obtaining an attribute mapping template of the database by utilizing a relation address corresponding to the attribute of each data in the read-write data table and the number of non-relation sub-databases corresponding to the relation address;
s2-4-4, acquiring non-relational addresses corresponding to the attribute data in the non-relational database;
s2-4-5, obtaining an address mapping template of the database by utilizing the relation address corresponding to the attribute of each data in the read-write data table and the corresponding non-relation address;
s2-4-6, using the attribute mapping template of the database and the address mapping template of the database as the mapping templates of the database.
The step S3 specifically comprises the following steps:
s3-1, screening a required data table from a relational database according to the read-write data attribute requirements of the data;
s3-2, obtaining a non-relational sub-database in the non-relational database by using a mapping template according to the required data table;
s3-3, reading and writing data according to the required data table and the non-relational sub-database are used as reading and writing results of the database.
The step S4 specifically comprises the following steps:
s4-1, acquiring read-write data attributes of the read-write result;
s4-2, judging whether the read-write data attribute corresponds to the read-write data attribute requirement, if so, executing S4-3, otherwise, returning to S3;
s4-3, obtaining an attribute mapping matching result of the read-write result according to the attribute mapping template corresponding to the mapping template;
s4-4, obtaining an address mapping matching result of the read-write result according to the address mapping template corresponding to the mapping template;
s4-5, obtaining a data verification result of the read-write result according to the attribute mapping matching result and the address mapping matching result;
s4-6, acquiring database address information and database index information corresponding to the read-write result as first database address information and first database index information respectively;
s4-7, obtaining a database verification result of the read-write result according to the first database address information and the first database index information;
s4-8, taking the data verification result and the database verification result according to the read-write result as the verification result of the read-write result.
The step S4-3 specifically comprises the following steps:
s4-3-1, acquiring a relation address corresponding to each attribute data in a read-write result and the number of non-relation sub-databases corresponding to the relation address as a first attribute mapping;
s4-3-2, judging whether the first attribute mapping is corresponding to the attribute mapping template corresponding to the mapping template, if so, judging that the attribute mapping matching result of the read-write result is successful, otherwise, judging that the attribute mapping matching result of the read-write result is unsuccessful.
The step S4-4 specifically comprises the following steps:
s4-4-1, acquiring a relation address and a non-relation address corresponding to each attribute data in the read-write result as a first address mapping;
s4-4-2, judging whether the first address mapping is corresponding to the address mapping template corresponding to the mapping template, if so, the address mapping matching result of the read-write result is successful, otherwise, the address mapping matching result of the read-write result is unsuccessful.
The step S4-5 specifically comprises the following steps:
and judging whether the attribute mapping matching result and the address mapping matching result are successful, if so, verifying the data of the read-write result, and if not, verifying the data of the read-write result.
The step S4-7 specifically comprises the following steps:
s4-7-1, acquiring database address information corresponding to the read-write data attribute requirement as second database address information;
s4-7-2, judging whether the first database address information is the same as the second database address information, if so, determining that the database address information verification result is passed, and if not, determining that the database address information verification result is not passed;
s4-7-3, acquiring database index information corresponding to the read-write data attribute requirement as second database index information;
s4-7-4, judging whether the first database index information is the same as the second database index information, if so, determining that the database index information verification result is passed, and if not, determining that the database index information verification result is not passed;
s4-7-5, judging that the database address information verification result and the database index information verification result are both verification passing, if yes, the database verification result of the read-write result is verification passing, otherwise, the database verification result of the read-write result is verification failing.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical aspects of the present application and not for limiting the same, and although the present application has been described in detail with reference to the above embodiments, it should be understood by those of ordinary skill in the art that: modifications and equivalents may be made to the specific embodiments of the application without departing from the spirit and scope of the application, which is intended to be covered by the claims.
Claims (10)
1. A database read-write based verification method, comprising:
s1, acquiring the read-write data attribute requirement of a database;
s2, obtaining a mapping template of the database according to the read-write data attribute requirements;
s3, obtaining a read-write result of the database by utilizing the read-write data attribute requirement according to the mapping template;
and S4, verifying the read-write result according to the mapping template to obtain a verification result.
2. The method for verifying the database according to claim 1, wherein obtaining the mapping template of the database according to the read-write data attribute requirement comprises:
screening the read-write data by utilizing a relational database according to the read-write data attribute requirement to obtain a read-write data table set;
acquiring a data index corresponding to a read-write data table in the read-write data table set;
obtaining a non-relational database corresponding to the read-write data table in the read-write data table set according to the data index;
obtaining a mapping template of the database according to the non-relational database and the relational database;
the data index comprises attributes and corresponding relation addresses of data in a data table.
3. The database read-write based verification method according to claim 2, wherein the step of performing filtering processing by using a relational database according to the read-write data attribute requirement to obtain a read-write data table set includes:
screening out an initial read-write data table corresponding to the read-write data attribute requirement from a relational database according to the read-write data attribute requirement, and establishing an initial read-write data table set;
acquiring initial data table data attributes corresponding to each initial read-write data table in the initial read-write data table set;
judging whether the data attribute of the initial data table corresponds to the demand of the read-write data attribute, if so, obtaining a read-write data table set according to the initial read-write data table corresponding to the data attribute of the initial data table, otherwise, giving up processing.
4. The method for verifying a database read-write system according to claim 2, wherein obtaining the mapping template of the database from the non-relational database and the relational database comprises:
acquiring a non-relational address set corresponding to a read-write data table in the non-relational database;
acquiring the attribute type number of the data in the non-relational database as the number of the non-relational sub-databases;
obtaining an attribute mapping template of a database by using a relation address corresponding to the attribute of each data in a read-write data table and the number of non-relation sub-databases corresponding to the relation address;
acquiring non-relational addresses corresponding to the attribute data in the non-relational database;
obtaining an address mapping template of the database by utilizing the corresponding relation address and the corresponding non-relation address of the attribute of each data in the read-write data table;
and mapping templates according to the attributes of the database and the address of the database as mapping templates of the database.
5. The database read-write based verification method according to claim 4, wherein obtaining the read-write result of the database by using the read-write data attribute requirement according to the mapping template comprises:
screening a required data table from a relational database according to the read-write data attribute requirements of the data;
obtaining a non-relational sub-database in the non-relational database by using a mapping template according to the required data table;
and taking the read-write data of the required data table and the non-relational sub-database as the read-write result of the database.
6. A database read-write based verification method according to claim 3, wherein the verifying the read-write result according to the mapping template to obtain the verification result comprises:
s4-1, acquiring read-write data attributes of the read-write result;
s4-2, judging whether the read-write data attribute corresponds to the read-write data attribute requirement, if so, executing S4-3, otherwise, returning to S3;
s4-3, obtaining an attribute mapping matching result of the read-write result according to the attribute mapping template corresponding to the mapping template;
s4-4, obtaining an address mapping matching result of the read-write result according to the address mapping template corresponding to the mapping template;
s4-5, obtaining a data verification result of the read-write result according to the attribute mapping matching result and the address mapping matching result;
s4-6, acquiring database address information and database index information corresponding to the read-write result as first database address information and first database index information respectively;
s4-7, obtaining a database verification result of the read-write result according to the first database address information and the first database index information;
s4-8, taking the data verification result and the database verification result according to the read-write result as the verification result of the read-write result.
7. The database read-write based verification method according to claim 6, wherein obtaining the attribute mapping matching result of the read-write result according to the attribute mapping template corresponding to the mapping template comprises:
acquiring a relation address corresponding to each attribute data in a read-write result and the number of non-relation sub-databases corresponding to the relation address as a first attribute mapping;
judging whether the first attribute mapping is corresponding to an attribute mapping template corresponding to the mapping template, if so, judging that the attribute mapping matching result of the read-write result is successful, otherwise, judging that the attribute mapping matching result of the read-write result is unsuccessful.
8. The database read-write based verification method according to claim 7, wherein the obtaining the address mapping matching result of the read-write result according to the address mapping template corresponding to the mapping template includes:
acquiring a relation address and a non-relation address corresponding to each attribute data in a read-write result as a first address mapping;
and judging whether the first address mapping is corresponding to an address mapping template corresponding to the mapping template, if so, the address mapping matching result of the read-write result is successful, otherwise, the address mapping matching result of the read-write result is unsuccessful.
9. The database read-write based verification method according to claim 8, wherein the obtaining the data verification result of the read-write result according to the attribute map matching result and the address map matching result comprises:
and judging whether the attribute mapping matching result and the address mapping matching result are successful, if so, verifying the data of the read-write result, and if not, verifying the data of the read-write result.
10. The database read-write based authentication method according to claim 9, wherein the obtaining the database authentication result of the read-write result according to the first database address information and the first database index information includes:
acquiring database address information corresponding to the read-write data attribute requirement as second database address information;
judging whether the first database address information is the same as the second database address information, if so, determining that the database address information verification result is passed, and if not, determining that the database address information verification result is not passed;
acquiring database index information corresponding to the read-write data attribute requirement as second database index information;
judging whether the first database index information is the same as the second database index information, if so, determining that the database index information verification result is passed, and if not, determining that the database index information verification result is not passed;
judging whether the database address information verification result and the database index information verification result are verification passing or not, if so, judging that the database verification result of the read-write result is verification passing, otherwise, judging that the database verification result of the read-write result is not verification passing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311257041.4A CN116991692B (en) | 2023-09-27 | 2023-09-27 | Verification method based on database reading and writing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311257041.4A CN116991692B (en) | 2023-09-27 | 2023-09-27 | Verification method based on database reading and writing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116991692A true CN116991692A (en) | 2023-11-03 |
| CN116991692B CN116991692B (en) | 2024-02-09 |
Family
ID=88523611
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311257041.4A Active CN116991692B (en) | 2023-09-27 | 2023-09-27 | Verification method based on database reading and writing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116991692B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111414403A (en) * | 2020-03-20 | 2020-07-14 | 腾讯科技（深圳）有限公司 | Data access method and device and data storage method and device |
| CN111506559A (en) * | 2020-04-21 | 2020-08-07 | 北京同邦卓益科技有限公司 | Data storage method and device, electronic equipment and storage medium |
| CN112749147A (en) * | 2019-10-31 | 2021-05-04 | 北京京东尚科信息技术有限公司 | Method and device for merging and migrating data tables in database |
| CN113254455A (en) * | 2021-06-24 | 2021-08-13 | 中国平安人寿保险股份有限公司 | Dynamic configuration method and device of database, computer equipment and storage medium |
| CN114547055A (en) * | 2022-02-16 | 2022-05-27 | 浙江大华技术股份有限公司 | Data processing method and device |
| CN116204542A (en) * | 2023-04-28 | 2023-06-02 | 广东广宇科技发展有限公司 | Quick reading and writing processing method for database |
-
2023
- 2023-09-27 CN CN202311257041.4A patent/CN116991692B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112749147A (en) * | 2019-10-31 | 2021-05-04 | 北京京东尚科信息技术有限公司 | Method and device for merging and migrating data tables in database |
| CN111414403A (en) * | 2020-03-20 | 2020-07-14 | 腾讯科技（深圳）有限公司 | Data access method and device and data storage method and device |
| CN111506559A (en) * | 2020-04-21 | 2020-08-07 | 北京同邦卓益科技有限公司 | Data storage method and device, electronic equipment and storage medium |
| CN113254455A (en) * | 2021-06-24 | 2021-08-13 | 中国平安人寿保险股份有限公司 | Dynamic configuration method and device of database, computer equipment and storage medium |
| CN114547055A (en) * | 2022-02-16 | 2022-05-27 | 浙江大华技术股份有限公司 | Data processing method and device |
| CN116204542A (en) * | 2023-04-28 | 2023-06-02 | 广东广宇科技发展有限公司 | Quick reading and writing processing method for database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116991692B (en) | 2024-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110162516B (en) | Data management method and system based on mass data processing | |
| CN110837520A (en) | Data processing method, platform and system | |
| CN108334596B (en) | Massive relational data efficient parallel migration method for big data platform | |
| CN1976320B (en) | Data access control method and system | |
| CN108255852B (en) | SQL execution method and device | |
| WO2024183599A1 (en) | Data query method, and device, system, and storage medium | |
| CN113138990B (en) | Data blood margin construction and tracing method, device and equipment | |
| CN116991692B (en) | Verification method based on database reading and writing | |
| CN116204542B (en) | Quick reading and writing processing method for database | |
| US11841841B2 (en) | Stand in tables | |
| CN117421302A (en) | Data processing method and related equipment | |
| CN110704635B (en) | Method and device for converting triplet data in knowledge graph | |
| CN112783927A (en) | Database query method and system | |
| CN114490724B (en) | Method and device for processing database query statement | |
| CN114356454A (en) | Account checking data processing method, account checking data processing device, account checking data storage medium and program product | |
| CN110297842B (en) | Data comparison method, device, terminal and storage medium | |
| CN113902531A (en) | Automatic generation system, method, electronic device and storage medium for bid document | |
| CN113407378A (en) | Fragmentation information backup method and device for distributed database | |
| CN110675254A (en) | Intelligent financial transaction system based on big data | |
| CN111723104A (en) | Method, device and system for syntax analysis in data processing system | |
| CN110517010A (en) | A kind of data processing method, system and storage medium | |
| CN111930313B (en) | Method and device for data association access in host | |
| CN116049147A (en) | Method and device for generating multidimensional data model, readable medium and electronic equipment | |
| CN118193576A (en) | Connection table scanning method, device, equipment, storage medium and product | |
| CN114036346A (en) | Database maintenance method and device for three-dimensional visualization model of power system |
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 |