An object-oriented nested Record data type management method

Through object-oriented design, abstracting and managing nested Record data types, the problem of nested Record data type processing in the existing technology is solved, efficient data management and security are achieved, and large-scale data processing is suitable for large-scale data processing.

CN118820280BActive Publication Date: 2024-11-19JIANGSU HUAKU DATA TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411305332.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-19
Publication Date
2024-11-19
Estimated Expiration
2044-09-19

AI Technical Summary

Technical Problem

It is difficult for the prior art to effectively manage and process complex nested Record data types, especially in large-scale data processing, and the processing methods of basic data types cannot meet the needs of storage and reading and writing.

Method used

Adopting an object-oriented design, the Record data type is abstracted into Record classes and Record objects, and the management of nested Record data types is realized through recursive use of class and object methods, including abstraction of field names and field types, allocation of storage areas, Abstraction of write and read operations.

Benefits of technology

It realizes nested management of any layer Record data type, improves the security and reliability of data management, meets the needs of large-scale data processing, and is more convenient to operate regardless of the number of nested layers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118820280B_ABST
    Figure CN118820280B_ABST
Patent Text Reader

Abstract

The present invention relates to the field of database technology, and provides an object-oriented nested Record data type management method, comprising: obtaining the field name and field type of the nested Record data by recursively calling the Record class, allocating the storage area of ​​the nested Record data by recursively using the Record object; writing the value into the storage area by recursively calling the assignment method of the Record object; reading the value in the storage area by recursively calling the value method of the Record object; adopting the concepts of class, object and method, realizing the management of the nested Record data type, the present invention has no limit on the number of layers of data nesting, and can realize the nesting of any layer of Record data type, so that users can more conveniently create, operate and manage the nested Record type, can meet the needs of large-scale data processing, and improve the security and reliability of data management.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of database technology, and in particular to an object-oriented nested Record data type management method. Background Art

[0002] With the advent of the data age, the data that systems or programs need to store or maintain is becoming more and more abundant. Record is a user-defined composite data type in the database. It can be understood as a row of data in a table. The data contains a set of fields. Each field has a corresponding data type. The data type can be a basic data type, such as integer, character, date, or another user-defined Record data type. In this case, this data type is a nested Record data type. In other words, at least one field type in the nested Record data type is another Record data type, and the field type of another Record data type may also be a Record data type. Compared with the basic data type, the difficulty of nested Record data types in storage and reading and writing increases exponentially. When processing large-scale data, the processing method of basic data types is no longer applicable. Summary of the invention

[0003] The present invention aims to solve at least one of the technical problems existing in the related art. To this end, the present invention provides an object-oriented nested Record data type management method, which realizes the nesting of any layer of Record data type, can more conveniently create, operate and manage nested Record data types, meet the processing of large-scale data, and improve the security and reliability of data management. The present invention provides an object-oriented nested Record data type management method, comprising the following steps:

[0004] S1: Use the class in the programming language to abstract the Record data type into the Record class in the object-oriented language, and obtain the field name and field type of the nested Record data by recursively using the Record class;

[0005] S2: Using objects in the programming language, the nested Record variables are abstracted into Record objects in the object-oriented language. According to the field name and field type of the nested Record data, the storage area of ​​each field of the nested Record variable is allocated by recursively using the Record object.

[0006] S3: Use the class method in the programming language to abstract the write operation of the nested Record variable into the assignment method of the Record object in the object-oriented language, and write the value into the storage area of ​​the target field of the nested Record variable by recursively calling the assignment method of the Record object;

[0007] S4: Use the class method in the programming language to abstract the read operation of the nested Record variable into the value-taking method of the Record object in the object-oriented language, and read the value in the storage area of ​​the target field of the nested Record variable by recursively calling the value-taking method of the Record object.

[0008] According to an object-oriented nested Record data type management method provided by the present invention, the step of recursively calling the Record class in the step S1 is as follows:

[0009] S11: define the Record data type whose field types are all basic field types as the first Record class;

[0010] S12: Record the field name and field type of each field of the first Record class;

[0011] S13: define the nested Record data type whose field type is the first Record class as the second Record class;

[0012] S14: Record the field name and field type of the second Record class according to the field name and field type of the first Record class;

[0013] S15: Repeat steps S13 and S14 until all field types are basic field types.

[0014] According to an object-oriented nested Record data type management method provided by the present invention, the step of recursively applying the Record object in the step S2 is as follows:

