Database data manipulation methods, storage media and computer equipment

Abstract

This invention provides a database data manipulation method, storage medium, and computer device. The method includes: obtaining an operation instruction; determining the target data to be manipulated based on the operation instruction; checking the availability identifier of the existing version of the target data; if the availability identifier indicates unavailability, obtaining a conversion function from the target data's metadata table; calling the conversion function to convert the target data; and executing the operation instruction. This invention's solution can use a physical backup and restore strategy to upgrade the database system, allowing users to flexibly choose between using the original data structure storage or upgrading the data to a new data structure storage according to actual needs, and data can be manipulated normally regardless of the chosen strategy. This improves the convenience and efficiency of database upgrades.

Description

Technical Field

[0001] This invention relates to database technology, and in particular to data manipulation methods, storage media, and computer equipment for databases. Background Technology

[0002] There are two common methods for database upgrades: logical backup and restore, and physical backup and restore. Logical backup and restore involves exporting the old version of the database as a data file in SQL or another format, and then importing it into the new version. The database only needs to be compatible with the logical data file format. Physical backup and restore directly copies the physical storage files of the old version of the database to the new version. For the new database to recognize the new version upon startup, this requires compatibility at the physical storage format level.

[0003] During the iteration of database software, it's inevitable that we'll encounter situations where we need to modify the storage data structure of data types to meet new requirements. In such cases, physical backup and restore strategies cannot be used to upgrade existing databases; only logical backup and restore strategies can be employed. Logical backup and restore requires import and export operations, which can be time-consuming and cumbersome for databases with large amounts of data. Summary of the Invention

[0004] One object of the present invention is to provide a database data operation method, storage medium and computer device that can solve any of the above problems.

[0005] A further objective of this invention is to ensure the physical compatibility of the database when the storage data structure of data types is changed during database upgrades.

[0006] Another further objective of this invention is to enable normal reading and writing of existing data even when the storage data structure of the database changes its data type, thereby improving the convenience of database upgrades.

[0007] Another objective of this invention is to allow users to freely choose whether to upgrade the data to the current data type or retain the original data type when upgrading the database.

[0008] Specifically, the present invention provides a data manipulation method for a database, comprising:

[0009] Obtain operation instructions;

[0010] Determine the target data to be operated based on the operation instructions;

[0011] Check for available identifiers for existing versions of the target data;

[0012] If the available identifier is displayed as unavailable, then the conversion function is obtained from the metadata table of the target data;

[0013] Call the conversion function to convert the target data and execute the operation instructions.

[0014] Optionally, the operation instructions include: read instructions for performing read operations on the database;

[0015] The target data to be operated on, as determined by the operation instructions, includes: the value represented by the internal data structure of the target data being read;

[0016] The steps for executing the operation instructions include:

[0017] Retrieve the current version of the output function from the metadata table;

[0018] The existing version of the output function is used to perform the output operation, converting the value represented by the internal data structure into a string representation.

[0019] Optionally, the operation instructions include: write instructions for performing write operations on the database;

[0020] The target data to be operated on, as determined by the operation instructions, includes: the string representation value corresponding to the target data to be written;

[0021] Before the step of obtaining the transformation function from the metadata table of the target data, the following steps are included:

[0022] Retrieve the available input functions for the current version from the metadata table;

[0023] The current version of the available input functions can be used to perform input operations, converting the string representation of the value into the value represented by the internal data structure.

[0024] Optionally, the steps of obtaining operation instructions may include:

[0025] Retrieve database upgrade events;

[0026] Check the database system configuration for options related to user selection strategies;

[0027] If the option is to upgrade to the data type corresponding to the existing version, then the data conversion process will be executed.

[0028] Optionally, the steps of performing the data transformation process include:

[0029] Read data from the existing storage space and check the data availability flags one by one;

[0030] If the availability flag is set to available, the data will be stored in the existing storage space.

[0031] If the available flag is marked as unavailable, then the conversion function is retrieved from the metadata table;

[0032] The transformation function is called to transform the data, and then it is stored in the existing storage space.

[0033] Optionally, the step of storing in existing storage space may be followed by:

[0034] Update the metadata of the data, and update the availability flag to "available";

[0035] Associate metadata with existing storage space;

[0036] Delete the existing storage space.

[0037] Optionally, the database system configuration options regarding user selection strategies include:

[0038] Retain the original data types;

[0039] Upgrade the original data type to the current data type.

[0040] Optionally, the metadata table includes:

[0041] Meta-information table for data types and conversion information table between different versions of the same data type;

[0042] The metadata table for data types includes:

[0043] The data type's ID, name, version, availability flag, input function, and output function corresponding to the data type's version;

[0044] Conversion information between different versions of the same data type includes:

[0045] The data type ID, previous versions of the data type, currently available versions of the data type, and conversion functions between different versions of the data type.

[0046] According to another aspect of the present invention, a machine-readable storage medium is also provided, on which a machine-executable program is stored, which, when executed by a processor, implements the data operation method of any of the above-described databases.

[0047] According to another aspect of the present invention, a computer device is also provided, including a memory, a processor, and a machine-executable program stored in the memory and running on the processor, wherein the processor executes the machine-executable program to implement any of the above-described database data operation methods.

[0048] The database data operation method of this invention, after obtaining the operation instruction, determines the target data to be operated on according to the operation instruction, checks the existing version availability identifier of the target data, and if the existing version availability identifier shows that it is unavailable, retrieves a conversion function from the target data metadata table, calls the conversion function to convert the target data to a state available in the existing version, and continues to execute the operation instruction. After a database upgrade, if the physical storage of the database still contains the original version's data types, the existing version is incompatible with the original version's data types. Through the above method, the data types of the target data can be converted to data types available in the existing version when executing the operation instruction, thereby enabling the operation of the original version's data after a database upgrade, improving the convenience of database use. Simultaneously, when the database data types change, a physical backup and restore strategy can be used for database upgrades, improving the execution efficiency of database upgrades.

[0049] Furthermore, the database data manipulation method of the present invention, when executing a read instruction to perform a read operation on the database, determines the target data to be operated on based on the read instruction. It checks the existing version availability identifier of the target data. If the existing version availability identifier shows as unavailable, it indicates that the existing database does not support the original data type of the target data. Then, it retrieves a conversion function from the target data metadata table and converts the original data type of the target data to an existing available data type. Next, it retrieves the existing version output function from the target data metadata table and calls the output function to convert the converted target data into a string representation for output. This method, even after a database upgrade and change of data type, when the physically stored data still uses the original version's data type, can convert the data that the user wants to read into data usable in the existing database version for output. This eliminates the need for the user to update the original data's data type, improving the convenience of using the database.

[0050] Furthermore, the database data operation method of the present invention, when a user wants to execute a write instruction to perform a write operation on an existing database that has been upgraded and changed in terms of data type, and wants to store the written data according to the original version's data type, determines the target data to be operated on based on the write instruction. It retrieves the input function of the existing version from the target data metadata table, and calls the input function to convert the target data into a value represented by the database's internal data structure. It checks the version availability flag of the target data; if the version availability flag is unavailable, it indicates that the existing database does not support the original data type of the target data. Then, it retrieves the conversion function from the target data metadata table, converts the existing data type of the target data into the original data type, and then stores it in the storage space of the original data type. This method, even after the database upgrade and changes in data type, when the physically stored data still uses the original version's data type, allows the user to convert the data they want to write into the original version of the database data and then store it in the storage space of the original data type when they want to store the written data according to the original data type. This allows the user to choose whether to store the written data according to the existing version's data type or the original version's data type, improving the convenience of using the database.

[0051] Furthermore, in the database data operation method of the present invention, after the database upgrade event is completed, a user selection strategy is added to the database system configuration items, including retaining the original data types and upgrading the original data types to the existing data types. When the strategy of retaining the original data types is selected, the user's read and write operation process for the upgraded existing version database is as described above. When the strategy of upgrading the original data types to the existing data types is selected, the database reads data from the original data storage one by one and sequentially determines whether the data type of the read data is consistent with the data types available in the existing version. If they are consistent, the data is directly stored in the new storage space; if they are inconsistent, the conversion function in the data metadata table is queried, the conversion function is called to convert the data, and the converted data is stored in the new storage space. Subsequently, the information in the metadata table corresponding to the data is updated, associated with the new storage, and the old storage is deleted. This strategy allows users to choose whether to use the original data type storage structure or upgrade all data in the database to the storage structure of the existing database data types after the database upgrade, improving the convenience of database use.

[0052] The above and other objects, advantages and features of the present invention will become more apparent to those skilled in the art from the following detailed description of specific embodiments of the invention in conjunction with the accompanying drawings. Attached Figure Description

[0053] The following sections will describe some specific embodiments of the invention in detail by way of example and not limitation, with reference to the accompanying drawings. The same reference numerals in the drawings denote the same or similar parts or portions. Those skilled in the art should understand that these drawings are not necessarily drawn to scale. In the drawings:

[0054] Figure 1 This is a schematic flowchart of a database data operation method according to an embodiment of the present invention;

[0055] Figure 2 This is a schematic diagram of the process of reading database data in a database data operation method according to an embodiment of the present invention;

[0056] Figure 3 This is a schematic diagram of the process of writing database data in a database data operation method according to an embodiment of the present invention;

[0057] Figure 4 This is a schematic diagram of the process of upgrading data in an existing database in a database data operation method according to another embodiment of the present invention;

[0058] Figure 5 This is a schematic diagram of a machine-readable storage medium in a database data manipulation method according to an embodiment of the present invention; and

[0059] Figure 6 This is a schematic diagram of a computer device in a database data manipulation method according to an embodiment of the present invention. Detailed Implementation

[0060] Those skilled in the art should understand that the embodiments described below are merely a part of the embodiments of the present invention, and not all of the embodiments of the present invention. These partial embodiments are intended to explain the technical principles of the present invention and are not intended to limit the scope of protection of the present invention. Based on the embodiments provided by the present invention, all other embodiments obtained by those skilled in the art without creative effort should still fall within the scope of protection of the present invention.

[0061] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, such as calling a conversion function to convert between different versions of data data, can be implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a processor-based system, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device), or in conjunction with such an instruction execution system, apparatus, or device.

[0062] The method in this embodiment adds version information and conversion information between different versions of the same data type to the data type metadata of each piece of data in the database. Simultaneously, in the table definition, the version information of the available state of the data type at the time of record creation is also added to the column attribute information. Logical structure examples are shown in Tables 1 and 2:

[0063] Table 1 Data Type Meta-Information Table

[0064]

[0065] Table 2 Data Type Version Conversion Meta-Information Table

[0066]

[0067] Table 1, DataTypeMeta (Data Type Information), records the data type's id, name, version information, availability flag, and input / output functions. The availability flag indicates whether the original version of the data type is consistent with the current version, i.e., whether this data type is available in the current version of the database. Input functions convert externally input string values ​​into values ​​represented by internal data structures; output functions convert values ​​represented by internal data structures back into string values.

[0068] Table 2, DataTypeVersionConversion, records the conversion function information for data types from one version to another, that is, converting the internal structure defined in one version to the internal structure defined in another version. Conversionfunc is a conversion function that converts between the original version and the currently available version of a data type.

[0069] This embodiment also adds a user selection strategy option to the database system configuration items, where the user selection strategy includes retaining the old data type and upgrading to the new data type. When the database system starts up after an upgrade, it will check this configuration item and perform different workflows based on different user choices.

[0070] It should be noted that Tables 1 and 2 are just specific examples of data type metadata tables, and any table information that can achieve the above functions should be included in this invention.

[0071] Figure 1 This is a flowchart illustrating a database data manipulation method according to an embodiment of the present invention. It includes the following steps:

[0072] Step S101: Obtain operation instructions.

[0073] Step S102: Determine the target data to be operated according to the operation instructions.

[0074] Step S103: Check the available version identifier of the target data. The available version identifier is shown in Table 1, and it can be a boolean value or any value that can indicate whether it is available.

[0075] Step S104: Determine whether the result of the available identifier for the existing version is available.

[0076] Step S105: If the target data is deemed unavailable in step S104, a conversion function is retrieved from the target data's metadata table. The target data's metadata table in this step is shown in Tables 1 and 2, and the conversion function, such as Conversionfunc in Table 2, can convert between the original version of the data type and the currently available version.

[0077] Step S106: Call the conversion function to convert the target data.

[0078] Step S107: After completing the above operations, continue executing the operation instructions.

[0079] This embodiment provides a solution to the problem of data incompatibility between the existing and original data types in the database after an upgrade. This allows for continued operation on the original physical storage of the database even after data types have been modified following the upgrade, without the need for import / export operations required by logical backup and restore methods. This improves the convenience of database upgrades and reduces the overhead associated with them.

[0080] The above operation instructions may include read instructions. Figure 2 This is a schematic flowchart illustrating the process of reading database data in a database data manipulation method according to an embodiment of the present invention. It includes the following steps:

[0081] Step S201: Obtain the read instruction for the read operation.

[0082] Step S202: Determine the target data according to the read instruction.

[0083] Step S203: Check the existing version availability identifier of the target data. The existing version availability identifier, as shown in Table 1, can be a boolean value or any value that indicates availability.

[0084] Step S204: Determine whether the result of the available identifier for the existing version is available.

[0085] Step S205: If the target data is deemed unavailable in step S104, a conversion function is retrieved from the target data's metadata table. The target data's metadata table in this step is shown in Tables 1 and 2, and the conversion function, such as Conversionfunc in Table 2, can convert between the original version of the data type and the currently available version.

[0086] Step S206: Call the conversion function to convert the data type of the target data to a data type that is available in the current version.

[0087] Step S207: Obtain the existing version of the output function from the target data information table. The output function in this step is, for example, the function corresponding to Outputfunc in Table 1 above, which can convert the value represented by the internal data structure into a string format.

[0088] Step S208 involves calling the output function to convert the target data into a string representation. This step involves converting the target data from its internal database data structure representation into a string format, thereby increasing the readability of the target data.

[0089] Step S209, output the result.

[0090] The data reading process in this embodiment can be implemented when the database has been upgraded and the data types have been modified, resulting in incompatibility with the original version's data types. The data to be read by the user is converted within the database using a pre-set function, thereby enabling the existing version of the database to read the data from the original version of the database normally. This improves the compatibility and convenience of database upgrades.

[0091] The above operation instructions may also include write instructions. Figure 3 This is a schematic diagram of the process of writing database data in a database data operation method according to an embodiment of the present invention.

[0092] It should be noted that this embodiment addresses a situation where a user selects to retain the old data type in the user selection policy within the database system configuration settings. The user wants to perform write operations based on the new database's operation commands after the upgrade, and wants to save the data to the original (old) version's data storage space. Based on this requirement, the following solution steps are proposed:

[0093] Step S301: Obtain the write command for the write operation.

[0094] Step S302: Determine the target data according to the write instruction.

[0095] Step S303: Obtain the existing version of the input function from the target data information table. The input function in this step is, for example, the function corresponding to Inputfunc in Table 1 above, which can convert the string value input from the outside into a value represented by an internal data structure.

[0096] Step S304 involves calling the input function to convert the target data into a value represented by the database's internal data structure. This step refers to converting the target data from a string value to a value represented by the database's internal data structure.

[0097] Step S305: Check the existing version availability identifier of the target data. The existing version availability identifier, as shown in Table 1, can be a boolean value or any value that indicates availability.

[0098] Step S306: Determine whether the result of the available identifier for the existing version is available.

[0099] Step S307: If the target data is deemed unavailable in step S306, a conversion function is retrieved from the target data's metadata table. The target data's metadata table in this step is shown in Tables 1 and 2, and the conversion function, such as `Conversionfunc` in Table 2, can convert between the original version of the data type and the currently available version.

[0100] Step S308: Call the conversion function to convert the data type of the target data to the original data type.

[0101] Step S309: If the determination in step S306 is yes or if step S308 is completed, write to the storage file.

[0102] The data writing process in this embodiment can convert user-input data through a pre-set function when the database has been upgraded and the data types have been modified, resulting in incompatibility with the original version's data types. This allows the existing version of the database to store data normally in the original version's database, improving the compatibility and convenience of database upgrades.

[0103] When a user selects to upgrade to a new data type in the user selection policy within the database system configuration settings, the database system will upgrade the data in the physical storage of the original version. Figure 4 This is a flowchart illustrating the process of upgrading data in an existing database according to another embodiment of the present invention, comprising the following steps:

[0104] Step S401: Read data from the existing data storage. This step involves reading all data from the physical storage of the existing version database, and then operating on the read data row by row.

[0105] Step S402: Sequentially obtain the data type of the read data.

[0106] Step S403: Determine whether the data type of the original data is consistent with the data types available in the current version. This step involves checking each piece of data to see if the data type of the original data is consistent with the data types available in the current version. If they are inconsistent, it means that the data types of the original version are not available in the current version of the database after the upgrade; if they are consistent, it means that the data type is still available.

[0107] Step S404: If the determination result in step S403 is inconsistent, obtain the conversion function from the metadata table of the target data. The metadata tables of the target data in this step are shown in Tables 1 and 2, and the conversion function, such as Conversionfunc in Table 2, can convert between the original version and the currently available version of the data type.

[0108] Step S405: Call the conversion function to convert the data type of the target data to the existing version of the data type.

[0109] Step S406: Store the converted data in the new storage space.

[0110] Step S407: If the judgment result in step S403 is consistent, the original version data is stored in the new storage space.

[0111] Step S408: Update the metadata table corresponding to the target data and associate it with the new storage. This step refers to updating the version information and version availability identifier in the target data.

[0112] Step S409: Delete the old storage.

[0113] The update process in this embodiment can upgrade the data row by row in the physical storage of the original version of the database, even when the data types change after the database upgrade, resulting in incompatibility between the old and new versions. This improves the speed of migrating and upgrading existing data during database upgrades and also enhances the execution efficiency of the database upgrade.

[0114] This embodiment also provides a machine-readable storage medium and a computer device. Figure 5 This is a schematic diagram of a machine-readable storage medium 501 according to an embodiment of the present invention. Figure 6 This is a schematic diagram of a computer device 603 according to an embodiment of the present invention.

[0115] The machine-readable storage medium 501 stores a machine-executable program 502 thereon, which, when executed by a processor, implements the data operation method of the database in any of the above embodiments.

[0116] Computer device 603 may include memory 601, processor 602, and machine-executable program 502 stored on memory 601 and running on processor 602. When processor 602 executes machine-executable program 502, it implements the data operation method of the database in any of the above embodiments.

[0117] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, such as the method for calculating the schema feature values ​​of a relational table, can be specifically implemented in any machine-readable storage medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a processor-based system, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device), or in conjunction with such an instruction execution system, apparatus, or device.

[0118] For the purposes of this embodiment, the machine-readable storage medium 501 can be any means capable of containing, storing, communicating, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the machine-readable storage medium 501 include: an electrical connection (electronic device) having one or more wires, a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, the machine-readable storage medium 501 can even be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0119] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system.

[0120] Computer device 603 can be, for example, a server, desktop computer, laptop computer, tablet computer, or smartphone. In some examples, computer device 603 can be a cloud computing node. Computer device 603 can be described in the general context of computer system executable instructions (such as program modules) executed by a computer system. Typically, program modules can include routines, programs, object programs, components, logic, data structures, etc., that perform specific tasks or implement specific abstract data types. Computer device 603 can be implemented in a distributed cloud computing environment where tasks are performed by remote processing devices linked via a communication network. In a distributed cloud computing environment, program modules can reside on local or remote computing system storage media, including storage devices.

[0121] Computer device 603 may include a processor 602 adapted to execute stored instructions and a memory 601 that provides temporary storage space for the operation of said instructions during operation. The processor 602 may be a single-core processor, a multi-core processor, a computing cluster, or any other configuration. The memory 601 may include random access memory (RAM), read-only memory, flash memory, or any other suitable storage system.

[0122] The processor 602 can be connected via a system interconnect (e.g., PCI, PCI-Express, etc.) to an I / O interface (input / output interface) suitable for connecting the computer device 603 to one or more I / O devices (input / output devices). I / O devices may include, for example, a keyboard and indicating devices, where indicating devices may include a touchpad or touchscreen, etc. I / O devices may be built into the computer device 603 or may be external devices connected to the computing device.

