CN116306532A

CN116306532A - Data connection and presentation method, device, system and storage medium

Info

Publication number: CN116306532A
Application number: CN202111500997.3A
Authority: CN
Inventors: 李界和
Original assignee: Wisteria Intellectual Property Operations Shenzhen Co ltd
Current assignee: Wisteria Intellectual Property Operations Shenzhen Co ltd
Priority date: 2021-12-09
Filing date: 2021-12-09
Publication date: 2023-06-23
Also published as: WO2023103311A1

Abstract

The invention relates to a data connection and presentation method, which can present user data tables with unlimited field combinations and unlimited quantity only by data structures generated by limited bottom tables in a database. Utilizing a database bottom table to generate a plurality of abstract data structures for representing the constituent elements of the user data table, wherein the abstract data structures comprise a target object item of a first dimension block, a problem field item of a second dimension block and a filling content item corresponding to the first dimension and the second dimension in a filling result block of the user data table. The data in each abstracted data structure is associated with one of a plurality of database-based tables to present the data content of each component of the user data table.

Description

Data connection and presentation method, device, system and storage medium

Technical Field

The present invention relates to the field of computer science, and more particularly, to a data connection and presentation method.

Background

Traditionally, information technology (Information Technology, IT) system programmers have designed the underlying tables of databases, essentially one-to-one, according to the needs of the user. Taking personnel data of a company as an example, the user side requirements generally include these data tables: a personnel basic data table, a personnel expertise data table, a personnel salary data table, a personnel leave record data table, a personnel attendance record data table, a personnel examination record data table and the like. The traditional way for a programmer to design is to build an underlying table (table) on the database that corresponds to the requirements. For the functions of adding and deleting data of different bottom tables of the database, different program codes are conventionally used for corresponding processing. Once a user end subsequently has a new data table, a conventional approach is to add a new underlying table to the database and add data editing function programs such as adding and deleting corresponding to the new underlying table. This situation causes the conventional programming effort to increase in proportion to the increase of the data table requirement of the user end, which causes a heavy burden to the programmer.

Traditionally, one of the major challenges encountered in database bottom-level table design is the initial adoption of a "one-to-one" data structure, with the subsequent end-of-use changing requirements, hopefully becoming a "one-to-many" structure. For example, an underlying table corresponding to personnel data contains the following fields:

1.ID

2.Name

3.Department

4.Title

5.Telephone

6.Address

the ID is a unique Identifier (ID) of the underlying table. Such a data structure is a so-called "one-to-one" data structure, i.e. each field in each piece of data is filled with a single value, rather than a plurality of values. This is not problematic for the general case, because a person corresponds to only one name, one division, one title, one phone, etc. However, as the actual demand changes, there are two telephone numbers from the beginning, so users have placed new demands that a second set of telephone numbers needs to be stored. The traditional correspondence is to add a "text 2" field to the underlying table as follows:

1.ID

2.Name

3.Department

4.Title

5.Telephone

6.Telephone2

7.Address

even though adding fields to the underlying form is a simple matter, it is a burden to the programmer that the corresponding amount of code must be coordinated to correspond to the addition of the new field Telephone 2. More challenging is that the practical requirement that the user end wish to add fields is often continuous, for example, because the employee starts to have a third phone number, the job title needs to be split between the inside and the outside, and so on. In the face of situations where the actual requirements will always vary, every field is added to mobilize all relevant program code, which presents a challenge of not little maintenance burden for the program code.

In the face of the situation, conventionally, another approach is to separate the data relationship of "person" to "phone" into a new underlying table, such as the underlying table called "peer_phone", with fields: ID. A telephone. The contents of the underlying table peopleiectephone are exemplified as follows:

people_telephone

ID	Telephone
		1	23456
2	10110
		2	10020
:	:

for example, a person with id=1 has one phone number 23456 and a person with id=2 has two phone numbers 10110, 10020. The data structure of this way has the advantage of providing flexibility to cope with situations where no matter how many phones are available, the corresponding program code is basically only adjusted once, and the overall programming effort is much less than in the previous conventional method.

However, as the actual requirements change, if there are other fields, such as Address, that also need to be changed to "one-to-many", another adjustment will be needed. And as the situation of changing the field 'one-to-one' into 'one-to-many', the number of the newly independent bottom tables is increased, and the situation of increasing the number of the bottom tables, the maintenance of the information system is also very challenging.

Therefore, in the information system design, a programmer often emphasizes the requirement for the user end to be clear at first, and what data tables and all fields are needed to be defined in a one-to-one or one-to-many relationship are clear, so that the data structure of the underlying table can be determined to be designed. The data structure of the underlying form is just like the infrastructure of a building, and it is often cumbersome to go back to adjust the infrastructure once it is completed. Although theoretically possible, the method is practically effective, and the pulling and the whole body are changed, so that few people are willing to do so in practice.

On the other hand, in the aspect of editing and recording data, in order to record information of data maintainers, time and the like, taking the bottom table of the database corresponding to employee data as an example, fields of a creator and a date_update are added in the conventional design, for example:

1.ID

2.Name

3.Department

4.Title

5.Telephone

6.Address

7.creator

8.date_update

however, such a data structure can only reflect who the "whole record" of the record set was last (i.e., the creator field) when (i.e., the date_update field) was compiled, and cannot reflect when each field is adjusted by which person, respectively. This is a bottleneck that conventional practice does not practically overcome. Although each field can be theoretically assigned to a corresponding creator, date_update is structured as follows:

1.ID

2.Name

3.Name_creator

4.Name_date_update

5.Department

6.Department_creator

7.Department_date_update

8.Title

9.Title_creator

10.Title_date_update

11.Telephone

12.Telephone_creator

13.Telephone_date_update

14.Address

15.Address_creator

16.Address_date_update

it is apparent that such a cumbersome field design is practically impossible to do as the associated program code becomes very complex.

It is conventionally another practice to record (log) from whom, when, what the contents of the field were before editing, etc. a particular database-based table (e.g., named wait_log). The "content of the field before editing" is generally stored in text form, but it is difficult to process when a specific field content needs to be queried in the past, unless a standardized design is available.

In a conventional data structure design method, when a user requests the user data table a as described above, a programmer sets up a database bottom table a including fields a, b and c on the database. When the user has set forth another user data table B, the programmer opens a database bottom table B in the database. It is conceivable that in this way, how many user data table requirements are set up by the user, and how many database-underlying tables are often set up in the database. With the change of the actual requirement, the number of user data tables required by the user is often increased, and the details of the required fields may be changed afterwards, so that the maintenance of the program code is not easy.

Rights management is a necessary mechanism for an information system used by multiple persons. For example, employee data, project data, customer data, etc., may require rights management to set up different rights that a user may have to read, write, manage, etc. For example, a database is provided with an underlying table employee to record employee data, an underlying table project to record project data, an underlying table customer to record customer data, and conventionally a design is to allocate an authority table to each of the underlying table employee data table (employee), project data table (project), customer data table (customer), etc., for example: three underlying tables of permission_ people, project _permission_ project, permission _customer. However, it is obvious in this way how many objects, how many underlying tables need to be configured to record rights.

In view of the above-described dilemma, the present invention provides a way to increase the number of tables required by users, and basically, the number of tables at the bottom of the database does not need to be increased, unlike the conventional method, which causes a proportional increase in the workload of programming/maintenance. Basically, with a limited number of database-underlying tables, a user data table can be constructed that is far greater than the number of database-underlying tables. This allows the maintenance costs of the database-underlying tables, and their program code, to be significantly reduced.

Disclosure of Invention

In order to solve the problems, the invention provides a data connection and presentation method, a device, a system and a storage medium.

In an embodiment of the present invention, a data connection and presentation method includes: generating a questionnaire form in the database bottom form for loading a user data form content representing a user data form; generating a plurality of data content tables in the database bottom table, wherein the data content tables are used for loading various data contents; generating a questionnaire object table in the database bottom table for loading data items of a plurality of objects in a first dimension block of the user data table, wherein the questionnaire object table comprises a field for being associated with the questionnaire table and a target object identification number field for being associated with data contents in the plurality of data content tables; generating a questionnaire template form in the database bottom form, wherein the questionnaire form comprises a field for being related to the questionnaire template form; generating a problem table in the database bottom table; generating a questionnaire template question form in the database bottom form for being associated with a plurality of question fields in a second dimension block of the user data form, wherein the questionnaire template question form comprises a template identification number field for being associated with the questionnaire template form and a question identification number field for being associated with the question form; generating a filling result table in the database bottom table, wherein the filling result table is used for loading filling result items of the user data table and comprises a questionnaire identification number field, a target identification number field, a question identification number field and a filling identification number field, wherein the questionnaire identification number field is used for being related to the questionnaire table, the target identification number field is used for being related to the questionnaire target table, the question identification number field is used for being related to the question table, and the filling identification number field is used for being related to the plurality of data content tables; and presenting the user data table using the questionnaire table, the questionnaire object table, the questionnaire template table, the question table, the questionnaire template question table, the filling result table, and the association of the plurality of data content tables.

In an embodiment of the present invention, the filling identifier field of the filling result table is a two-dimensional field set structure, a first field of the two-dimensional field set is used for determining which one of the plurality of data content tables is associated with, and a second field of the two-dimensional field set is used for associating with a record set of the data content table corresponding to the first field.

In an embodiment of the present invention, the plurality of data content tables covers an underlying table in the database having the following characteristics: comprises an identification field, the data type of which is the same as the data type of the second field of the two-dimensional field set.

In an embodiment of the present invention, the object identifier field of the questionnaire object table and the object identifier field of the filling result table are both in a two-dimensional field set structure, a first field of the two-dimensional field set is used for determining which one of the plurality of data content tables is associated with, and a second field of the two-dimensional field set is used for associating with a record set of the data content table corresponding to the first field.

In one embodiment of the present invention, the questionnaire template question form includes, in addition to a question identifier field for association with the question form, another field for setting whether the filling of the question field associated with the question identifier in the user data form is radio or check.

In an embodiment of the present invention, the plurality of data content tables includes a system user table and a system user group table, the answer-filling result table includes an answer-filling identifier field to record a provider of the answer-filling data, the answer-filling identifier field is a two-dimensional field set, a first field of the two-dimensional field set is used for determining a record set associated with the system user table or the system user group table, and a second field of the two-dimensional field set is used for associating with a table corresponding to the first field.

In one embodiment of the present invention, a permission table is generated in the database bottom table for configuring user permissions, where the permission table includes a user identification number field, which is a two-dimensional field set, a first field of the two-dimensional field set is used for determining a record set associated with the system user table or the system user group table, and a second field of the two-dimensional field set is used for associating with a table corresponding to the first field.

In an embodiment of the present invention, the permission table further includes a target identifier field for corresponding to a target for permission application, the target identifier field is a two-dimensional field set structure, a first field of the two-dimensional field set is used for determining which one of the plurality of data content tables is associated with, and a second field of the two-dimensional field set is used for associating with a record set of the data content table corresponding to the first field.

In an embodiment of the present invention, the questionnaire template question table further includes another field and the question identifier field form a two-dimensional field set, a first field of the two-dimensional field set is used for determining which one of the plurality of data content tables is associated with, and a second field of the two-dimensional field set is used for associating with a record set of the data content table corresponding to the first field.

In an embodiment of the present invention, the filling result table includes a field for indicating that the filling result item corresponding to the user data table is the latest filling data or history data.

In an embodiment of the present invention, a data table of the plurality of data tables includes an identification number field and a data field for recording one-dimensional data.

In an embodiment of the present invention, a data table of the plurality of data tables includes an identification number field and two data fields for recording two-dimensional data. And so on, one of the data content tables may include an identification number field and N data fields for recording N-dimensional data.

In an embodiment of the present invention, the database bottom table includes an identification name table, including an identification number field and a name field, where the name field includes contents covering each bottom table in the database bottom table.

In an embodiment of the present invention, the object identifier field and the filling identifier field of the filling result table are both a two-dimensional field set structure, and a first field of the two-dimensional field set is associated with the identifier field of the identifier table, so as to determine to which of the database bottom table the object identifier field or the filling identifier field is associated, and a second field of the two-dimensional field set is used for being associated with a record set of the database bottom table corresponding to the first field.

In an embodiment of the invention, a storage medium stores computer executable program code that, when loaded into an electronic device, causes the electronic device to perform the data connection and presentation method.

In one embodiment of the present invention, a data connection and presentation system comprises: the front-end module is used for receiving user operation and retrieving user data sheet data; a back-end module for generating database instructions according to the user operation; the database module generates and provides user data table data to the back-end module according to the database instruction; the back-end module obtains the user data table data from the database module and transmits the user data table data to the front-end module; wherein the front-end module displays the user data sheet data; the database module generates a plurality of database bottom tables serving as a basic data structure by utilizing the bottom tables of the database module, and the user data table is a link and presentation form of data of the plurality of database bottom tables; the database module generates a plurality of abstract data structures by utilizing the database bottom table, wherein the abstract data structures are used for representing the constituent elements of the user data table and comprise a first dimension block, a second dimension block and a filling content block corresponding to the first dimension and the second dimension of the user data table; wherein each abstracted data structure is associated with one of the plurality of database-underlying tables to present data content of the user data table.

In one embodiment of the present invention, a data connection and presentation device includes: a storage device comprising a database module; a processor that performs the steps of: generating a plurality of basic data structures by using the bottom table of the database module to present a user data table, wherein the user data table is a linking and presenting form of data of the plurality of basic data structures; generating a plurality of abstract data structures by using the bottom layer table, wherein the abstract data structures are used for representing the constituent elements of the user data table and comprise a first dimension block, a second dimension block and a filling content block corresponding to the first dimension and the second dimension of the user data table; wherein the plurality of abstracted data structures are associated with one of the plurality of underlying data structures to generate data content of the user data table; and generating the user data table based on associations of the plurality of underlying data structures and a plurality of abstracted data structures.

Drawings

FIG. 1 is a schematic diagram of a data connection and presentation device and system according to the present invention;

FIG. 2 is a schematic diagram of an embodiment of a data connection and presentation method according to the present invention;

FIG. 3 is a schematic diagram of a two-dimensional positioning structure for associating object data of a questionnaire with different database bottom tables according to the present invention;

FIG. 4 is a schematic diagram of the present invention of filling result data using two-dimensional positioning structures to correlate to different database bottom tables;

FIG. 5 is a diagram illustrating the generation of multiple underlying data structures for rendering a user data table using the underlying tables of the database module in accordance with the present invention.

Detailed Description

The technical content and detailed description of the present invention will now be described with reference to the accompanying drawings:

the data connection and presentation method of the invention is that only a limited number of database bottom tables are established in the database, a plurality of basic data structures are generated, and various user data table presentations with unlimited number can be made through the association of the limited database bottom tables. The invention utilizes a database bottom table with specific design to generate a plurality of abstract data structures for presenting the data of each component block in the user data table, and the abstract data structures comprise a first dimension block, a second dimension block and a filling content block corresponding to the first dimension and the second dimension of the user data table. The data structure of each abstract block is associated with a plurality of underlying data tables to present the user data table contents.

Referring to fig. 1, fig. 1 is a schematic diagram of an electronic device 700 according to an embodiment of the invention for performing the method according to the embodiment of the invention. The embodiments described herein may be implemented using any suitably configured hardware and/or software. As shown in fig. 1, the apparatus 700 includes: transceiver 720, processor 730, memory/storage 740, display 750, camera 760, sensor 770, and Input/Output (I/O) interface 780, connected as shown in fig. 1.

Processor 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Processors may include any combination of general purpose processors and special purpose processors, such as a graphics processor and an application processor (application processor). Processor 730 may be coupled to memory/storage 740 and configured to execute instructions stored in memory/storage 740 to enable various applications and/or operating systems running on the system.

The transceiver 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor of the transceiver 720 may include a communication unit for wired or wireless communication over a network, wherein radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency conversion, and the like.

As used herein, "circuitry" may refer to, participate in, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some implementations, the circuitry of the electronic device or functions associated with the circuitry may be implemented in one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, application circuitry, and/or memory/storage 740 may be implemented together on a system on a chip (SOC).

Memory/storage 740 may be used to load and store data and/or instructions, for example, to a system. Memory/storage in one embodiment may include any combination of suitable volatile memory such as dynamic random access memory (Dynamic Random Access Memory, DRAM) and/or non-volatile memory such as flash memory.

Further, the apparatus may further include a Read Only Memory (ROM) or other static storage device for storing static information and instructions for the processor.

The memory/storage 740 may include, for example, a media disk drive and a removable storage device interface. The media disk drive may include a disk drive or other mechanism that supports fixed or removable storage media, such as a hard disk drive, floppy disk drive, tape drive, optical disk drive, or digital video disk (Digital Video Disc, DVD) drive read or write (R or RW) disk drive, or other removable or fixed media disk drive. The storage medium may include, for example, a hard disk, floppy disk, magnetic tape, compact Disc (CD) or DVD, or other fixed or removable medium that is read by and written to by a media disk drive. The storage medium may include a computer-readable storage medium having particular computer software or data stored therein

In various embodiments, input/output interface 780 may include one or more user interfaces intended to enable a user to interact with the system and/or peripheral component interfaces intended to enable interaction with peripheral components of the system. The user interface may include, but is not limited to, a physical keyboard or keyboard, a touchpad, a speaker, a microphone, and the like. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (Universal Serial Bus, USB) port, an audio jack, and a power interface.

The memory/storage 740 includes the system 100. The system 100 includes a front-end module 110, a back-end module 120, and a database module 130. The database module 130 may be located on the same computer as the back-end module 120 or on another computer. The front-

end modules

110, 120 may contain computer executable program code. The apparatus 700 may transmit the output content of the front end module 110 to the apparatus 701. The output content may be in the form of a web page, and may be operated by the device 701, and the device 701 may receive a user operation and transmit a result of the user operation to the back-end module 120 of the device 700. The back-end module 120 generates database instructions according to the user's operations and transmits the database instructions to the database module 130. The database module 130 queries the underlying table according to the database instructions. The back-end module 120 retrieves the underlying table data from the database module 130 and communicates it to the front-end module 110. The front end module 110 then outputs content to the device 701 for presentation to the user. The device 701 may be a mobile phone, a personal computer or the same or similar device as the device 700.

Fig. 2 shows an embodiment of the data connection and presentation method of the present invention.

The invention provides a data structure, a data connection and a presentation method, which can be used for constructing various user data tables (user data tables) with unlimited quantity in a database (database) such as MySQL, MS SQL and the like by only establishing a limited database bottom table. The flexibility is enough to cope with the requirement of changeable user data table, so that the development and maintenance cost of the information system program can be greatly reduced, and the maintenance cost is not increased along with the increase of the number of the bottom tables of the database as the traditional mode is adopted. By adopting the method, the development speed of constructing the user data table is faster than that of the traditional method.

The present invention proposes a way to break through the dilemma. It is well known that there are a wide variety of molecular species in the world, and each molecule is composed of more basic building blocks, i.e., atoms, arranged and combined. Note that although the number of molecular species is not limited in the tens of millions, the number of atomic species used as a base unit is limited (usually less than 90). Based on similar principles, the present invention provides a database-based table (like an atom) with a limited number, which can be combined to construct a wide variety of user data tables (like a molecule) with an unlimited number. This allows the maintenance costs of the database-underlying tables to be significantly reduced.

When we observe the various data sheet needs of the user, we can see that a user data sheet is just like a questionnaire (questionnaire). For ease of description, the user data sheet is sometimes referred to herein as a questionnaire sheet. The user data table, considered as a questionnaire table, is basically in the form of a matrix (matrix), and has three constituent blocks:

first dimension block: questionnaire target (simply referred to as target)

Second dimension block: question field (simply called question field, or header field)

Questionnaire filling result block (abbreviated as filling result block)

Referring to an example of user data table a:

user data table A

After the user's data table is regarded as a questionnaire structure, the' object 1, objects 2, …, object x 'are the objects of the questionnaire, forming the first dimension block of the user's data table; the question field a, question fields b, …, and question field y are questions to be asked about the target object by the questionnaire, and form a second dimension block of the user data table. The user fills in the "filling result xy" field in the data table filling result block based on the answer corresponding to the "object x" and the "title field y". The "filling results 1a, …, and the filling result xy" are filling results of each object in the first dimension block corresponding to each question in the second dimension block, and form a filling result block of the user data table.

Based on the analysis, the method is different from the traditional method: aiming at the requirement of a user data table, a dedicated database bottom table is directly built in a database for storing the user data table, the invention is based on the detail composition of the user data table after structural analysis, and each basic database bottom table is built in the database by utilizing the database bottom table, as shown in fig. 2, and comprises the following steps: a series of basic data structures of the basic data layer 210 include a data content table 211 (including database bottom tables q_result_text, q_result_int, etc.), a question table q_query 213, an identification name table q_naspace 215, a system user table user 217, a system user group table group 219; and an abstract data structure belonging to the data association layer 220, comprising a questionnaire template table q_template 222, a questionnaire template question table q_template_query 221, a questionnaire object table q_query_target 224, and a filling result table q_result 225; and a questionnaire table q_queronnapire 231 belonging to the user data layer 230.

The database bottom layer table comprises an identification name table q_nano space 215, and comprises an identification number field and a name field, wherein the content of the name field covers all the database bottom layer tables. In order to thoroughly achieve objectification and digitization, a database bottom table is designed on a database: the identification name table q_naspace 215 assigns a unique value number to each database bottom table as an identification number. The attribute field of each record set identifying name table q_naspace 215 includes at least one or more of the following attributes, or other attributes that function the same or similar:

TABLE 1

Wherein the attribute field ID is used as an identification number and is a primary key for identifying the name table q_anamespace 215. In addition to the above example, the attribute field ID is set to an integer type (int), text or other data types may be used, and which type does not affect the use of the field as an identification number. The attribute field name is used to store an identification name. The attribute field pantID then indicates the parent node ID of the identification name. According to practical needs, the identification name table q_naspace 215 may further include these fields: the creatorID is used to record which user the data table was created by, date_create is used to record when it was created, etc., and order is used to record the ordering of the identification names.

The attribute field of the identification name table q_naspace 215 includes at least: an identification number ID, a name, and a parent layer node field pantID, wherein the content of the name field contains various bottom layer tables covering the database. For example, each of the bottom tables and its fields in the previous paragraph can be regarded as an object, and after the object is recorded in the identification name table q_namespace 215, the following exemplary contents can be obtained:

TABLE 2

By analogy, all database bottom table names in the database are stored in the identification name table q_Namespace 215 and are assigned an identification ID. Based on the data, some data positioning of the invention uses a two-dimensional positioning mode, which is a two-dimensional field group structure: (dataType, dataID), wherein dataType is the identification ID of the database bottom table, and dataID is the identification ID of the record set (recordset) in the database bottom table corresponding to dataType. That is, the first field dataType of the two-dimensional field set is used for determining which one of the plurality of data content tables corresponds to which one of the plurality of data content tables is associated, and the second field dataID of the two-dimensional field set is used for associating to the record set of the data content table corresponding to the first field. For example, the two-dimensional location (240,11) means a record set (record) with id=11 in the bottom database table (i.e. q_result_text) with identification number 240, wherein the bottom database table with identification number 240 is q_result_text as known from the identification name table q_nano space 215.

Referring to fig. 2 and 5, the data connection and presentation method of the present invention combines the database bottom tables in the databases, including the base data layer 210, the data association layer 220, the database bottom tables in the user data layer 230, and so on, to finally present the entire contents of the user data table 240 (block 302 of fig. 5).

The question table q_query 213 is a database bottom table, and the basic data of each question field required by the user data table, such as the content of the question, the attribute of the result of filling the question, etc., is stored therein, and the attribute field of each record set at least includes one or more attributes listed as follows, or other attributes with the same or similar functions:

TABLE 3 Table 3

Wherein the attribute field ID is used as an identification number and is a primary key (primary key) of the question table q_query 213. In addition to the above-described integer type of attribute field ID, text or other data types may be used, which type does not affect the use of the field as an identification number. The attribute field name is used to store the text content of the question. The attribute field answerType then reflects which database underlying table the fill corresponding to the question field is associated with. According to practical needs, the question table q_query 213 may further include these attribute fields: the creatorID is used to record which user the data was created by, and the date_create is used to record when it was created, etc.

In the embodiment of the present invention, the combined aspects of the plurality of question fields may be represented by a questionnaire template (template), where the basic data of each questionnaire template, such as a name, is stored in the questionnaire template table q_template 222, and the attribute field of each record set at least includes one or more of the following attributes, or other attributes with the same or similar functions:

TABLE 4 Table 4

Wherein the attribute field ID is used as an identification number and is the primary key of the questionnaire template table q_template. In addition to the above-described integer type of attribute field ID, text or other data types may be used, which type does not affect the use of the field as an identification number. The attribute field name is used to store the template name. According to actual needs, the questionnaire template table q_template may further include these attribute fields: the creatorID is used to record which user the data was created by, and the date_create is used to record when it was created, etc.

Utilizing the database bottom table to generate a questionnaire template question table q_template_query 221 for associating a plurality of question fields in a second dimension block of a user data table represented by the questionnaire table, wherein the questionnaire template question table q_template_query 221 comprises a field template id for associating with the questionnaire template table q_template 222 and a question identification number field query id for associating with the question table q_query 213. The processor establishes a data structure for loading a plurality of questions in a second dimension block 242 of the user data table 240 represented by the questionnaire table q_query 231 using the questionnaire template table q_template 222, the questionnaire template question table q_template_query 221, and the question table q_query 213 in the question-related table group 232. When a certain field template id value is given, the question field query id values in the question template question table q_template_query 221 are question field lists in the question template associated with the field template id value. The questionnaire template question table q_template_query 221 is a database-underlying table whose attribute fields for each record set contain at least one or more of the attributes listed below, or other attributes that function the same or similar:

TABLE 5

Wherein the attribute field ID is used as an identification number and is a primary key of the questionnaire template question form q_template_query. In addition to the above-described integer type of attribute field ID, text or other data types may be used, which type does not affect the use of the field as an identification number. The attribute field template id is associated with the questionnaire template form q_template 222, and the attribute field query id is associated with the question form q_query 213. The attribute field asQrTarget is used for recording whether the problem field corresponding to the attribute field questinid is a target field, i.e. the first dimension block of the user data table. The attribute field multiple answer records whether the answer to the question field is a single answer or allows multiple answers. And the attribute field order records the field display sequence of the problem field corresponding to the attribute field questid in the template corresponding to the attribute field template ID. According to practical needs, the questionnaire template question table q_template_query may further include these attribute fields: the creatorID is used to record which user the data was created by, and the date_create is used to record when it was created, etc.

The questionnaire template question table q_template_query 221 may further include another field and the question field quesitonID to form a two-dimensional field set, where a first field of the two-dimensional field set is used to determine which of the plurality of data content tables is associated with, and a second field quesitonID of the two-dimensional field set is used to associate with a record set of the data content table corresponding to the first field. That is, the questionnaire template question table q_template_query 221 may further include an attribute field, namely, a query type (query type) in addition to the question fields associated with the query id, and the question fields may be associated with each other by forming a two-dimensional location method using the (query type, query id). Using only the attribute field, the querionID is associated with the question table q_querier 213. By adopting the two-dimensional positioning method (query type, query id), the header fields of the user data table can be used as the data of other bottom tables in the database besides the problem table q_query 213. This may make the design of the user data table header field more flexible.

The basic data of each user data table 240, such as name, setup time, etc., is a questionnaire table q_queronnaire 231 recorded in the user data layer 230. The questionnaire table q_queronnaire 231 is a database-underlying table whose attribute fields for each record set contain at least one or more of the attributes listed below, or other attributes that function the same or similar:

TABLE 6

Wherein the attribute field ID is used as an identification number and is a primary key (primary key) of the questionnaire form q_queronnaire. In addition to the above-described integer type of attribute field ID, text or other data types may be used, which type does not affect the use of the field as an identification number. The attribute field name is used to record the name of the user data table. The attribute field template id is associated with the template table q_template to record which template the user data table applies. According to actual needs, the questionnaire table q_queronnaire may further include these attribute fields: the creatorID is used to record which user the user data table was created by, date_create is used to record when it was created, etc.

The questionnaire form q_queronnaire 231 contains an attribute field template id for association to the questionnaire template form q_template 222. Based on the questionnaire template form q_template 222, a user data table can be presented accordingly, the details of which include: the attribute field template ID corresponding to the user data table in the questionnaire table q_queronnaire 231 is used for knowing which template is used for the user data table; further, the question template q_template_query 221 can obtain which of the question fields contained in the template, so that each header field in the second dimension block of the user data table can be displayed accordingly.

The user data table is presented based on a template, and the design has the following advantages: it is quite easy to make multiple user data tables with a uniform header field structure, as long as the template id values of these user data tables are the same. Another benefit is that once the user data table header field structure has an adjustment requirement, such as: the header fields need to be increased or decreased, the sequence in which the header fields are displayed needs to be adjusted, and the like, so long as the configuration corresponding to the template in the questionnaire template question table q_template_query 221 is adjusted, all the header field structures of the user data table applying the template are updated.

As described above, a plurality of user data tables having the same header field structure can be easily made by applying a template. Based on this feature, there may be practically the following applications: the template can be used to create a user data table for the test area and the formal area, respectively. The user data list in the test area is specially used for the user to test. After the user passes the test, the user data table in the formal area can be provided for the user to use formally. Conventionally, for two systems, i.e., a "test area" and a "formal area" which are often the same set of program codes, in the case of a website system, two different websites are usually used, and the user has to switch between the websites, which is troublesome in operation. The invention provides a mode that: the effect of testing the zone data table is also allowed for the formal zone system, which is not easily achieved by conventional design practice.

The present invention is in fact a linking and presentation form of data based on the plurality of underlying data structures, for example the front end module 110 presents the user data table 240 in the device 701. Referring to fig. 5, first, the underlying data structures (e.g., tables 211, 213, 215, 217, and 219) in the underlying data layer 210 are generated using the database-underlying tables (block 302). The plurality of abstract data structures (e.g., tables 221-225) in the data association layer 220 are generated using database-based tables to represent the constituent blocks of the user data table 240, including the first dimension block, the second dimension block, and the filler content blocks of the components corresponding to the first and second dimensions of the user data table 240 (block 304). In the user data table 240 in each user data layer 230, each abstract data structure of the data association layer 220 associates one of the plurality of base data structures in the base data layer 210 to produce the actual content of the constituent blocks of the user data table 240 (block 306). The user data table 240 is generated based on the association of the plurality of underlying data structures with a plurality of abstracted data structures (block 308). The front-end module 110, the back-end module 120 and the database module 130 can implement the data connection and presentation method of the present invention. It will be appreciated that the abstract data structure is an underlying table for abstract purposes and the underlying data structure is an underlying table for purposes of materializing the record of the actual content.

The back-end module 120 and the database module 130 generate the corresponding user data table 240 by using the data content tables 211, the filling result table q_result 225, the questionnaire object table q_query_target 224, the question table q_query 213, the questionnaire template question table q_template_query 221, and the questionnaire table q_query 231.

In the data connection and presentation method of the present invention, the processor 730 uses the database-underlying table to generate the questionnaire table q_query naire 231. The database bottom table contains a plurality of data content tables 211. The questionnaire form q_query 231 is itself an abstract data structure of the abstract user data layer 230 representing the processor-generated user data table 240.

The processor uses the database underlying table to build a data structure for loading a plurality of objects in a first dimension block 241 of the user data table 240 represented by the questionnaire table q_queronnaire 231, referred to as a questionnaire object table q_queronnaire_target 224. The questionnaire object table q_query_target 224 is a database-based table, and the attribute field of each record set at least contains one or more attributes listed below, or other attributes that function the same or similar:

TABLE 7

Wherein the attribute field ID is used as an identification number and is a primary key (primary key) of the questionnaire object table q_query_target 224. In addition to the above-described integer type of attribute field ID, text or other data types may be used, which type does not affect the use of the field as an identification number. The attribute field QrID is used to associate with the questionnaire form q_queronnapire 231. The attribute field (targetType, targetID) forms a two-dimensional location structure for association to any underlying database table within the database in addition to the data associated with the data content table 211. The attribute field order is used for recording the display sequence of the target object data associated with the attribute field (targetType, targetID) in the user data table associated with the attribute field qrdid. According to actual needs, the questionnaire table q_queronnaire 231 may further include these attribute fields: the creatorID is used to record which user the user data table was created by, date_create is used to record when it was created, etc.

The processor uses the database underlying table to build a data structure for loading the fill field 243 of the user data table 240 represented by the questionnaire table q_queronnaire 231. In other words, a data structure for loading the filling content of the user data table represented by the questionnaire table is established by using the database bottom table, which is called a filling result table, wherein the filling result table has a plurality of fields including a target field for being associated with the questionnaire target table q_query_target 224, a question field for being associated with the question table q_query 213, and a filling field for being associated with the plurality of data content tables 211. The filling result of the user data table is stored in the filling result table q_result 225 of the questionnaire. The fill result table q_result 225 is a database underlying table, and the attribute field of each record set at least contains one or more attributes listed below, or other attributes that function the same or similar:

TABLE 8

Wherein the attribute field ID is used as an identification number and is the primary key of the filling result table q_result 225. In addition to the above-described integer type of attribute field ID, text or other data types may be used, which type does not affect the use of the field as an identification number. The attribute field QrID corresponds to the questionnaire table q_queronnapire 231, indicating to which user data table the filler content belongs. The attribute field (targetType, targetID) correlates which target content the filler content corresponds to by two-dimensional positioning. The attribute field query id is associated with the question table q_query 213 to respond to which question field the response content corresponds to. The attribute field (answerType, answerID) correlates out the filler content through two-dimensional positioning. The attribute field (creatotype), through two-dimensional localization, associates who the filled content is established. The filling result table includes a field active to indicate that the data is the latest filling data or the history data, for example, active=1 indicates the latest data, active= -1 indicates the history data, and active=0 indicates the deletion. The attribute field date_create represents the data setup time. The attribute field date_update indicates a data update time.

In practice, the filling content of each filling field 243 in the user data table is not limited to text, integer, floating point number, date, menu, and other data types, which are different types of basic modules. The database of the present invention is thus designed with a series of data content tables 211 for storing various types of filler content, respectively. Each of the plurality of data tables 211 includes an identification number field and a data field for recording one-dimensional data, and the data field of the data table of the plurality of data tables may be a number, a text, or a date. The data table 211 may also include a plurality of data fields for recording multi-dimensional data. For example, the data table 211 contains two date-type data fields for recording data of time interval type. The data table of contents further includes a field for corresponding to a class of values of the data field. The series of data content tables 211 are all database bottom tables, including:

q_result_text table: the attribute field of each record set contains at least one or more attributes listed below, or other attributes that function the same or similar:

TABLE 9

In addition to the above example, the field ID may be in the form of text or other data, which does not affect the use of the field as an identification number. The attribute field value is used for storing the content of the text class filled by the user.

q_result_int table: the attribute field of the filling content for storing integer class at least comprises the following:

table 10

In addition to the above example, the field ID may be in the form of text or other data, which does not affect the use of the field as an identification number. The attribute field value is used to store the content of the integer class filled by the user.

q_result_float table: the attribute field of each record set used for storing the filling content of the floating point digital class at least comprises one or more attributes listed below, or other attributes with the same or similar functions:

TABLE 11

In addition to the above example, the field ID may be in the form of text or other data, which does not affect the use of the field as an identification number. The attribute field value is used to store the content of the floating point class filled by the user.

q_result_date table: the attribute field of each record set for storing the fill-in content of the date class contains at least one or more attributes listed below, or other attributes that function the same or similar:

table 12

In addition to the above example, the field ID may be in the form of text or other data, which does not affect the use of the field as an identification number. The attribute field value is used to store the contents of the date class filled by the user.

The four types of filling result tables are only examples, if the filling content has other types of data, such as the types of "expense" data and "date zone" data containing the coin and the amount, a corresponding database bottom table is established to store the data of the types, and a corresponding identification name and identification ID are established in the identification name table q_nano space 215, so that two-dimensional positioning can be associated. Note that, no matter how many user data tables are required, the types of the filling data are practically different, so that the filling result tables only need to be built, and the number of the filling result tables to be built is very much smaller than that of the user data tables.

Referring to fig. 3, the attribute fields (targetType, targetID) in the questionnaire object table q_queronnapire_target 224 and (targetType, targetID), (answerType, answerID), (creatorType, creatorID) in the filling result table q_result 225 all form a two-dimensional location structure. The filling result table q_result 225 includes a two-dimensional field set structure, wherein a first field of the two-dimensional field set is used for determining which one of the plurality of data content tables corresponds to, and a second field of the two-dimensional field set is used for associating a record set of the data content table corresponding to the first field. The first field corresponds to an identification number field of the identification name table, and the second field corresponds to a record set in a data content table of the plurality of data content tables to which the identification number field corresponds. The first two-dimensional field set (targetType, targetID) of the filling result table q_result 225 is associated with the two-dimensional field set of the questionnaire object table, and corresponds to a plurality of object data in the first dimension of the user data table represented by the questionnaire table, and the second two-dimensional field set (answerType, answerID) of the filling result table corresponds to filling content data of the user data table represented by the questionnaire table. The filling result table includes a third two-dimensional field set (creatorType, creatorID) for associating to the system user table user 217 or the system user group table group 219 to record the executor of the filling result. By the multiplexer module 310, a two-dimensional location structure (dataType, dataid) can be associated with virtually any database-based table in the database, and is not limited to the data-content table 211. The database module 130 may implement the multiplexer module 310 using the identification name table q_naspace 215. For a two-dimensional location structure (dataType, dataid), different dataType values represent the database underlying tables to be associated with, and dataid values correspond to the identification ID values of the database underlying tables associated with the dataType.

Because of the use of two-dimensional localization, the target (targetType, targetID) can be associated with data in virtually any database-based table, as well as the fill value (answerType, answerID). The infill (creator type, creator id) also adopts a two-dimensional positioning method, so that the effect of "the infill is a group" can be easily achieved besides the expression of "the infill is a person". For example, when the filler (creatotype, createid) in the filling result table q_result 225 is (100, 10), reference is made to the identification name table q_nano space 215, which indicates that the user with the identification number=10 in the database bottom table "user" with the identification number=100 is the filler. As another example, when the populator (creatotype, createid) is (110, 2), this indicates that the group with identification number=2 in the database-underlying table "group" with identification number=110 is the data provider.

Referring to fig. 4, the fill result table q_result 225 fields answerID and answerType are associated by a multiplexer module 320 to the data within the series of data content tables 211, such as q_result_text, q_result_int, q_result_float, q_result_date, and q_result_time. The database module 130 may utilize the identification name table q_naspace 215 to implement the multiplexer module 320.

In general, to display a specific user data table, taking a specific user data table with id=10 as an example, the detailed procedure is as follows:

the template ID of the particular user data table is looked up from table q_queronnaire-i.e., the template ID field of table q_queronnaire for id=10 of the pen data, and then associated to table q_template to look up those problem fields (header fields) within the template, which would constitute a second dimension block field (e.g., 242) of the user data table (e.g., user data table 240). All objects of the user data table are looked up from the table q_query_target, which will constitute the first dimension block field (e.g., 241) of the user data table.

Based on the data, including user data table ID, header fields of the user data table, objects of the user data table, etc., and finally associating the user data table ID, header fields of the user data table, objects of the user data table, and finally associating the user data table ID, header fields of the user data table, and the user data table, each of the user data table, and finally associating the user data table to a corresponding filling result table q_result to obtain actual filling contents according to a two-dimensional positioning (answerType, answerID) of each filling content part, and further associating the filling contents to tables q_result_text, q_result_int, q_result_float, or q_result_date, etc.

The method is applicable to any user data table, so that no matter how many user data tables are added, the number of the bottom tables used by the database is the same, and the bottom tables are not added all the time like the traditional method. Also, because the user data table is applicable to any user data table, the interface program codes of the user data table can be used commonly, and the corresponding program codes are required to be designed for different user data tables unlike the conventional method, so that the maintenance workload of the system program codes can be reduced.

In contrast, after each field of the conventional underlying table of the database is set, when an adjustment such as adding a field is needed, IT personnel needs to adjust the field structure of the underlying table. Another advantage of the method of the present invention is that only the content of the questionnaire template question table q_template_query is required to be adjusted, and the data structure of each underlying table of the database is not required to be adjusted, so that the required system maintenance workload is reduced greatly, for example, after the number of fields is increased or decreased according to the underlying table structure of the database in the conventional manner, all the program code portions related to the fields in each program need to be correspondingly adjusted; the mode of the invention can reduce the situation that the joint needs to be adjusted.

The invention has the effect of original data editing history (log). Once the fields in the conventional data table are updated, the original values are not covered. In order to record the history, it is conventional practice to create a separate log table for recording, but in conjunction, it is necessary to design and maintain the associated program code corresponding to the log table. The invention can achieve the effect of programming history records by filling the active field in the result table q_result without designing and maintaining an additional independent log table and corresponding program codes.

When a certain data cell fill in the user data table is modified, the active field of the record set record of the fill corresponding to the fill result table q_result corresponding to the fill is set to-1 to indicate that the history has been obtained. The active field of q_result corresponding to the latest fill is set to 1 to indicate the current value. The record sets corresponding to a field (a query id) of a target object (a target type, a target id combination) of a user data table (a target QrID) are called out from the filling result table q_result to be the repair history of the data grid of the user data table, wherein active=1 is the current filling value, active= -1 is the past filling value, and the user can further know from fields such as creatorID, creatorType, date _create and the like when the previous filling is performed.

In the aspect of data grid filling and single selection check, in the data structure provided by the invention, the filling result corresponding to a field (a query id) of a certain target object (a certain targetType, a targetID combination) of a certain user data table (a certain QrID) is allowed to be checked by more than one stroke, namely, each data grid can be checked on the first day. If the data grid is to be presented as a single selection to the user, the surface limitation is only made on the program interface, so that the data grid with the filled content is not allowed to continue to newly add the filled content. The "radio/check" of each field of the user data table is set as a multi-answer threshold in the questionnaire template question table q_template_query, and the field can be changed from radio to check only by changing the multi-answer value from 0 to 1, so that the surface restriction is released on the program interface, and the user is allowed to continue to newly fill the data table. Therefore, the invention does not have the difficulties of adjusting the underlying data structure, adjusting the corresponding program code and the like caused by the conventional "radio selection and check".

Rights management is a necessary mechanism for an information system used by multiple persons. By two-dimensional positioning of this design, only one database-underlying table may be used: the permission table global_permission can cover various permission management and control settings in the system. Through a two-dimensional positioning mode, various authority management and control settings in the system can be recorded in the same database bottom table: on the permission table global_permission, the system maintenance cost can be reduced.

For different data in an information system, such as personnel data, project data, customer data, etc., authority control is often required to set the authority of the user for reading, writing, etc. Conventionally, in the case of database bottom tables, a database bottom table is built for each of personnel data, project data, and customer data to record corresponding authority settings, for example:

database underlying table permission_scope: permission setting for storing personnel data.

Database underlying table permission_project: permission setting for storing the item data.

Database underlying table permission_customer: the authority setting is used for storing the client data.

This way, it is apparent how many data table objects there are, and an equal amount of database underlying tables would need to be built, which would result in an increase in system maintenance costs.

The invention uses a two-dimensional positioning mode to achieve the purpose of using a single database bottom table: the permission table global_permission can store the effects of various permission management and control settings in the system. Each record set of the permission table global_permission contains at least one or more attributes of the following fields, or other attributes that function the same or similar:

TABLE 13

The attribute field ID is an identification number, and is a primary key of the permission table global_permission, and may be in a numeric form or a text form in practice. The attribute fields p_read, p_write represent the "read", "write" permission settings, respectively. The (targetType, targetID) forms a two-dimensional location that can be associated with any set of records in any database-underlying table within the database. The (userType, userID) also forms a two-dimensional location that is associated with the system user table user 217 or the system user group table group 219, i.e., to "person" or "group", depending on the value of the userType. Through the two-dimensional positioning data structure, the authority control setting of various targets can be recorded by using only one database bottom table global_permission. The attribute field date_create, date_update records the creation and update times, respectively.

The permission table global_permission may further add an attribute field as required, for example: p_message: representing various other rights fields such as "manage" rights; parentID: the identification number representing the authority setting of the parent layer is used for indicating which authority setting the present authority setting inherits.

The storage medium of the present invention stores computer executable program code that, when loaded into an electronic device, causes the electronic device to perform the data connection and presentation method.

The method provided by the invention can construct the user data table which has elasticity and meets the random and various requirements of users under the condition of using a limited number of database bottom tables. The maintenance cost of the system can be greatly reduced, and the maintenance cost is not increased in proportion to the increase of the number of the user data sheets as in the traditional mode; the speed efficiency of constructing the user data table is also faster than in conventional approaches.

It will be apparent to those skilled in the art that various changes can be made in the embodiments according to the invention without departing from the spirit of the invention. It is therefore evident that the particular embodiments disclosed are not limited thereto, but rather are intended to cover modifications as fall within the spirit and scope of the present invention as defined by the appended claims.

