TWI860073B - Data processing system - Google Patents

Abstract

A data processing method is used for a data processing system processing an upload data. The data processing system comprises a relational database and a NoSQL database, and the upload data comprises a data content and a table name. The data processing method comprises determining a structure type of the upload data according to the data content; determining a first table of a first database according to the structure type, the data content and the table name of the upload data; and storing the upload data in the first table of the first database. The first database is the relational database or the NoSQL database.

Description

Data processing system

The present invention refers to a data processing system, in particular, a data processing system that can automatically perform database selection, data structure adjustment and data transfer based on data content.

With the digitization of information and the popularization of the Internet, all fields have the need to access databases through application programming interfaces (APIs). In order to meet the diversification of data applications, the types of databases have also flourished. Today, mainstream databases can be mainly divided into two types: relational databases and non-relational databases (NoSQL). Relational databases such as Oracle, MySQL, and SQL Server usually store data through multiple tables. The data in the tables and the tables have pre-defined and strictly structured relationships. Non-relational databases such as MangoDB and Redis are different from traditional relational databases. They do not need to use a fixed table format to store data. Data models can be defined at will, and they have better flexibility and scalability. The technology of accessing databases through APIs allows users to access databases based on the definition of APIs without having to possess database-related expertise when faced with multiple database types and diverse database technologies.

However, generally speaking, before uploading data, users still need to confirm their needs with database technicians. Database technicians will select a database that meets the user's actual needs, plan the corresponding data relational architecture, and establish the corresponding database table. In addition, they must provide a customized API for accessing data. After the database and database table are set up and a certain amount of data is stored, if there is a need to change the database or table structure in the future, database technicians are still required to transfer the database and adjust the data structure. With the increasing amount of information, database technicians will face considerable manpower burdens and database change costs. This problem is particularly serious when using a relational database. However, changing data content in response to changing needs has always been an unavoidable problem in this field. Therefore, it is urgent to establish an automatic identification method that can automatically adjust the database and table based on the data content uploaded by the user to save manpower and reduce costs.

Therefore, the main purpose of the present invention is to provide a data processing system that can automatically identify the content of data, so as to improve the shortcomings of the known technology.

The present invention discloses a data processing system for processing an uploaded data, wherein the uploaded data includes a data content and a data table name. The data processing system includes a relational database, a non-relational database, a data processing unit and a storage unit. The data processing unit is coupled to the relational database and the non-relational database to execute a program code. The storage unit is coupled to the data processing unit to store the program code to instruct the processing unit to execute a data processing method. The data processing method includes determining a data type of the uploaded data according to the data content; determining a first data table of a first database according to the data type, the data content and the data table name of the uploaded data; and storing the uploaded data in the first data table of the first database. The first database is the relational database or the non-relational database.

100:API

110: User

120: Database

130: Data

20:Data processing system

200:API

210: Relational database

212: Non-relational database

220: Data processing unit

230: Storage unit

232:Program code

240: Upload data

30: Data processing flow

300~308: Steps

40: Data type determination process

400~416: Steps

50, 60: Process

500~510, 600~618: Steps

70: Database migration process

700~710: Steps

80:Data table migration process

800~810: Steps

Figure 1 is a diagram showing a user accessing a database through an API.

Figure 2 is a schematic diagram of a data processing system according to one embodiment of the present invention.

Figure 3 is a schematic diagram of the data processing flow of one embodiment of the present invention.

Figure 4 is a schematic diagram of the data type determination process of one embodiment of the present invention.

Figure 5 is a schematic diagram of the process of one embodiment of the present invention.

Figure 6 is a schematic diagram of the process of one embodiment of the present invention.

Figure 7 is a schematic diagram of the database migration process of one embodiment of the present invention.

Figure 8 is a schematic diagram of the data table transfer process of one embodiment of the present invention.

Certain terms are used in this specification and subsequent patent applications to refer to specific components. A person with ordinary knowledge in the field should understand that hardware manufacturers may use different terms to refer to the same component. This specification and subsequent patent applications do not use differences in names as a way to distinguish components, but rather use differences in components' functions as the criteria for distinction. The term "including" mentioned throughout the specification and subsequent patent applications is an open term and should be interpreted as "including but not limited to".

Please refer to Figure 1, which is a schematic diagram of a user accessing a database through an API. As shown in Figure 1, a user 110 sends a request to access a database 120 through an API 100 and obtains a response from the database 120. In this process, the user 110 only needs to carry the data 130 that needs to be stored in the database 120 in the request according to the specification of the API 100, without knowing the type of the database 120 or having professional knowledge related to the database 120. However, in general, the API 100 and the database 120 need to be carefully planned by database technicians according to user needs and implemented in a form that is easy to access. Once the system is online, it is difficult to change. Data 130 may be a structured table, or may be various multimedia data, or may be a data set with any structure. In response to changes in actual needs, the structure and content of data 130 may need to be updated at any time. In this case, database technicians need to comprehensively consider the old data structure stored in database 120 and the needs of new data 130, and update the table structure, table associations, etc. in database 120 and the content of API 100 accordingly. Under specific needs, data migration between different types of databases must also be considered. This update process will consume considerable manpower and material resources.

In response to the above problems, please refer to FIG. 2, which is a schematic diagram of a data processing system 20 of an embodiment of the present invention. As shown in FIG. 2, the data processing system 20 includes a relational database 210, a non-relational database 212, a data processing unit 220, and a storage unit 230. The relational database 210 can be any kind of relational database such as Oracle, MySQL, SQL Server, etc., but is not limited thereto. The non-relational database 212 can be any kind of non-relational database such as MangoDB, Redis, etc., but is not limited thereto. The data processing unit 220 can be a general-purpose processor, a microprocessor, an application-specific integrated circuit (ASIC), etc., or a combination thereof. The storage unit 230 can be any data storage device for storing a program code 232, and the data processing unit 220 reads and executes the program code 232. For example, the storage unit 230 can be a read-only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, an optical data storage device, and a non-volatile storage unit, but is not limited thereto.

As shown in FIG. 2, the data processing system 20 provides an API 200 for the user 110 to access an uploaded data 240, and the uploaded data 240 must at least include a table name and its data content. The data processing system 20 executes a data processing method based on the uploaded data 240 uploaded by the user 110, and thereby determines the database and table suitable for storing the uploaded data 240, thereby achieving the purpose of automatically storing data. As shown in FIG. 3, the data processing method of the embodiment of the present invention can be summarized as a data processing process 30 and compiled into a program code 232, which includes the following steps:

Step 300: Start.

Step 302: Determine a data type of the uploaded data 240 according to the data content of the uploaded data 240.

Step 304: Determine a first data table of a first database according to the data type, data content and data table name of the uploaded data 240.

Step 306: Store the data content of the uploaded data 240 in the first data table of the first database.

Step 308: End.

According to process 30, in step 302, the data processing system 20 first determines the data type of the uploaded data 240 according to the data content. Then, in step 304, the data processing system 20 searches the relational database 210 and the non-relational database 212 according to the table name of the uploaded data 240 to determine whether relevant data has been stored in the data processing system 20, and accordingly determines the first database and the first table for finally storing the uploaded data 240. Finally, in step 306, the data processing system 20 stores the data content of the uploaded data 240 in the first table of the first database determined in step 304.

Specifically, in step 302, the data processing system 20 first determines the data type of the uploaded data 240 according to the structure of the data content. The data type of the uploaded data 240 can be divided into two types: structured data type and unstructured data type. Data of structured data type is suitable for storage in the relational database 210, while data of unstructured data type is suitable for storage in the non-relational database 212. The embodiment of the present invention further determines based on this information to determine the final storage method of the uploaded data 240. In one embodiment, the data processing system 20 can receive a database specified parameter specified by the user 110 while receiving the uploaded data 240. The database-specified parameter can specify that the data is stored in a relational database 210 or a non-relational database 212. Please refer to FIG. 4, which is a data type determination process 40 for performing data type determination in step 302, which includes the following steps:

Step 400: Start.

Step 402: Determine whether the database specified parameter is true? If so, execute step 406; if not, execute step 404.

Step 404: Determine whether the data content of the uploaded data 240 meets a first determination condition? If yes, execute step 410; if no, execute step 414.

Step 406: Determine whether the database-specified parameter indicates the use of a relational database or a non-relational database? If a relational database is used, execute step 408; if a non-relational database is used, execute step 414.

Step 408: Determine whether the data content of the uploaded data 240 meets a first determination condition? If yes, execute step 410; if no, execute step 412.

Step 410: Determine that the data type of the uploaded data 240 is a structured data type.

Step 412: Return an error message of "data structure does not match".

Step 414: Determine that the data type of the uploaded data 240 is an unstructured data type.

Step 416: End.

According to the process 40, the data processing system 20 can determine the data structure of the uploaded data 240 stored in the data processing system 20 according to the data content of the uploaded data 240 and the database specified parameters. The data processing system 20 first determines whether the user 110 has set the database specified parameters (step 402). If the user 110 has not uploaded the database specified parameters, the data processing system 20 automatically determines the data type of the uploaded data 240 according to whether the data content of the uploaded data 240 meets a first determination condition (step 404). When the first judgment condition is met, the data processing system 20 determines that the data type of the uploaded data 240 is a structured data type (step 410); when the first judgment condition is not met, the data processing system 20 determines that the data type of the uploaded data 240 is an unstructured data type (step 414). On the other hand, when the user 110 has a database-specified parameter for uploading (the database-specified parameter value is true), the data type of the uploaded data 240 needs to be further determined based on the database-specified parameter and the data content of the uploaded data 240 (step 406). If the database-specified parameter indicates that a relational database is used, it is necessary to determine whether the data content of the uploaded data 240 meets the first judgment condition (step 408). When the data content of the uploaded data 240 meets the first judgment condition, the data processing system 20 determines that the data type of the uploaded data 240 is a structured data type (step 410); when the data content of the uploaded data 240 does not meet the first judgment condition, the data processing system 20 needs to return an error message to the user 110 and prompt that the specified database type does not match the data structure (step 412). If the database specified parameter indicates the use of a non-relational database, the data processing system 20 can directly determine that the data type of the uploaded data 240 is a non-structured data type (step 414).

In the process 40, the data processing system 20 determines the data format and data type of the uploaded data 240 according to whether the data content of the uploaded data 240 satisfies the first judgment condition. In one embodiment, the first judgment condition may include the data content structure of the uploaded data 240, which is composed of a column name and a row representing a data value group, and all data types of the data corresponding to each column must be consistent, and the data type of each column is one of a floating point number (including an integer) (Float), a date and time (Datetime), and a string (String). When the above conditions are met, the data processing system 20 can determine that the data content of the uploaded data 240 is a structured data type, otherwise it is an unstructured data type. Compared with the unstructured data type, the structured data type has strict format restrictions and can be stored in the relational database 210 or the non-relational database 212. Compared with the structured data type, the non-structured data type has a looser structure and can only be stored in the non-relational database 212. When the user 110 does not set the database specified parameter, the data processing system 20 can directly determine the data type of the uploaded data 240 according to the first judgment condition. When the user 110 sets the database specification parameter, the specified database type and the data content of the uploaded data 240 must be considered at the same time to see if they meet the first judgment condition. If the data content of the uploaded data 240 cannot meet the first judgment condition, it cannot be stored in the relational database 210 with a more stringent data structure. Therefore, if the user 110 specifies to use the relational database 210 under this condition, the data processing system 20 needs to return an error message and terminate the process.

Regarding the method of determining the data type in the first judgment condition, existing software or packages can be used, but are not limited to this. For example, when using Python to determine the data type, the "dateutil.parser.parse" package can be used to check the date and time type, the "float()" function can be used to check the floating point type, and the "isinstance(input,str)" function can be used to check the string type. When using R language to determine the data type, "as.Date" can be used to check the date and time type, "float.TryParse(input,out valid_float)" can be used to check the floating point type, and "is.character()" can be used to check the string type. People with ordinary knowledge in this field can use appropriate tools to determine the data type according to actual needs, but are not limited to this.

According to process 30, in step 304, the data processing system 20 determines the first database and the first data table for storing the uploaded data 240 according to the data type, data content and data table name of the uploaded data 240. In this step, the data processing system 20 must first search the relational database 210 and the non-relational database 212 according to the data table name of the uploaded data 240 to determine whether there is related data stored in the data processing system 20, and accordingly determine the first database and the first data table for finally storing the uploaded data 240.

Please refer to Figure 5, which shows a process 50 for determining a first database and a first data table for actually storing the uploaded data 240 according to the data type of the uploaded data 240 when the data processing system 20 fails to find a data table with a data table name matching the uploaded data 240 in the relational database 210 and the non-relational database 212. In this case, the data processing system 20 does not store data related to the uploaded data 240, and the first database and the first data table can be automatically determined directly according to the data type of the uploaded data 240 determined by the data type determination process 40 in step 302. Process 50 includes the following steps:

Step 500: Start.

Step 502: Determine the data type of the uploaded data 240. If it is a structured data type, execute step 504; if it is an unstructured data type, execute step 506.

Step 504: Determine that the first database is the relational database 210.

Step 506: Determine that the first database is a non-relational database 212.

Step 508: Create a first data table with the data table name of the uploaded data 240 in the first database.

Step 510: End.

According to the process 50, the data processing system 20 needs to determine the first database according to the data type of the uploaded data 240 in step 302 (step 502). When the data type of the uploaded data 240 is a structured data type, the first database storing the uploaded data 240 is determined to be the relational database 210 (step 504). When the data type of the uploaded data 240 is an unstructured data type, the first database storing the uploaded data 240 is determined to be the non-relational database 212 (step 506). Finally, the data processing system 20 must establish a first data table in the first database determined in steps 504 and 506 according to the data table name of the uploaded data 240 to store the data content of the uploaded data 240.

Please refer to Figure 6, which shows a process 60 for determining a first database and a first data table for actually storing the uploaded data 240 when the data processing system 20 searches for a data table that matches the data table name of the uploaded data 240 in the relational database 210 and the non-relational database 212. Assume that the processing system 20 finds a second data table that matches the data table name of the uploaded data 240 in a second database. In this case, the data processing system 20 needs to consider the compatibility of the second database, the second data table and the uploaded data 240 to determine the first database and the first data table. Process 60 includes the following steps:

Step 600: Start.

Step 602: Determine the data type of the uploaded data 240. If it is a structured data type, execute step 604; if it is an unstructured data type, execute step 606.

Step 604: Determine whether the second database is a relational database 210 or a non-relational database 212. If it is a relational database 210, execute step 608: If it is a non-relational database 212, execute step 610.

Step 606: Determine whether the second database is a relational database 210 or a non-relational database 212. If it is a relational database 210, execute step 612: If it is a non-relational database 212, execute step 610.

Step 608: Determine whether the data content of the uploaded data 240 is compatible with the second data table? If yes, execute step 616; if not, execute step 614.

Step 610: Determine that the first database is a non-relational database 212 and the first data table is a second data table.

Step 612: Determine that the first database is a non-relational database 212 and perform a database migration process.

Step 614: Determine that the first database is the relational database 210 and perform a table migration process.

Step 616: Determine that the first database is the relational database 210 and the first data table is the second data table.

Step 618: End.

According to process 60, the data processing system 20 needs to judge and determine the first database and the first data table according to the data type of the uploaded data 240 and the type of the second database (steps 602-606). When the second database is a non-relational database 212, regardless of whether the data type of the uploaded data 240 is structured data, the uploaded data must be stored in the non-relational database 212. In this case, the data processing system 20 determines that the first database is a non-relational database 212 and the first data table is a second data table (step 610). In other words, the uploaded data 240 can be directly stored in the second data table in the existing second database.

Furthermore, when the second database is a relational database 210, the data processing system 20 needs to determine whether the uploaded data 240 is suitable for being stored in the relational database 210 together with the data content of the second table according to the data type of the uploaded data 240. For example, when the second database is a relational database 210 and the data type of the uploaded data 240 is a non-structured data type, the relational database 210 will not be able to store the non-structured data in the uploaded data 240. Accordingly, the data processing system 20 needs to first migrate the data of the second table from the relational database 210 to the non-relational database 212, and then store the uploaded data 240. Therefore, the data processing system 20 determines that the first database is a non-relational database 212 and performs a database migration process (step 612).

On the other hand, when the second database is a relational database 210 and the data type of the uploaded data 240 is a structured data type, the uploaded data 240 can be stored in the relational database 210. Since the relational database has a strict database schema definition for the storage method of data, the data processing system 20 needs to first check whether the data content of the second data table and the uploaded data 240 is compatible, and cannot directly store the uploaded data 240 in the second data table (step 608). If all fields of the data content of the uploaded data 240 and their data types are compatible or consistent with the second data table, the data processing system 20 can directly store the data content of the uploaded data 240 in the second data table. Therefore, the data processing system 20 determines that the first database is the relational database 210, and the first data table is the second data table (step 616). If the data content of the uploaded data 240 includes all the fields of the second data table and newly added fields compared to the second data table, the uploaded data 240 cannot be directly stored in the second data table. In this case, the data processing system 20 needs to expand the data table fields first, and then store the uploaded data 240. Therefore, the data processing system 20 determines that the first database is the relational database 210, and performs a data table migration process (step 614).

For the database migration process in step 612, please refer to Figure 7. Figure 7 is a schematic diagram of a database migration process 70 of an embodiment of the present invention. The database migration process 70 includes the following steps:

Step 700: Start.

Step 702: Export the data of the second data table as temporary data.

Step 704: Delete the second data table.

Step 706: Create a first table with the table name of the uploaded data 240 in the non-relational database 212.

Step 708: Import temporary data into the first data table.

Step 710: End.

According to the database migration process 70, after the data processing system 20 exports the data content of the second data table and temporarily stores it as a temporary data (step 702), the second data table can be deleted (step 704). Then, the data processing system 20 can create a first data table with the data table name of the uploaded data 240 in the non-relational database 212 (step 706). Finally, the data processing system 20 imports the temporary data into the newly created first data table (step 708). Accordingly, the cross-database data migration of the second data table can be completed, and a first data table compatible with the uploaded data 240 can be created in the non-relational database 212.

In one embodiment, the data processing system 20 can simultaneously receive a database migration parameter specified by the user 110 while receiving the uploaded data 240. When the value of the database migration parameter is true, the data processing system 20 can execute the database migration process 70 to migrate the second table data stored in the relational database 210 to the newly created first table in the non-relational database 212 regardless of whether the uploaded data 240 is a non-structural data type. In the case where the user 110 does not set the database migration parameter, the data processing system 20 can make a judgment according to the process 60 to determine the data processing method.

Please refer to Figure 8 for the data table transfer process in step 614. Figure 8 is a schematic diagram of a data table transfer process 80 of an embodiment of the present invention. The data table transfer process 80 includes the following steps:

Step 800: Start.

Step 802: Export the data of the second data table as temporary data.

Step 804: Delete the second data table.

Step 806: Based on the data content of the uploaded data 240 and the data content of the second data table, a first data table with the data table name of the uploaded data 240 is created in the relational database 210.

Step 808: Import the temporary data into the first data table, where the data of the newly added field is set to a null value.

Step 810: End.

According to the data table migration process 80, after the data processing system 20 exports the data content of the second data table and temporarily stores it as a temporary data (step 802), the second data table can be deleted (step 804). Then, the data processing system 20 can create a first data table with the data table name of the uploaded data 240 in the associative database 210 according to the uploaded data 240 and the data structure of the temporary data (step 806). Finally, the data processing system 20 imports the temporary data into the newly created first data table (step 808). In this way, the data migration of the second data table can be completed, and a first data table compatible with the uploaded data 240 can be established.

Accordingly, according to the processes 50, 60, the database migration process 70 and the table migration process 80 in step 304, the data processing system 20 can automatically identify the data type of the uploaded data 240 and determine the appropriate database and table according to the existing data in the data processing system 20, thereby reducing the burden of manpower and material resources caused by the change of data structure.

Finally, in step 306, the data processing system 20 can store the uploaded data 240 according to the first database and the first data table determined in step 304.

In summary, the present invention provides a data processing system and a data processing method, so that users do not need to repeatedly confirm their needs with database technicians before uploading data. When there are any changes in the uploaded data, there is no need to spend huge manpower costs and time to adjust the database architecture, migrate data, and modify the API. Therefore, the present invention can improve the shortcomings of the known technology and meet the needs of practical applications.

The above is only the preferred embodiment of the present invention. All equivalent changes and modifications made within the scope of the patent application of the present invention shall fall within the scope of the present invention.

20:Data processing system

200:API

210: Relational database

212: Non-relational database

220: Data processing unit

230: Storage unit

232:Program code

240: Upload data

110: User

Claims (8)