[0015] S21: abstract the nested Record variable into a Record object in object-oriented programming, allocate an overall storage area for the Record object, and calculate the storage space occupied by each field according to the field name and field type of the nested Record data;

[0016] S22: abstracting a variable whose field type is a nested Record data type into a Record sub-object in object-oriented programming, and obtaining the field type of the Record sub-object according to the field type of the Record object;

[0017] S23: Repeat step S22 until all field types of the Record sub-object are basic field types;

[0018] S24: Allocate a storage area for each field of the nested Record variable according to the storage space occupied by each field.

[0019] According to an object-oriented nested Record data type management method provided by the present invention, the starting position of the first field storage area of ​​the nested Record variable is the starting position of the Record object storage area, and the starting position of the second field storage area of ​​the nested Record variable is the position of the Record object after the starting position is offset by the storage space of the first field type.

[0020] According to an object-oriented nested Record data type management method provided by the present invention, the method further includes recording the starting position of the storage area of ​​each layer of Record sub-object.

[0021] According to an object-oriented nested Record data type management method provided by the present invention, the nested Record variable assignment step in the S3 step is as follows:

[0022] S31: Match the field name of the nested Record variable with the assignment target through the assignment method of the Record object;

[0023] S32: The field type corresponding to the field name of the matched nested Record variable is the nested Record data type, and the assignment method of the Record object is called again;

[0024] S33: Repeat steps S31 and S32 until the field type corresponding to the field name of the matched nested Record variable is a basic data type, and obtain the storage area of ​​the field of the nested Record variable;

[0025] S34: Write the assignment target into the storage area of ​​the field of the nested Record variable.

[0026] According to an object-oriented nested Record data type management method provided by the present invention, the method further includes matching each layer of Record sub-objects with their own first layer fields.

[0027] According to an object-oriented nested Record data type management method provided by the present invention, the nested Record variable value obtaining step in the S4 step is as follows:

[0028] S41: Match the field name of the nested Record variable with the value target through the assignment method of the Record object;

[0029] S42: The field type corresponding to the field name of the matched nested Record variable is the nested Record data type, and the value method of the Record object is called again;

[0030] S43: Repeat steps S41 and S42 until the field type corresponding to the field name of the matched nested Record variable is a basic data type, and obtain the storage area of ​​the field of the nested Record variable;

[0031] S44: Read the value in the storage area of ​​the field of the nested Record variable.

[0032] The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of any of the above-mentioned object-oriented nested Record data type management methods are implemented.

[0033] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the above-mentioned object-oriented nested Record data type management methods.

[0034] The above one or more technical solutions in the embodiments of the present invention have at least one of the following technical effects:

[0035] The object-oriented nested Record data type management method provided by the present invention realizes the management of nested Record data types by adopting the concepts of class, object and method based on the object-oriented design concept. Under ideal conditions without considering external constraints such as storage space, the present invention has no limit on the number of nested layers and can realize the nesting of any layer of Record data type. It enables users to create, operate and manage nested Record types more conveniently, can meet the needs of large-scale data processing, and improve the security and reliability of data management.

[0036] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0038] Figure 1A schematic flow chart of an object-oriented nested Record data type management method provided by the present invention.

[0039] Figure 2 A block diagram of an object-oriented nested Record data type management system provided by the present invention.

[0040] Reference numerals:

[0041] 201, processor; 202, communication bus; 203, communication interface; 204, memory. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical scheme and advantages of the present invention clearer, the technical scheme in the present invention will be clearly and completely described below. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present invention. The following embodiments are used to illustrate the present invention, but cannot be used to limit the scope of the present invention.

[0043] In the description of the embodiments of the present invention, it should be noted that the terms “first”, “second” and “third” are only used for descriptive purposes and cannot be understood as indicating or implying relative importance.

[0044] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0045] Combine the following Figure 1 The present invention describes an object-oriented nested Record data type management method. This embodiment takes SQL database processing of two-layer nested Record data as an example.

[0046] The present invention provides an object-oriented nested Record data type management method, comprising the following steps:

[0047] S1: Use the class in the programming language to abstract the Record data type into the Record class in the object-oriented language, and obtain the field name and field type of the nested Record data by recursively using the Record class;

[0048] In this embodiment, the statements in the SQL database are as follows:

[0049] TYPE record_type1 IS RECORD(field1 INT, field2 CHAR);

[0050] TYPE record_type2 IS RECORD(field3 INT, field4 record_type1);

[0051] The steps to recursively call the Record class are as follows:

[0052] S11: define the Record data type whose field types are all basic field types as the first Record class;

[0053] In this embodiment, the field types of record_type1 are all basic field types, so record_type1 is defined as the first Record class;

[0054] S12: Record the field name and field type of each field of the first Record class;

[0055] In this embodiment, each field is initialized according to the field information of record_type1, the field name of the first field is initialized to field1, and the field type of the first field is initialized to integer type (INT); the field name of the second field is initialized to field2, and the field type of the second field is initialized to character type (CHAR), and the field name and field type of each field of the first Record class are recorded according to the initialization result;

[0056] S13: define the nested Record data type whose field type is the first Record class as the second Record class;

[0057] In this embodiment, the fourth field type of record_type2 is a nested Record data type, so record_type2 is defined as the second Record class;

[0058] S14: Initialize the second Record class according to the field name and field type of the first Record class;

[0059] In this embodiment, the field name of the third field is initialized to field3, and the field type of the third field is initialized to integer type (INT); when initializing the fourth field field4, it can be identified that its field type record_type1 is the first Record class defined in the present invention, and the field name and field type of each field of the first Record class are called to complete the initialization of the fourth field field4, and the field name and field type of each field of the second Record class are recorded;

[0060] The field type of field4 is represented as the first Record class that has been initialized when record_type1 was defined previously. That is to say, the Record class in the programming language is also nested, and the type information in the outer class member may be another Record class in the inner layer.

[0061] S15: Repeat steps S13 and S14 until all field types are basic field types;

[0062] The nested Record data of this embodiment has only two layers. After recording the field name and field type of each field of the second Record class, the initialization of the nested Record data is completed.

[0063] S2: Using objects in the programming language, the nested Record variables are abstracted into Record objects in the object-oriented language. According to the field name and field type of the nested Record data, the storage area of ​​each field of the nested Record variable is allocated by recursively using the Record object.

[0064] In this embodiment, the variable corresponding to the nested Record type record_type2 is defined as record_variable;

[0065] The SQL database statement is as follows:

[0066] TYPE record_type1 IS RECORD(field1 INT, field2 CHAR);

[0067] TYPE record_type2 IS RECORD(field3 INT, field4 record_type1);

[0068] record_variable record_type2;

[0069] The steps to recursively use the Record object are as follows:

[0070] S21: abstract the nested Record variable into a Record object in object-oriented programming, allocate an overall storage area for the Record object, and calculate the storage space occupied by each field according to the field name and field type of the nested Record data;

[0071] In this embodiment, record_variable is abstracted into a Record object in a programming language, and an overall storage area is allocated to the Record object, and the storage space occupied by each field is calculated according to the field name and field type of the nested Record data;

[0072] S22: abstracting a variable whose field type is a nested Record data type into a Record sub-object in object-oriented programming, and obtaining the field type of the Record sub-object according to the field type of the Record object;

[0073] In this embodiment, the field type of the fourth field field4 of record_variable is record_type1, so field4 is abstracted as a Record sub-object, and the field type of field3 is INT and the field type of field4 is record_type1 according to the Record object, so that the field type of the Record sub-object is record_type1;

[0074] S23: Repeat step S22 until all field types of the Record sub-object are basic field types;

[0075] In this embodiment, the field type of field1 in record_type1 is INT, the field type of field2 is CHAR, and all field types in record_type1 are basic field types, and step S22 is not repeated;

[0076] S24: Allocate a storage area for each field according to the storage space occupied by each field.

[0077] The starting position of the first field storage area of ​​the nested Record variable is the starting position of the Record object storage area, and the starting position of the second field storage area of ​​the nested Record variable is the position of the Record object after the starting position is offset by the storage space of the first field type;

[0078] In this embodiment, for the third field (field3) of record_variable, the starting position of its storage area is the starting position of the storage area of ​​this Record object; and for the fourth field (field4), the starting position of its storage area is the position of this Record object after offsetting the starting position by an integer storage space.

[0079] In this embodiment, after obtaining the starting position, because the field type record_type1 of field4 is another Record type defined in the present invention, the present invention represents field4 as a sub-object in the programming language. At the same time, the field type of the Record sub-object can be obtained from the field type of the Record object, and then the storage area for the value of each specific field of this Record sub-object can be allocated.