Claims

1. A method of data connection and presentation, comprising:

generating a questionnaire form in the database bottom form for loading a user data form content representing a user data form;

Generating a complex data content table in the database bottom table, wherein the complex data content table is used for loading various data contents;

generating a questionnaire object table in the database bottom table for loading data items of a plurality of objects in a first dimension block of the user data table, wherein the questionnaire object table comprises a field for being associated with the questionnaire table and a target object identification number field for being associated with data contents in the plurality of data content tables;

generating a questionnaire template form in the database bottom form, wherein the questionnaire form comprises a field for being related to the questionnaire template form;

generating a problem table in the database bottom table;

generating a questionnaire template question form in the database bottom form for being associated with a plurality of question fields in a second dimension block of the user data form, wherein the questionnaire template question form comprises a template identification number field for being associated with the questionnaire template form and a question identification number field for being associated with the question form;

generating a filling result table in the database bottom table, wherein the filling result table is used for loading filling result items of the user data table and comprises a questionnaire identification number field, a target identification number field, a question identification number field and a filling identification number field, wherein the questionnaire identification number field is used for being related to the questionnaire table, the target identification number field is used for being related to the questionnaire target table, the question identification number field is used for being related to the question table, and the filling identification number field is used for being related to the plurality of data content tables; and

And presenting the user data table by using the questionnaire table, the questionnaire target table, the questionnaire template table, the question table, the questionnaire template question table, the filling result table and the association of the plurality of data content tables.

2. The method of claim 1, wherein the filling identifier field of the filling result table is a two-dimensional field set structure, a first field of the two-dimensional field set is used for determining which one of the plurality of data content tables is associated with, and a second field of the two-dimensional field set is used for associating with a record set of the data content table corresponding to the first field.

3. The data connection and presentation method of claim 2, wherein the plurality of data content tables comprise an underlying table in the database having the following characteristics: comprises an identification field, the data type of which is the same as the data type of the second field of the two-dimensional field set.

4. The method of claim 2, wherein the object identifier field of the questionnaire object table and the object identifier field of the filling result table are both two-dimensional field set structures, wherein a first field of the two-dimensional field set is used for determining which one of the plurality of data content tables is associated with, and a second field of the two-dimensional field set is used for associating with a record set of the data content table corresponding to the first field.

5. The data connection and presentation method of claim 1 wherein the questionnaire template question form includes, in addition to a question identifier field for association with the question form, another field for setting whether a fill of a question field associated with the question identifier in the user data form is a radio or a check.

6. The method of claim 2, wherein the plurality of data content tables includes a system user table and a system user group table, the filling result table includes a filler identifier field for recording a provider of the filling data, the filler identifier field is a two-dimensional field set, a first field of the two-dimensional field set is used for determining a record set associated with the system user table or the system user group table, and a second field of the two-dimensional field set is used for associating with a record set of the table corresponding to the first field.

7. The method of claim 6, wherein a permission table is generated in the database bottom table for configuring user permissions, the permission table including a user identification number field which is a two-dimensional field set, a first field of the two-dimensional field set being used for determining a record set associated with the system user table or the system user group table, and a second field of the two-dimensional field set being used for associating with a record set of the table corresponding to the first field.

8. The method of claim 7, wherein the rights table further comprises a target identifier field for corresponding to the target of the rights application, the target identifier field having a two-dimensional field set structure, a first field of the two-dimensional field set being used for determining which one of the plurality of data content tables is associated with, and a second field of the two-dimensional field set being used for associating with a record set of the data content table corresponding to the first field.

9. The method of claim 2, wherein the questionnaire template question form further comprises another field and the question identifier field form a two-dimensional field set, a first field of the two-dimensional field set being used to determine which one of the plurality of data content forms is associated with, and a second field of the two-dimensional field set being used to associate with a record set of the data content form corresponding to the first field.

10. The method of claim 1, wherein the fill result table includes a field indicating whether the fill result item corresponding to the user data table is the latest fill data or history data.

11. The method according to claim 1, wherein a data table of the plurality of data tables includes an identification number field and a data field for recording one-dimensional data.

12. The method of claim 1, wherein one of the plurality of data tables includes an identification number field and two data fields for recording two-dimensional data.

13. The method of claim 1, wherein the database bottom tables comprise an identification name table comprising an identification number field and a name field, wherein the name field comprises a content covering each of the database bottom tables.

14. The method of claim 13, wherein the object identifier field and the filling identifier field of the filling result table are both in a two-dimensional field set structure, wherein a first field of the two-dimensional field set is associated with an identifier field of the identifier table, so as to determine which of the database bottom table the object identifier field or the filling identifier field is associated with, and wherein a second field of the two-dimensional field set is used for associating with a record set of the database bottom table corresponding to the first field.

15. A storage medium storing computer executable program code which, when loaded into an electronic device, causes the electronic device to perform the data connection and presentation method of claims 1-14.

16. A data connection and presentation system, comprising:

the front-end module is used for receiving user operation and retrieving user data sheet data;

a back-end module for generating database instructions according to the user operation; and

the database module generates and provides user data table data to the back-end module according to the database instruction;

the back-end module obtains the user data table data from the database module and transmits the user data table data to the front-end module;

wherein the front-end module processes the user data sheet data into a data format suitable for presentation to a user;

the database module generates a plurality of database bottom tables serving as a basic data structure by utilizing the bottom tables of the database module, and the user data table is a link and presentation form of data of the plurality of database bottom tables;

The database module generates a plurality of abstract data structures by utilizing the database bottom table, wherein the abstract data structures are used for representing the constituent elements of the user data table and comprise a first dimension block, a second dimension block and a filling content block corresponding to the first dimension and the second dimension of the user data table;

wherein each abstracted data structure is associated with one of the plurality of database-underlying tables to present data content of the user data table.

17. A data connection and presentation device, comprising:

a storage device comprising a database module;

a processor that performs the steps of:

generating a plurality of basic data structures by using the bottom table of the database module to present a user data table, wherein the user data table is a linking and presenting form of data of the plurality of basic data structures;

generating a plurality of abstract data structures by using the bottom layer table, wherein the abstract data structures are used for representing the constituent elements of the user data table and comprise a first dimension block, a second dimension block and a filling content block corresponding to the first dimension and the second dimension of the user data table;

Wherein the plurality of abstracted data structures are associated with one of the plurality of underlying data structures to generate data content of the user data table; and

the user data table is generated from associations of the plurality of underlying data structures with a plurality of abstracted data structures.