CN111382142B - Database operation method, server and computer storage medium - Google Patents
Database operation method, server and computer storage medium Download PDFInfo
- Publication number
- CN111382142B CN111382142B CN202010143676.1A CN202010143676A CN111382142B CN 111382142 B CN111382142 B CN 111382142B CN 202010143676 A CN202010143676 A CN 202010143676A CN 111382142 B CN111382142 B CN 111382142B
- Authority
- CN
- China
- Prior art keywords
- database
- data
- cache
- data table
- client
- 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
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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2372—Updates performed during offline database operations
-
- 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/21—Design, administration or maintenance of databases
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- 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)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a database operation method, a server and a computer storage medium, which are applied to a data server, wherein the method comprises the following steps: receiving a database operation instruction output by a client; after a first session connection is established with a database, reading cache data from the database and storing the cache data in a preset cache space; the cache data at least comprises data of database operation instruction request operation; closing the first session connection, and establishing a second session connection with the client, so that the client executes the operation corresponding to the database operation instruction on the cached data. In the scheme, after receiving the operation instruction of the client, the data server reads the data needing to be operated from the database and stores the data serving as cache data in a preset cache space, so that the client can directly operate the data in the cache space without establishing session connection with the database, and the problem that other clients cannot operate in time due to long-time connection between the client and the database in the prior art is solved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a database operating method, a server, and a computer storage medium.
Background
With the development of society, a data management system composed of a data server and a client has been widely used in various fields in life. In the data management system, the data server is provided with a database for storing data to be managed, and the client can operate the data in the database by directly establishing session connection with the database, for example, can search, update or delete the data in the database.
In existing data management systems of this type, it is necessary to maintain a direct session connection between the client and the database for the duration of the client's operation of the data. However, the number of session connections that can be carried by the database at the same time is limited, which results in that when there are multiple clients that need to operate the database, each client needs to wait for the current operation of the client to end and release the session connection before operation, so that the waiting time of the client is longer and the user experience is worse.
Disclosure of Invention
Based on the shortcomings of the prior art, the application provides a database operation method, a server and a computer storage medium, so as to provide an offline database operation method.
A first aspect of the present application provides an operation method of a database, applied to a data server, where the operation method includes:
receiving a database operation instruction output by a client;
after a first session connection is established with the database, reading cache data from the database and storing the cache data in a preset cache space; wherein, the cache data at least comprises data of the database operation instruction request operation;
closing the first session connection, and establishing a second session connection with the client, so that the client executes the operation corresponding to the database operation instruction on the cached data.
Optionally, reading the cache data from the database and storing the cache data in a preset cache space, including:
determining a target data type according to the database operation instruction; wherein the target data type refers to a data type of data of the database operation instruction request operation;
creating a cached data object that matches the target data type;
and reading the cache data from the database and storing the cache data in a preset cache space by utilizing the cache data object.
Optionally, the database operation instruction includes a record query instruction;
wherein the reading the cache data from the database and saving the cache data comprises:
reading a first target data table from the database, and storing the first target data table as cache data; wherein the first target data table refers to a data table including records specified by the record query instruction.
Optionally, the database operation instruction includes a record deletion instruction;
wherein the reading the cache data from the database and saving the cache data comprises:
reading a second target data table from the database, and storing the second target data table as cache data; wherein the second target data table refers to a data table including a record specified by the record deletion instruction;
and after closing the first session connection and establishing a second session connection with the client, enabling the client to execute the operation corresponding to the database operation instruction on the cached data, the method further comprises the following steps:
and after the record designated by the record deleting instruction contained in the cache data is deleted, updating a second target data table in the database by using the deleted second target data table.
Optionally, each data table in the database is provided with a corresponding reading state, and the reading state of the data table is used for controlling whether the corresponding data table stored in the database is read or not;
wherein after the second target data table is read from the database and is stored as cache data, the method further comprises:
setting a read state of the second target data table to unreadable;
the updating the second target data table in the database with the deleted second target data table includes:
and updating the second target data table in the database by using the deleted second target data table, and setting the reading state of the second target data table in the database to be readable.
A second aspect of the present invention provides a server, the server being a data server, the data server comprising:
the receiving unit is used for receiving database operation instructions output by the client;
the first session unit is used for reading cache data from the database after a first session connection is established with the database, storing the cache data in a preset cache space and closing the first session connection after the cache data is stored; wherein, the cache data at least comprises data of the database operation instruction request operation;
and the second session unit is used for establishing second session connection with the client so that the client executes the operation corresponding to the database operation instruction on the cached data.
Optionally, when the first session unit reads the cache data from the database and stores the cache data in a preset cache space, the first session unit is specifically configured to:
determining a target data type according to the database operation instruction; wherein the target data type refers to a data type of data of the database operation instruction request operation;
creating a cached data object that matches the target data type;
and reading the cache data from the database and storing the cache data in a preset cache space by utilizing the cache data object.
Optionally, the database operation instruction includes a record query instruction;
the first session unit is specifically configured to, when reading the cached data from the database and storing the cached data:
reading a first target data table from the database, and storing the first target data table as cache data; wherein the first target data table refers to a data table including records specified by the record query instruction.
Optionally, the database operation instruction includes a record deletion instruction;
the first session unit is specifically configured to, when reading the cached data from the database and storing the cached data:
reading a second target data table from the database, and storing the second target data table as cache data; wherein the second target data table refers to a data table including a record specified by the record deletion instruction;
the data server further includes:
and the updating unit is used for updating the second target data table in the database by using the deleted second target data table after the record designated by the record deleting instruction contained in the cache data is deleted.
A third aspect of the present invention provides a computer storage medium storing a program which, when executed, is adapted to carry out the method of operating a database provided in any one of the first aspects of the present invention.
The application provides a database operation method, a server and a computer storage medium, which are applied to a data server, wherein the method comprises the following steps: receiving a database operation instruction output by a client; after a first session connection is established with a database, reading cache data from the database and storing the cache data in a preset cache space; the cache data at least comprises data of database operation instruction request operation; closing the first session connection, and establishing a second session connection with the client, so that the client executes the operation corresponding to the database operation instruction on the cached data. In the scheme, after receiving the operation instruction of the client, the data server reads the data needing to be operated from the database and stores the data serving as cache data in a preset cache space, so that the client can directly operate the data in the cache space without establishing session connection with the database, and the problem that other clients cannot operate in time due to long-time connection between the client and the database in the prior art is solved.
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 to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a method of operating a database according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a data server according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. 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.
An embodiment of the present application provides a method for operating a database, which is applied to a data server in a data management system, please refer to fig. 1, the method includes the following steps:
s101, receiving a database operation instruction output by a client.
First, briefly introducing a data management system:
the data management system comprises a client and a data server. In the prior art, a client is used for sending a database operation instruction to a data server, and after the data server receives the database operation instruction, session connection is established between the database and the client, so that the client directly performs corresponding operation on data in the database.
For example, the material management system of the enterprise may be considered as a data management system, where the warehouse information of various materials (including produced products, raw materials, etc.) of the enterprise is stored in the database, when the condition of the materials changes, for example, products are sold to the outside, the raw materials are taken out from the warehouse, and when new purchased raw materials are stored in the warehouse, a corresponding person is required to log in the client to operate the corresponding warehouse information in the database.
In connection with the above description, it may be appreciated that multiple clients may request to operate the database at the same time during the operation of the data management system. In the existing data management system, because the number of session connections that can be carried by the database at the same time is limited, the clients often cannot be connected to the clients immediately, but the clients that are not connected to the database need to be connected in sequence according to the request, and the clients that are not connected to the database need to wait for the operation of the clients that are connected to the database to finish and release the corresponding session connections, so that the corresponding operation is performed.
The aim of the embodiment is to enable the data management system to support more clients to operate on data simultaneously by providing an offline operating scheme of the database.
The operations on the data can be newly added, searched, deleted, changed and the like, the operations to be executed are different, and the corresponding database operation instructions are also different, specifically, the corresponding database operation instructions are a record new instruction, a record query instruction, a record delete instruction, a record change instruction and the like for the four operations.
S102, establishing a first session connection with a database.
In this embodiment, the session connection is used to refer to a session connection between the data server and the database.
Specifically, the data server may establish a session port, then send a connection request to the session port of the database through the session port, and after the database responds to the connection request, the data server and the database successfully establish the first session connection.
S103, reading the cache data from the database and storing the cache data in a preset cache space.
The cache data at least comprises data of a database operation instruction request operation.
Specifically, if the received database operation instruction is a record query instruction, the record query instruction is used to search and read a record meeting the query condition from the specified data table, and then the cached data is the whole data table specified by the record query instruction in the database. For example, the warehouse information database includes two data tables of product warehouse information and raw material warehouse information, and the record inquiry command designates to search warehouse information corresponding to some products in the product warehouse information, and then the cache data read in step S103 is the whole product warehouse information table.
If the received database operation instruction is a record deletion instruction, the record deletion instruction is used for deleting the record meeting the deletion condition in the appointed data table, and then the cached data is the whole data table appointed by the record deletion instruction.
If the received database operation instruction is a record change instruction, the record change instruction is used for changing the record meeting the change condition in the appointed data table, and then the cache data is the data table appointed by the record change instruction.
If the received database operation instruction is a record new instruction, the record new instruction is used for adding a new record in the appointed data table, and the cached data is the data table appointed by the record new instruction.
The specific implementation procedure of step S103 includes:
and determining a target data type according to the database operation instruction, wherein the target data type refers to the data type of the data of the operation requested by the database operation instruction. Specifically, the data types include, but are not limited to, integer, character, date, and big data types.
After the target data type is determined, a cache data object datarow matched with the target data type can be correspondingly created, a storage space is allocated for the cache data object in a preset cache space, finally, the cache data can be read from a database to copy the cache data to the pre-created cache data object, and after assignment is completed, the cache data is stored in the storage space corresponding to the cache data object.
S104, closing the first session connection and establishing a second session connection with the client.
The second session connection in this embodiment refers to a session connection between the data server and the client. The method for establishing the second session connection with the client is identical to the method for establishing the first session connection described above, and will not be described here again.
After session connection is established between the data server and the client, the client can directly operate the cache data stored in the cache space of the data server without establishing connection with the database.
And S105, after the operation of the client is finished, updating the operated data into a database.
It should be noted that, according to the database operation instruction, step S105 may be selectively performed.
Specifically, if the database operation instruction is a record query instruction, after the operation of the client is finished, the data after the operation is consistent with the original data, that is, the operation of the client on the data cannot cause the change of the original data, and in this case, the data after the operation may not be updated to the database.
If the database operation instruction is a record deletion instruction, a record new instruction or a record change instruction, then after the client operates on the cached data, compared with the original data, the data after operation will have a record deletion, change or increase, that is, the data after operation is different from the original data, in this case, step S105 needs to be executed to update the data after operation into the database.
Taking a record deleting instruction as an example, the client needs to delete a record of the data table a, after the data server caches the data table a, the client deletes the designated record from the data table a cached by the data server, however, cached data is easy to be lost in the running process of the system and cannot be permanently saved, so in order to persist the operation of the client into the database, step S105 needs to be executed, that is, with the data table a stored in the cache after the client deletes the corresponding record, the data table a originally stored in the database and not deleted the corresponding record is covered. The process of covering the original data table a of the database with the deleted data table a is the update execution process described in step S105.
In this embodiment, when a plurality of clients operate data, a case may occur in which a plurality of clients operate one data table at the same time. For example, when the client 1 deletes a record from the cached data table a, the client 2 may query another cached data table a for some records, which may easily cause a data error.
For example, the record to be deleted by the client 1 is exactly one record meeting the query condition of the client 2, and should be deleted normally, the client 2 will not find the record, however, after the above situation, since the deletion of the record in the data table a by the client 1 is not updated to the database in time, the client 2 can still find the deleted record from the data table a, which leads to the error in the subsequent processing.
Alternatively, in order to avoid the above problem, a corresponding read state may be set in advance for each data table in the database, and the read state may be set to be readable or unreadable by the data server. If the reading state of any one data table (marked as a data table A) is unreadable, the data server does not read the data table A in the database until the operation of the data table A cached in the cache space of the data server by the client ends, and after the data server updates the cached data table A to the database, the reading state of the data table A is set to be readable by the data server.
By the method, when any one client operates one data table in the cache, the data server refuses to read the same-name data table in the database again and provide the same-name data table for other clients to operate, so that errors caused by the fact that a plurality of clients operate one data table at the same time are effectively avoided.
The application provides an operation method of a database, which is applied to a data server, and comprises the following steps: receiving a database operation instruction output by a client; after a first session connection is established with a database, reading cache data from the database and storing the cache data in a preset cache space; the cache data at least comprises data of database operation instruction request operation; closing the first session connection, and establishing a second session connection with the client, so that the client executes the operation corresponding to the database operation instruction on the cached data. In the scheme, after receiving the operation instruction of the client, the data server reads the data needing to be operated from the database and stores the data serving as cache data in a preset cache space, so that the client can directly operate the data in the cache space without establishing session connection with the database, and the problem that other clients cannot operate in time due to long-time connection between the client and the database in the prior art is solved.
In combination with the operation method provided in the foregoing embodiments of the present application, the embodiments of the present application further provide a data server, please refer to fig. 2, the data server includes:
and the receiving unit 201 is configured to receive a database operation instruction output by the client.
The first session unit 202 is configured to read the buffered data from the database and store the buffered data in a preset buffer space after the first session connection is established with the database, and close the first session connection after the buffered data is stored.
The cache data at least comprises data of a database operation instruction request operation.
And the second session unit 203 is configured to establish a second session connection with the client, so that the client performs an operation corresponding to the database operation instruction on the cached data.
The first session unit 202 is specifically configured to, when reading the cache data from the database and storing the cache data in a preset cache space:
determining a target data type according to the database operation instruction; wherein the target data type refers to a data type of data of the database operation instruction request operation;
creating a cache data object matched with the target data type;
and reading the cache data from the database and storing the cache data in a preset cache space by utilizing the cache data object.
Optionally, the database operation instructions include record query instructions;
the first session unit 202 is specifically configured to, when reading the cached data from the database and storing the cached data:
and reading the first target data table from the database, and storing the first target data table as cache data.
Wherein the first target data table refers to a data table comprising records specified by the record query instruction.
Optionally, the database operation instructions include record deletion instructions;
the first session unit 202 is specifically configured to, when reading the cached data from the database and storing the cached data:
and reading the second target data table from the database, and storing the second target data table as cache data.
Wherein the second target data table refers to a data table including a record specified by the record deletion instruction.
The data server further includes:
and an updating unit 204, configured to update the second target data table in the database with the deleted second target data table after the record specified by the record deletion instruction included in the cache data is deleted.
Optionally, each data table in the database is provided with a corresponding reading state, and the reading state of the data table is used for controlling whether the corresponding data table stored in the database is read or not;
the data server further includes:
a setting unit 205, configured to set a read state of the second target data table to be unreadable after the first session unit reads the second target data table; the second target data table refers to a data table specified by the record deletion instruction.
After the updating unit 204 updates the second target data table in the database with the deleted second target data table, the setting unit 205 is configured to set the read status of the second target data table in the database to be readable.
The specific working principle of the data server provided in any embodiment of the present application may refer to the operation method of the database provided in any embodiment of the present application, which is not described herein again.
The application provides a data server, a receiving unit 201 receives a database operation instruction output by a client; after the first session unit 202 establishes a first session connection with the database, reading the cache data from the database and storing the cache data in a preset cache space; the cache data at least comprises data of database operation instruction request operation; after closing the first session connection, the second session unit 203 establishes a second session connection with the client, so that the client executes an operation corresponding to the database operation instruction on the cached data. In the scheme, after receiving the operation instruction of the client, the data server reads the data needing to be operated from the database and stores the data serving as cache data in a preset cache space, so that the client can directly operate the data in the cache space without establishing session connection with the database, and the problem that other clients cannot operate in time due to long-time connection between the client and the database in the prior art is solved.
The embodiment of the application also provides a computer storage medium, which is characterized by being used for storing a program, and when the program is executed, the program is used for realizing the operation method of the database in any embodiment of the application.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
It should be noted that the terms "first," "second," and the like herein are merely used for distinguishing between different servers, modules, or units and not for limiting the order or interdependence of the functions performed by such servers, modules, or units.
Those skilled in the art can make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. A method of operating a database, for application to a data server, the method comprising:
receiving a database operation instruction output by a client;
after a first session connection is established with the database, reading cache data from the database and storing the cache data in a preset cache space; wherein, the cache data at least comprises data of the database operation instruction request operation;
closing the first session connection, and establishing a second session connection with the client so that the client executes the operation corresponding to the database operation instruction on the cached data;
when the database operation instruction includes a record deletion instruction:
the reading the cache data from the database and storing the cache data comprises the following steps:
reading a second target data table from the database, and storing the second target data table as cache data; wherein the second target data table refers to a data table including a record specified by the record deletion instruction;
and after closing the first session connection and establishing a second session connection with the client, enabling the client to execute the operation corresponding to the database operation instruction on the cached data, the method further comprises the following steps:
and after the record designated by the record deleting instruction contained in the cache data is deleted by the client, covering a second target data table in the database by the second target data table deleted in the cache space.
2. The method of claim 1, wherein reading cache data from the database and saving the cache data in a preset cache space comprises:
determining a target data type according to the database operation instruction; wherein the target data type refers to a data type of data of the database operation instruction request operation;
creating a cached data object that matches the target data type;
and reading the cache data from the database and storing the cache data in a preset cache space by utilizing the cache data object.
3. The method of operation of claim 1, wherein the database operation instructions comprise record query instructions;
wherein the reading the cache data from the database and saving the cache data comprises:
reading a first target data table from the database, and storing the first target data table as cache data; wherein the first target data table refers to a data table including records specified by the record query instruction.
4. The method of claim 1, wherein each data table in the database is provided with a corresponding read status for controlling whether the corresponding data table stored in the database is read;
wherein after the second target data table is read from the database and is stored as cache data, the method further comprises:
setting a read state of the second target data table to unreadable;
the covering the second target data table in the database with the deleted second target data table in the cache space includes:
and covering a second target data table in the database by the deleted second target data table in the cache space, and setting the reading state of the second target data table in the database to be readable.
5. A server, wherein the server is a data server, the data server comprising:
the receiving unit is used for receiving database operation instructions output by the client;
the first session unit is used for reading cache data from the database after a first session connection is established with the database, storing the cache data in a preset cache space and closing the first session connection after the cache data is stored; wherein, the cache data at least comprises data of the database operation instruction request operation;
the second session unit is used for establishing second session connection with the client so that the client executes the operation corresponding to the database operation instruction on the cache data;
when the database operation instruction includes a record deletion instruction:
the first session unit is specifically configured to, when reading the cached data from the database and storing the cached data:
reading a second target data table from the database, and storing the second target data table as cache data; wherein the second target data table refers to a data table including a record specified by the record deletion instruction;
the data server further includes:
and the updating unit is used for covering a second target data table in the database by the second target data table deleted in the cache space after the record designated by the record deletion instruction contained in the cache data is deleted by the client.
6. The server according to claim 5, wherein when the first session unit reads the cache data from the database and stores the cache data in a preset cache space, the first session unit is specifically configured to:
determining a target data type according to the database operation instruction; wherein the target data type refers to a data type of data of the database operation instruction request operation;
creating a cached data object that matches the target data type;
and reading the cache data from the database and storing the cache data in a preset cache space by utilizing the cache data object.
7. The server of claim 5, wherein the database operation instructions comprise record query instructions;
the first session unit is specifically configured to, when reading the cached data from the database and storing the cached data:
reading a first target data table from the database, and storing the first target data table as cache data; wherein the first target data table refers to a data table including records specified by the record query instruction.
8. A computer storage medium storing a program which, when executed, is adapted to carry out the method of operation of a database as claimed in any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010143676.1A CN111382142B (en) | 2020-03-04 | 2020-03-04 | Database operation method, server and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010143676.1A CN111382142B (en) | 2020-03-04 | 2020-03-04 | Database operation method, server and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111382142A CN111382142A (en) | 2020-07-07 |
| CN111382142B true CN111382142B (en) | 2023-06-20 |
Family
ID=71215242
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010143676.1A Active CN111382142B (en) | 2020-03-04 | 2020-03-04 | Database operation method, server and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111382142B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111966679B (en) * | 2020-07-15 | 2022-09-30 | 宏图智能物流股份有限公司 | Storage transportation database cache management method and device |
| CN113468195B (en) * | 2021-07-15 | 2023-10-03 | 南方电网数字平台科技(广东)有限公司 | Server data cache updating method, system and main database server |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102331986A (en) * | 2010-07-12 | 2012-01-25 | 阿里巴巴集团控股有限公司 | Database cache management method and database server |
| CN102890675A (en) * | 2011-07-18 | 2013-01-23 | 阿里巴巴集团控股有限公司 | Method and device for storing and finding data |
| CN105512240A (en) * | 2015-11-30 | 2016-04-20 | 中国建设银行股份有限公司 | Data copying method and system based on different database |
| CN106331148A (en) * | 2016-09-14 | 2017-01-11 | 郑州云海信息技术有限公司 | Cache management method and cache management device for data reading by clients |
| CN106503186A (en) * | 2016-10-25 | 2017-03-15 | 广东浪潮大数据研究有限公司 | A kind of data managing method, client and system |
| CN106874343A (en) * | 2016-12-24 | 2017-06-20 | 上海七牛信息技术有限公司 | The data-erasure method and system of a kind of time series database |
| CN107562385A (en) * | 2017-09-13 | 2018-01-09 | 郑州云海信息技术有限公司 | Distributed storage client reads the method, apparatus and equipment of data |
| CN107562905A (en) * | 2017-09-08 | 2018-01-09 | 深圳市金立通信设备有限公司 | Management method, server and the computer-readable recording medium of data |
| CN108920300A (en) * | 2018-08-02 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of data manipulation method and relevant apparatus |
| CN110032567A (en) * | 2019-04-24 | 2019-07-19 | 江苏满运软件科技有限公司 | Report form inquiring method, device, server and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8326932B2 (en) * | 2009-02-20 | 2012-12-04 | Research In Motion Limited | Caching email unique identifiers |
-
2020
- 2020-03-04 CN CN202010143676.1A patent/CN111382142B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102331986A (en) * | 2010-07-12 | 2012-01-25 | 阿里巴巴集团控股有限公司 | Database cache management method and database server |
| CN102890675A (en) * | 2011-07-18 | 2013-01-23 | 阿里巴巴集团控股有限公司 | Method and device for storing and finding data |
| CN105512240A (en) * | 2015-11-30 | 2016-04-20 | 中国建设银行股份有限公司 | Data copying method and system based on different database |
| CN106331148A (en) * | 2016-09-14 | 2017-01-11 | 郑州云海信息技术有限公司 | Cache management method and cache management device for data reading by clients |
| CN106503186A (en) * | 2016-10-25 | 2017-03-15 | 广东浪潮大数据研究有限公司 | A kind of data managing method, client and system |
| CN106874343A (en) * | 2016-12-24 | 2017-06-20 | 上海七牛信息技术有限公司 | The data-erasure method and system of a kind of time series database |
| CN107562905A (en) * | 2017-09-08 | 2018-01-09 | 深圳市金立通信设备有限公司 | Management method, server and the computer-readable recording medium of data |
| CN107562385A (en) * | 2017-09-13 | 2018-01-09 | 郑州云海信息技术有限公司 | Distributed storage client reads the method, apparatus and equipment of data |
| CN108920300A (en) * | 2018-08-02 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of data manipulation method and relevant apparatus |
| CN110032567A (en) * | 2019-04-24 | 2019-07-19 | 江苏满运软件科技有限公司 | Report form inquiring method, device, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111382142A (en) | 2020-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8694472B2 (en) | System and method for rebuilding indices for partitioned databases | |
| US9830342B2 (en) | Optimizing database deduplication | |
| CN103150394B (en) | Distributed file system metadata management method facing to high-performance calculation | |
| WO2017049764A1 (en) | Method for reading and writing data and distributed storage system | |
| US8103621B2 (en) | HSM two-way orphan reconciliation for extremely large file systems | |
| CN102629247B (en) | Method, device and system for data processing | |
| JP2022500727A (en) | Systems and methods for early removal of tombstone records in databases | |
| EP2461615A1 (en) | Method for backing up terminal data and system thereof | |
| US20110314085A1 (en) | Offline modification of business data | |
| CN111382142B (en) | Database operation method, server and computer storage medium | |
| CN107391045B (en) | Directory space quota method and system | |
| US11507277B2 (en) | Key value store using progress verification | |
| CN103795811A (en) | Information storage and data statistical management method based on meta data storage | |
| CN106021327A (en) | A method for constructing a network disk system supporting simultaneous reading and writing of multiple users | |
| WO2024041433A1 (en) | Data processing method and apparatus | |
| JPH1021061A (en) | Automatic version-up system for client software | |
| CN116204575A (en) | Method, device, equipment and computer storage medium for importing data into database | |
| US8131884B1 (en) | Reusing system configuration information and metadata for related operations | |
| US11853229B2 (en) | Method and apparatus for updating cached information, device, and medium | |
| US11321374B2 (en) | External storage of unstructured database objects | |
| CN112445986B (en) | Cache information updating method, pushing method, device and medium | |
| CN111459913B (en) | Capacity expansion method and device of distributed database and electronic equipment | |
| US8909875B1 (en) | Methods and apparatus for storing a new version of an object on a content addressable storage system | |
| CN116049306A (en) | Data synchronization method, device, electronic equipment and readable storage medium | |
| JPH10111821A (en) | Client server 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 |