[0080] From initializing record_variable to initializing field4 is a recursive process. The key to this process is that each Record object only needs to know the starting position of its own storage area, but does not need to know the starting position of its upper Record object. Therefore, the present invention ensures the scalability of the number of nested layers of nested Record data types.

[0081] S3: Use the class method in the programming language to abstract the write operation of the nested Record variable into the assignment method of the Record object in the object-oriented language, and write the value into the storage area of ​​the target field of the nested Record variable by recursively calling the assignment method of the Record object;

[0082] Design the reading and writing of Record variables in SQL language as class methods in the programming language;

[0083] In this embodiment, an integer variable int_variable is defined, and the statement in the SQL database is as follows:

[0084] TYPE record_type1 IS RECORD(field1 INT, field2 CHAR);

[0085] TYPE record_type2 IS RECORD(field3 INT, field4 record_type1);

[0086] record_variable record_type2;

[0087] int_variable INT;

[0088] record_variable.field4.field1 := 123;

[0089] The specific steps to assign values ​​to variables using the Record object's assignment method are as follows:

[0090] S31: Match the field name of the nested Record variable with the assignment target through the assignment method of the Record object;

[0091] In this embodiment, when assigning a value to a target field of a Record variable, the assignment method of the Record object in the programming language is called to match each field name of the variable record_variable with the assignment target respectively;

[0092] S32: The field type corresponding to the field name of the matched nested Record variable is the nested Record data type, and the assignment method of the Record object is called again;

[0093] In this embodiment, when field 4 is matched, the field type record_type1 of field 4 is another defined Record type, and the assignment method of the Record object is called again for the sub-object corresponding to field 4;

[0094] S33: Repeat steps S31 and S32 until the field type corresponding to the field name of the matched nested Record variable is a basic data type, and obtain the storage area of ​​the field of the nested Record variable;

[0095] In this embodiment, when field1 is matched, the field type of field1 is integer type (INT), and the storage area of ​​field1 is obtained;

[0096] S34: writing the assignment target into the storage area of ​​the field of the nested Record variable;

[0097] In this embodiment, the assignment target 123 is written into the storage area of ​​field1;

[0098] The assignment method call from record_variable to field4 is also recursive. In the assignment method of the Record object, each Record object only needs to match the first-level fields under itself, and does not need to match the lower-level fields layer by layer.

[0099] S4: Using the class method in the programming language, the read operation of the nested Record variable is abstracted into the value-getting method of the Record object in the object-oriented language, and the value in the storage area of ​​the target field is read by recursively calling the value-getting method of the Record object;

[0100] In this embodiment, the statements in the SQL database are as follows:

[0101] int_variable := record_variable.field4.field1;

[0102] The steps to obtain the value of a nested Record variable are as follows:

[0103] S41: Match the field name of the nested Record variable with the value target through the assignment method of the Record object;

[0104] In this embodiment, when the value of the Record variable field is assigned to the target variable, the value method of the Record object in the programming language is called to match each field name of the variable record_variable with the value target;

[0105] S42: The field type corresponding to the field name of the matched nested Record variable is the nested Record data type, and the value method of the Record object is called again;

[0106] In this embodiment, when field 4 is matched, the field type record_type1 of field 4 is another defined Record type, and the assignment method of the Record object corresponding to field 4 is called again;

[0107] S43: Repeat steps S41 and S42 until the field type corresponding to the field name of the matched nested Record variable is a basic data type, and obtain the storage area of ​​the field of the nested Record variable;

[0108] In this embodiment, when field1 is matched and the field type of field1 is an integer type (INT), the matching is stopped and the storage area of ​​field1 is obtained;

[0109] S44: Read the value in the storage area of ​​the target field of the nested Record variable. In this embodiment, the corresponding value 123 is read from the storage area of ​​field1, and 123 is written into the target variable int_variable.

[0110] Figure 2The following is a block diagram of an object-oriented nested Record data type management system. Figure 2 As shown, the system includes: a processor 201, a communication interface 203, a memory 204 and a communication bus 202, wherein the processor 201, the communication interface 203 and the memory 204 communicate with each other through the communication bus 202. The processor 201 can call the logic instructions in the memory 204 to execute an object-oriented nested Record data type management method.

[0111] In addition, the logic instructions in the above-mentioned memory 204 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0112] On the other hand, the present invention also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer can execute an object-oriented nested Record data type management method provided by the above methods.

[0113] On the other hand, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which is implemented when the computer program is executed by a processor to perform the above-mentioned object-oriented nested Record data type management method.

[0114] The beneficial effects of the present invention are as follows: the object-oriented nested Record data type management method provided by the present invention realizes the management of nested Record data types by adopting the concepts of class, object and method based on the object-oriented design concept. Under ideal conditions without considering external constraints such as storage space, the present invention has no limit on the number of nested layers and can realize the nesting of any layer of Record data types. It enables users to create, operate and manage nested Record types more conveniently, can meet the needs of large-scale data processing, and improve the security and reliability of data management.

[0115] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0116] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0117] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. An object-oriented nested Record data type management method, characterized in that: The steps include: S1: Use the class in the programming language to abstract the Record data type into the Record class in the object-oriented language, and obtain the field name and field type of the nested Record data by recursively using the Record class; S2: Using objects in the programming language, the nested Record variables are abstracted into Record objects in the object-oriented language. According to the field name and field type of the nested Record data, the storage area of ​​each field of the nested Record variable is allocated by recursively using the Record object. S3: Use the class method in the programming language to abstract the write operation of the nested Record variable into the assignment method of the Record object in the object-oriented language, and write the value into the storage area of ​​the target field of the nested Record variable by recursively calling the assignment method of the Record object; S4: Use the class method in the programming language to abstract the read operation of the nested Record variable into the value-taking method of the Record object in the object-oriented language, and read the value in the storage area of ​​the target field of the nested Record variable by recursively calling the value-taking method of the Record object.

2. The object-oriented nested Record data type management method according to claim 1, characterized in that: The steps of recursively calling the Record class in step S1 are as follows: S11: define the Record data type whose field types are all basic field types as the first Record class; S12: Record the field name and field type of each field of the first Record class; S13: define the nested Record data type whose field type is the first Record class as the second Record class; S14: Record the field name and field type of the second Record class according to the field name and field type of the first Record class; S15: Repeat steps S13 and S14 until all field types of the nested Record data are basic field types.

3. The object-oriented nested Record data type management method according to claim 1, characterized in that: The steps for recursively using the Record object in step S2 are as follows: S21: abstract the nested Record variable into a Record object in object-oriented programming, allocate an overall storage area for the Record object, and calculate the storage space occupied by each field according to the field name and field type of the nested Record data; S22: abstracting a variable whose field type is a nested Record data type into a Record sub-object in object-oriented programming, and obtaining the field type of the Record sub-object according to the field type of the Record object; S23: Repeat step S22 until all field types of the Record sub-object are basic field types; S24: Allocate a storage area for each field of the nested Record variable according to the storage space occupied by each field.

4. The object-oriented nested Record data type management method according to claim 3, characterized in that: The starting position of the first field storage area of ​​the nested Record variable is the starting position of the Record object storage area, and the starting position of the second field storage area of ​​the nested Record variable is the position of the Record object after the starting position is offset by the storage space of the first field type.

5. The object-oriented nested Record data type management method according to claim 4, characterized in that: Each layer of Record sub-object records the starting position of its storage area.

6. The object-oriented nested Record data type management method according to claim 3, characterized in that: The steps for assigning values ​​to nested Record variables in the S3 step are as follows: S31: Match the field name of the nested Record variable with the assignment target through the assignment method of the Record object; S32: The field type corresponding to the field name of the matched nested Record variable is the nested Record data type, and the assignment method of the Record object is called again; S33: Repeat steps S31 and S32 until the field type corresponding to the field name of the matched nested Record variable is a basic data type, and obtain the storage area of ​​the field of the nested Record variable; S34: Write the assignment target into the storage area of ​​the field of the nested Record variable.

7. The object-oriented nested Record data type management method according to claim 6, characterized in that: Each layer of Record sub-object matches its own first-layer fields.

8. The object-oriented nested Record data type management method according to claim 1, characterized in that: The steps for obtaining the value of the nested Record variable in step S4 are as follows: S41: Match the field name of the nested Record variable with the value target through the assignment method of the Record object; S42: The field type corresponding to the field name of the matched nested Record variable is the nested Record data type, and the value method of the Record object is called again; S43: Repeat steps S41 and S42 until the field type corresponding to the field name of the matched nested Record variable is a basic data type, and obtain the storage area of ​​the field of the nested Record variable; S44: Read the value in the storage area of ​​the target field of the nested Record variable.