A data processing system is provided for processing an uploaded data, wherein the uploaded data includes a data content and a data table name, and the data processing system includes: a relational database; a non-relational database; a data processing unit coupled to the relational database and the non-relational database, and used to execute a program code; and a storage unit coupled to the data processing unit, and used to store the program code to instruct the processing unit to execute a data processing method, wherein the data processing method includes: determining a data type of the uploaded data according to the data content; determining a first data table of a first database according to the data type, the data content and the data table name of the uploaded data; and storing the uploaded data in the first data table of the first database. wherein the first database is the associative database or the non-associative database; wherein the data type is divided into a structured data type and an unstructured data type; wherein the step of determining the data type of the uploaded data according to the data content comprises determining the data type of the uploaded data to be the structured data type when the data content of the uploaded data satisfies a first judgment condition. structured data type, otherwise the data type of the uploaded data is determined to be the unstructured data type, wherein the first judgment condition includes: the data content includes at least one field; the data type of the corresponding data of each field of the at least one field is consistent; and the data type of each field of the at least one field is one of a floating point number, an integer, a date and time, and a string. The data processing system as described in claim 1, wherein the data processing system further receives a database-specified parameter specified by a user and determines the data type according to the database-specified parameter, wherein the step of determining the data type of the uploaded data according to the data content further includes: in response to the database-specified parameter indicating the use of the associative database and the data content of the uploaded data satisfying the first judgment condition, determining The data type of the uploaded data is determined to be the structured data type; in response to the database specified parameter indicating the use of the relational database and the data type of the uploaded data not satisfying the first judgment condition, the data processing system returns an error message to the user; and in response to the database specified parameter indicating the use of the non-relational database, the data type of the uploaded data is determined to be the unstructured data type. The data processing system as described in claim 1, wherein the step of determining the first data table of the first database according to the data type, the data content and the data table name of the uploaded data comprises: determining whether a second data table with the data table name is stored in the data processing system, wherein the second data table is stored in a second database of the data processing system; in response to the second data table not existing, determining the first database according to the data type of the uploaded data, and establishing the first data table with the data table name in the first database; and in response to the second data table already existing, determining the first database and the first data table according to the uploaded data and the second data table. The data processing system as described in claim 3, wherein in response to the second data table not existing, the step of determining the first database according to the data type of the uploaded data comprises: In response to the data type of the uploaded data being a structured data type, determining the first database to be the associative database; and in response to the data type of the uploaded data being a non-structured data type, determining the first database to be the non-associative database. The data processing system as described in claim 3, wherein in response to the second data table existing, the step of determining the first database and the first data table according to the uploaded data and the second data table comprises: in response to the data type of the uploaded data being the structural data type and the second database being the associative database, determining the first database and the first data table according to the data content of the uploaded data and the second data table; in response to the data type of the uploaded data being the structural data type and the second database being the non-associative database , determining the first database to be the non-relational database, and determining the first data table to be the second data table; in response to the data type of the uploaded data being the non-structured data type and the second database being the relational database, determining the first database to be the non-relational database, and performing a database migration; and in response to the data type of the uploaded data being the non-structured data type and the second database being the non-relational database, determining the first database to be the non-relational database, and determining the first data table to be the second data table. The data processing system as described in claim 5, wherein the data type corresponding to the uploaded data is the structural data type and the second database is the associative database, and the step of determining the first database and the first data table according to the data content of the uploaded data and the second data table includes: all fields and their data types corresponding to the data content of the uploaded data and the second data table are determined. When the data tables match, the first database is determined to be the associative database, and the first data table is determined to be the second data table; and in response to all fields of the second data table matching a subset of all fields of the data content of the uploaded data and the data content of the uploaded data having a newly added field, the first database is determined to be the associative database, and a data table migration is performed. The data processing system as described in claim 6, wherein the step of transferring the data table includes: exporting the data of the second data table as temporary data; deleting the second data table; creating the first data table with the data table name in the relational database according to the data content of the uploaded data and a data content of the second data table; and importing the temporary data into the first data table, wherein the data of the newly added field is set to a null value. The data processing system as described in claim 5, wherein in response to the data type of the uploaded data being the unstructured data type and the second database being the relational database, the first database is determined to be the non-relational database of the data processing system, and the steps of performing the database migration include: exporting the data of the second data table as temporary data; deleting the second data table; creating the first data table with the data table name in the non-relational database; and importing the temporary data into the first data table.