[0123] The processor 602 may also be linked via a system interconnect to a display interface suitable for connecting the computer device 603 to a display device. The display device may include a display screen as a built-in component of the computer device 603. The display device may also include a computer monitor, television, or projector, etc., externally connected to the computer device 603. Furthermore, a network interface controller (NIC) may be adapted to connect the computer device 603 to a network via a system interconnect. In some embodiments, the NIC may use any suitable interface or protocol (such as an Internet Minicomputer System Interface) to transmit data. The network may be a cellular network, a radio network, a wide area network (WAN), a local area network (LAN), or the Internet, etc. Remote devices may connect to the computing device via the network.

[0124] The flowcharts provided in this embodiment are not intended to indicate that the operations of the method will be performed in any particular order, or that all operations of the method are included in every case. Furthermore, the method may include additional operations. Within the scope of the technical concept provided by the method in this embodiment, additional variations can be made to the above method.

[0125] Therefore, those skilled in the art should recognize that although numerous exemplary embodiments of the present invention have been shown and described in detail herein, many other variations or modifications conforming to the principles of the present invention can be directly determined or derived from the disclosure of the present invention without departing from the spirit and scope of the invention. Thus, the scope of the present invention should be understood and construed as covering all such other variations or modifications.

Claims

1. A database data manipulation method, comprising: Obtain operation instructions; The target data to be operated is determined according to the operation instructions; Check the available identifiers for existing versions of the target data; If the available identifier is not available, then the conversion function is obtained from the metadata table of the target data; The conversion function is invoked to convert the target data, and the operation instructions are executed. The operation instructions include: write instructions for performing write operations on the database; The step of determining the target data to be operated according to the operation instruction includes: the value represented by the string corresponding to the target data to be written; Before the step of obtaining the conversion function from the metadata table of the target data, the steps include: obtaining the currently available input function from the metadata table; and using the currently available input function to perform an input operation to convert the string representation of the value into the value represented by the internal data structure. The metadata table includes: a metadata table for data types and a conversion information table between different versions of the same data type; The metadata table for the data type includes: the data type's ID, name, version, availability flag, input function, and output function for the corresponding version of the data type; The conversion information between different versions of the same data type includes: the ID of the data type, the previous version of the data type, the currently available version of the data type, and the conversion function between different versions of the data type.

2. The database data manipulation method according to claim 1, wherein, The operation instructions include: read instructions for performing read operations on the database; The step of determining the target data to be operated according to the operation instruction includes: the value represented by the internal data structure of the target data being read; The steps for executing the operation instructions include: Retrieve the existing version of the output function from the metadata table; The existing version of the output function is used to perform the output operation, converting the value represented by the internal data structure into a string representation.

3. The database data manipulation method according to claim 1, wherein, Prior to the step of obtaining the operation instruction, the following steps are included: Obtain the upgrade event of the database; Check the options related to user selection strategy in the system configuration of the database; If the selected option is a data type corresponding to the existing version, then the data conversion process will be executed.

4. The database data manipulation method according to claim 3, wherein, The steps of the data transformation process include: Read data from the existing storage space and check the available identifiers of the data in sequence; If the availability identifier is available, then the data is stored in the existing storage space; If the available identifier is unavailable, then the conversion function is obtained from the metadata table; The data is transformed by calling the transformation function and then stored in the existing storage space.

5. The database data manipulation method according to claim 4, wherein, Following the step of storing in the existing storage space, the following is also included: Update the metadata of the data, and update the availability identifier to available; The metadata is associated with the existing storage space; Delete the existing storage space.

6. The database data manipulation method according to claim 3, wherein, The database system configuration includes the following options regarding user selection strategies: Retain the original data types; Upgrade the original data type to the current data type.

7. A machine-readable storage medium having a machine-executable program stored thereon, the machine-executable program, when executed by a processor, implementing the data manipulation method of the database according to any one of claims 1 to 6.

8. A computer device comprising a memory, a processor, and a machine-executable program stored in the memory and running on the processor, wherein the processor, when executing the machine-executable program, implements a data manipulation method for a database according to any one of claims 1 to 6.

Images