Continuing the description of the CRUD Function Extension for Grid (front-end) components with Unit verification, we all know that in some scenarios, we have to collect basic data required by the system from various channels in some ways. If the data to be collected is large! It is not wise to enter people manually! Share here
Continuing the description of the CRUD Function Extension for Grid (front-end) components with Unit verification, we all know that in some scenarios, we have to collect basic data required by the system from various channels in some ways. If the data to be collected is large! It is not wise to enter people manually! Share here
Continued 《CRUD Function Extension of the Grid (front-end) component with cell verification functionWe all know that in some scenarios, we have to collect some basic data required by the system in various ways. If the amount of data to be collected is large! It is not wise to enter people manually! Here we will share the next tips (without the help of tools and software). I believe this method will be frequently used for those who frequently write reports!
Continued 《CRUD Function Extension of the Grid (front-end) component with cell verification function"Blog, because the following data collection method is to collect data from the platform data dictionary from a system prototype. After adding the data dictionary, you can also add, edit, and query Dictionary data directly by operating the Grid component. You do not need to create redundant forms pages to add Dictionary data, reduce the number of minutes for events that have been completed in one day!
Next, let's take a look at the data collection:
As we all know in the personnel Dictionary of the region selected in the figure that the region dictionary contains a large amount of data, will the data of this dictionary be manually input like a fool? I believe you will not. However, when we need to modify the new dictionary, simple input will not affect our work efficiency.
Next, let's briefly talk about the data transfer between heterogeneous databases [from oracle database to mysql database] (without tools ----Concatenate an SQL statement to [concatenate an insert statement or a stored procedure]:
Next we will go to oracle's IDE programming tool pl/SQL to execute the following statement:
Select 'insert jp_dict_Region (JPID, NAME, CODE, Rank_Num, IS_FLAG, Parent_Id) values (''' | t. encoding | ''', ''' | t. name | ''', ''' | t. simple code | ''', '| t. level | ',' | t. default | ', ''' | t. upper-level code | '''); 'As SQL statement from Region t
The following results are displayed:
Copy the generated script to mysql for execution!
Of course, we can use specific tools to transmit or transfer data between heterogeneous databases or between physical and heterogeneous data. I will not introduce the use of these tools here! The above is an implementation method without third-party tools. The above is helpful to you.
The following are the application results of the jplogic dictionary tool: