A method and apparatus for managing interface metadata

Abstract

The application discloses a kind of interface metadata management method and device, the management method includes: setting interface management platform to be used to manage all interface information;By the interceptor of MyBatis, the executed SQL is intercepted and dynamically modified the executed SQL and its parameters;Integrate interface management platform and the information that the executed SQL is intercepted by MyBatis to associate the interface information and the configuration information of MyBatis, so that when adjusting table field information, the corresponding field in the table corresponding to the statement associated to corresponding MyBatis can be modified.The beneficial effects of the application are: each interface associated query statement and associated table information can be analyzed by interface metadata information system;Newly added field is quickly adjusted through interface to adapt to customer demand, without modifying code.

Description

Technical Field

[0001] This invention relates to the field of interface metadata management technology, and more specifically, to a method and apparatus for managing interface metadata. Background Technology

[0002] Front-end and back-end separation has become an industry standard practice in internet project development. Using Nginx + Tomcat (or with Node.js in between) effectively decouples the systems and lays a solid foundation for future large-scale distributed architectures, elastic computing architectures, microservice architectures, and multi-platform services (multiple clients, such as browsers, in-vehicle terminals, Android, iOS, etc.). This step is an essential step in the evolution of system architecture from a primitive to a human. The core idea is that the front-end HTML page calls the back-end RESTful API interface via AJAX and interacts using JSON data. This way, front-end engineers focus on front-end tasks, and back-end engineers focus on back-end tasks.

[0003] With the gradual development of front-end and back-end separation, front-end interface configuration has become increasingly common. The front-end can automatically generate pages based on back-end interfaces, including list query pages, save and change pages, etc. The front-end needs back-end interface information and input and return field information for the configuration selection of the front-end interface.

[0004] Simultaneously, it's also necessary to meet some simple customer needs regarding changing fields, such as adding an extended field for saving or querying, or adding a query condition. For example, when configuring the front-end interface, the customer might request adding a field for display. How can this be done quickly and displayed through the interface management platform? Therefore, it's necessary to design and develop a platform to display all backend interfaces, and to simultaneously modify the field information in the backend logical SQL while modifying the interface information.

[0005] Currently, common practices include using API display platforms like Swagger or manually maintaining SQL statements and synchronizing with the API management platform. However, Swagger only serves for display and debugging and cannot modify backend fields; manual maintenance is costly, requiring modification of SQL, compilation and deployment, as well as modification of the corresponding management data, which is out of sync and requires separate maintenance. Summary of the Invention

[0006] This invention provides a method and apparatus for managing interface metadata, which solves the problems existing in the Swagger platform or the manual maintenance of interface platforms.

[0007] To address the aforementioned problems, this invention provides a method for managing interface metadata, comprising:

[0008] Set up an interface management platform to manage all interface information;

[0009] The execution of SQL can be intercepted and processed using MyBatis interceptors, and the execution of SQL and its parameters can be dynamically modified.

[0010] The interface management platform and the information of the SQL interception and processing by MyBatis are integrated to associate the interface information and the configuration information of MyBatis, so that when the table field information is adjusted, the corresponding field in the table associated with the corresponding MyBatis statement can be modified.

[0011] The interface management platform is configured to manage all interface information, including:

[0012] Set up extended fields to be used to associate with all fields in the table structure.

[0013] The process of intercepting and dynamically modifying the executed SQL and its parameters using MyBatis interceptors includes:

[0014] In MyBatis, each SQL statement corresponds to a Mapped StatementId so that the executed SQL can be intercepted and processed by MyBatis' interceptors.

[0015] In the Mapper.xml file, XMLStatementBuilder is called to parse the query statements and insert / delete / update statements in the SQL statement;

[0016] After parsing, MappedStatement is used to represent all SQL statements, so that one MSID corresponds to one SQL statement, one SQL statement corresponds to one or more table structures, and each table structure corresponds to the corresponding field information.

[0017] The integrated interface management platform and the MyBatis information regarding the interception and processing of executed SQL are associated with the interface information and the MyBatis configuration information. This allows for the modification of corresponding fields in the table associated with the corresponding MyBatis statement when adjusting table field information, including:

[0018] Synchronize the interface information, including the MSID information of the SQL execution corresponding to the interface, to the interface management platform;

[0019] Synchronize the corresponding table structure and field information to the interface management platform;

[0020] Synchronously transmit the table information corresponding to the MSID information obtained by parsing to the interface management platform.

[0021] The integrated interface management platform and the MyBatis information for intercepting and processing the executed SQL are associated with the interface information and the MyBatis configuration information. This allows for modification of the corresponding fields in the table associated with the corresponding MyBatis statement when adjusting table field information. It also includes:

[0022] After adding a new field, the newly added non-built-in field will be synchronized to the preset backend through the interface management platform;

[0023] When executing SQL in the background, the table structure and field information associated with the new field in the interface management are obtained by intercepting and processing the MSID.

[0024] Parse the SQL and dynamically modify the executed SQL to add the new field.

[0025] On the one hand, a management device for interface metadata is provided, including:

[0026] The settings module is used to configure the interface management platform for managing all interface information.

[0027] The interception module is used to intercept and process the executed SQL through MyBatis interceptors and dynamically modify the executed SQL and its parameters;

[0028] The integration module is used to integrate the information of the interface management platform and the MyBatis's interception and processing of the executed SQL to associate the interface information and the MyBatis configuration information, so that when the table field information is adjusted, the corresponding field in the table associated with the corresponding MyBatis statement can be modified.

[0029] The settings module includes:

[0030] The Field Settings submodule is used to set extended fields to be associated with all fields in the table structure.

[0031] The interception module includes:

[0032] The interception and processing submodule is used to map each SQL statement in MyBatis to a Mapped StatementId so that the executed SQL can be intercepted and processed by MyBatis' interceptors.

[0033] The parsing submodule is used to parse the query statements and insert / delete / update statements in the SQL statement within the Mapper.xml file by calling XMLStatementBuilder.

[0034] The corresponding submodule is used to represent all SQL statements using MappedStatement after parsing, so that one MSID corresponds to one SQL statement, one SQL statement corresponds to one or more table structures, and each table structure corresponds to the corresponding field information.

[0035] The integration module includes:

[0036] The first synchronization submodule is used to synchronize interface information, including the MSID information of the SQL execution corresponding to the interface, to the interface management platform.

[0037] The second synchronization submodule is used to synchronize the corresponding table structure and field information to the interface management platform.

[0038] The third synchronization submodule is used to synchronize the table information corresponding to the MSID information obtained by parsing to the interface management platform;

[0039] The fourth synchronization submodule is used to synchronize newly added non-built-in fields to the preset backend through the interface management platform after adding new fields.

[0040] The MSID interception submodule is used to obtain the table structure and field information associated with the addition of a field in the interface management by intercepting MSID when executing SQL in the background.

[0041] The field addition submodule is used to parse SQL and dynamically modify the executed SQL to add the new field.

[0042] On the one hand, a computer-readable storage medium is provided, wherein a plurality of instructions are stored therein, the instructions being adapted to be loaded by a processor to execute an interface metadata management method as described above.

[0043] The beneficial effects of this invention are:

[0044] The query statements and table information associated with each interface can be analyzed through the interface metadata information system; newly added fields can be quickly adjusted through a graphical interface to adapt to customer needs without modifying the code. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0046] Figure 1 This is a flowchart of an interface metadata management method provided in an embodiment of the present invention. Detailed Implementation

[0047] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0048] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more features. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0049] In this invention, the term "exemplary" is used to mean "serving as an example, illustration, or description." Any embodiment described as "exemplary" in this invention is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use the invention. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that the invention can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of the invention with unnecessary detail. Therefore, the invention is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed herein.

[0050] This project constructs a unified interface metadata platform that can manage interface information, such as interface name, URL, input and return fields; it can also adjust backend logic field information through interface configuration management. Without modifying the backend logic, the backend query or saved field information can be synchronously modified by adjusting the interface information. At the same time, it supports absolute or fuzzy search for newly added fields.

[0051] See Figure 1 , Figure 1This is a flowchart illustrating a method for managing interface metadata according to an embodiment of the present invention. The method for managing interface metadata includes steps S1-S3:

[0052] S1. Set up the interface management platform to manage all interface information; among which, set extended fields to associate with all fields in the table structure.

[0053] In this embodiment, an interface management platform is designed to manage all interfaces, including interface module information and interface information. The interface management platform uses an open-source interface management platform tool, mainly for interface module management, interface grouping, and interface information management. For interface information management, to address the need for field expansion, the functionality of extending fields is added to associate them with the table structure fields below.

[0054] S2. Intercept and process the executed SQL using MyBatis's interceptor and dynamically modify the executed SQL and its parameters; step S2 includes steps S21-S23:

[0055] S21. In MyBatis, each SQL statement corresponds to a Mapped StatementId so that the executed SQL can be intercepted and processed through MyBatis's interceptors.

[0056] In this embodiment, the executed SQL is intercepted and processed using a MyBatis interceptor, dynamically modifying the SQL and its parameters. The backend logic adds SQL interception, currently implemented through the corresponding MyBatis interceptor. MyBatis is an excellent persistence layer framework that supports customized SQL, stored procedures, and advanced mappings. MyBatis avoids almost all JDBC code and manual parameter setting and result set retrieval. MyBatis can use simple XML or annotations to configure and map native information, mapping interfaces and Java POJOs (Plain Ordinary Java Objects) to records in the database.

[0057] S22. In parsing the Mapper.xml file, call XMLStatementBuilder to parse the query statements and add, delete, and modify statements in the SQL statement;

[0058] In this embodiment, each SQL statement in MyBatis corresponds to a Mapped StatementId. SQL statements are further divided into DQL and DML, where DQL is for query statements and DML is for CRUD operations. The XMLStatementBuilder is called to parse these nodes in the Mapper.xml file.

[0059] S23. After parsing, MappedStatement is used to represent all SQL statements, so that one MSID corresponds to one SQL statement, one SQL statement corresponds to one or more table structures, and each table structure corresponds to the corresponding field information.

[0060] In this embodiment, MappedStatement is used to represent each SQL statement after parsing. Therefore, one MSID corresponds to one SQL statement, one SQL statement corresponds to one or more table structures, and each table structure corresponds to specific field information. The following example uses query results:

[0061] The SQL statement corresponding to `com.ly.demo.mapper.UserMapper.selectUser` is: `select u.name,u.age,p.provinceName as p.provinceStr from t_user_info u join t_province_infopon u.provinceId=p.provinceId`. SQL syntax parsing reveals that this SQL statement corresponds to two table structures: `t_user_info` and `t_province_info`. The fields corresponding to these two table structures are also known and can be obtained from the database metadata.

[0062] S3. Integrate the interface management platform and the information on the SQL interception and processing by MyBatis to associate the interface information and the MyBatis configuration information, so that when adjusting the table field information, the corresponding fields in the table associated with the corresponding MyBatis statement can be modified. Step S3 includes steps S31-S36:

[0063] S31. Synchronize the interface information, including the MSID information of the SQL execution corresponding to the interface, to the interface management platform;

[0064] In this embodiment, after the business function is developed, the interface information is manually maintained in the interface management platform, including the MSID information of the SQL execution corresponding to the interface.

[0065] S32. Synchronize the corresponding table structure and field information to the interface management platform;

[0066] In this embodiment, the table information and field information of the corresponding database are simultaneously synchronized to the interface management platform.

[0067] S33. Synchronize the table information corresponding to the MSID information obtained by parsing to the interface management platform.

[0068] In this embodiment, the table information corresponding to the MSID of the business module is also synchronized to the interface management platform through the MyBatis parsing tool method corresponding to the business module.

[0069] S34. After adding a new field, synchronize the newly added non-built-in field to the preset backend through the interface management platform;

[0070] In this embodiment, only the interface development process needs to be followed according to general development methods. Then, the corresponding interface management platform needs to be maintained. For example, the query above requires maintaining the MSID corresponding to the data node. This way, when adding a new field, the corresponding table can be selected, and the corresponding field can be selected through the table. This allows the newly created field to be associated with the database field. After adding a new field, the interface management platform will synchronize the newly added non-built-in field to the business backend.

[0071] S35. When executing SQL in the background, the table structure and field information associated with the new field in the interface management are obtained by intercepting and processing the MSID.

[0072] In this embodiment, when executing SQL in the background, the table structure and field information associated with adding fields in the interface management can be obtained by intercepting and judging the MSID.

[0073] S36. Parse the SQL and dynamically modify the executed SQL to add the new field.

[0074] In this embodiment, SQL is parsed, dynamically modified, and corresponding fields are added. Similarly, DML operations are also handled by associating MSIDs through the interface, adding fields via the interface, synchronizing with the business backend configuration, intercepting SQL execution in MyBatis, dynamically parsing and adjusting the SQL to be executed, and processing it. When a user needs to add a field, they only need to add a field in the interface management platform and select the corresponding table and field. After saving, the data is saved to the backend database and automatically synchronized to the business database. Thus, when MyBatis executes the SQL corresponding to the MSID, it parses the SQL, concatenates the corresponding fields from the table, converts them into aliases, and then executes it.

[0075] The core components are explained below:

[0076] 1. SQL parsing component

[0077] It is used to parse SQL statements and insert configuration extension fields into the statements.

[0078] 1) SQL query parsing

[0079] Because of the diversity of SQL queries, it is necessary to traverse various scenarios of the SQL query:

[0080] Single table scenario

[0081] Select name, age from t_user

[0082] Multi-table scenarios

[0083] Select u.name,u.age,p.province from t_user u join t_provicen p onu.province_id=p.id

[0084] 1.3) Subqueries

[0085] Select t.name,d.address from(Select u.id,u.name,u.age,p.province fromt_user u join t_provicen p on u.province_id=p.id)t join t_address d on t.id=d.user_id

[0086] 1.4) Multi-level complex queries containing *

[0087] Select t.name,d.address from(Select u.id,u.name,u.age,p.*from t_userujoin t_provicen p on u.province_id=p.id)t join t_address d on t.id=d.user_id

[0088] Based on the most complex example

[0089] First, we need to parse the sub-statement `Select u.id,u.name,u.age,p.*from t_user u join t_provicen p on u.province_id=p.id` to break it down into the two tables `t_user` and `t_provicen`, their aliases, and the corresponding statement blocks. Then, we need to parse the parent node of this subquery: `Select t.name,d.address from()tjoin t_address d on t.id=d.user_id`.

[0090] When adding a field to this SQL statement, when selecting the table `t_provicen` and adding column1 as `f1`, the corresponding subquery becomes: `Select u.id,u.name,u.age,p.*,p.column1 as f1 from t_user u join t_provicen p on u.province_id=p.id;`. Then, the parent statement is enhanced: `Select t.name,d.address,t.column1 as f1 from()t join t_address d on t.id=d.user_id`.

[0091] Of course, there are also the following scenarios.

[0092] If the parent statement is `Select*from()t join t_address d on t.id=d.user_id`, then there is no need to modify the parent statement; otherwise, duplicate field names will occur.

[0093] The entire SQL parsing process uses the open-source tool JSqlParser, which has been extended from there.

[0094] 2) New Scenarios

[0095] For example, the statement `insert t_user(name,age)values(?,?)` requires parsing out the corresponding SQL statement block, recognizing the expression statement block, and filling in the fields; when adding the field `column1` as `f1`, then the field `insert t_user(name,age,column1)values(?,?,?)` needs to be filled in.

[0096] 3) Update the scene

[0097] Similar to before, it parses the syntax structure, finds the corresponding position to add parameters and values, because there is a strategy for whether to modify the value, which is currently effective only when there is a non-empty value;

[0098] Taking the newly added data as an example, when modifying the column1 field, the front end will send the data f1 to the back end. Only when f1 is not null and is not an empty string will this field be modified.

[0099] Update t_user set name=? where id=?

[0100] The statement after the condition is met is changed to

[0101] Update t_user set name=? , column1=? where id=?

[0102] The above describes how to dynamically modify SQL. By parsing the SQL syntax structure, the SQL statement is dynamically modified according to the configuration rules, thus achieving dynamic expansion of fields.

[0103] 2. SQL statement interception

[0104] Currently, a MyBatis interceptor is used. After intercepting the MyBatis MSID, the configuration information is queried to determine if there is an enhanced configuration corresponding to the MSID. If so, the SQL statement is parsed by the SQL parsing component, the SQL is dynamically modified according to the configuration, and then reassigned to the SQL statement. The runtime status front-end input parameters are obtained through the configured fields and alias information, and the alias field information is converted into database field data information.

[0105] The interface metadata management device in this case includes:

[0106] The settings module is used to configure the interface management platform for managing all interface information.

[0107] The interception module is used to intercept and process the executed SQL through MyBatis interceptors and dynamically modify the executed SQL and its parameters;

[0108] The integration module is used to integrate the information of the interface management platform and the MyBatis's interception and processing of the executed SQL to associate the interface information and the MyBatis configuration information, so that when the table field information is adjusted, the corresponding field in the table associated with the corresponding MyBatis statement can be modified.

[0109] The settings module includes:

[0110] The Field Settings submodule is used to set extended fields to be associated with all fields in the table structure.

[0111] The interception module includes:

[0112] The interception and processing submodule is used to map each SQL statement in MyBatis to a Mapped StatementId so that the executed SQL can be intercepted and processed by MyBatis' interceptors.

[0113] The parsing submodule is used to parse the query statements and insert / delete / update statements in the SQL statement within the Mapper.xml file by calling XMLStatementBuilder.

[0114] The corresponding submodule is used to represent all SQL statements using MappedStatement after parsing, so that one MSID corresponds to one SQL statement, one SQL statement corresponds to one or more table structures, and each table structure corresponds to the corresponding field information.

[0115] The integration module includes:

[0116] The first synchronization submodule is used to synchronize interface information, including the MSID information of the SQL execution corresponding to the interface, to the interface management platform.

[0117] The second synchronization submodule is used to synchronize the corresponding table structure and field information to the interface management platform.

[0118] The third synchronization submodule is used to synchronize the table information corresponding to the MSID information obtained by parsing to the interface management platform;

[0119] The fourth synchronization submodule is used to synchronize newly added non-built-in fields to the preset backend through the interface management platform after adding new fields.

[0120] The MSID interception submodule is used to obtain the table structure and field information associated with the addition of a field in the interface management by intercepting MSID when executing SQL in the background.

[0121] The field addition submodule is used to parse SQL and dynamically modify the executed SQL to add the new field.

[0122] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor. Therefore, embodiments of the present invention provide a storage medium storing multiple instructions that can be loaded by a processor to execute the steps in any of the interface metadata management methods provided in the embodiments of the present invention.

[0123] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0124] Since the instructions stored in the storage medium can execute the steps in any of the interface metadata management methods provided in the embodiments of the present invention, the beneficial effects that any of the interface metadata management methods provided in the embodiments of the present invention can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0125] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for managing interface metadata, characterized in that, include: Set up an interface management platform to manage all interface information; The execution of SQL can be intercepted and processed using MyBatis interceptors, and the execution of SQL and its parameters can be dynamically modified. The interface management platform and the information of the SQL interception and processing by MyBatis are integrated to associate the interface information and the configuration information of MyBatis, so that when the table field information is adjusted, the corresponding field in the table associated with the corresponding MyBatis statement can be modified. The interface management platform is configured to manage all interface information, including: Set up extended fields to be used to associate with all fields in the table structure; The process of intercepting and dynamically modifying the executed SQL and its parameters using MyBatis interceptors includes: In MyBatis, each SQL statement corresponds to a Mapped StatementId so that the executed SQL can be intercepted and processed by MyBatis' interceptors. In the Mapper.xml file, XMLStatementBuilder is called to parse the query statements and CRUD statements in the SQL statement; After parsing, MappedStatement is used to represent all SQL statements, so that one MSID corresponds to one SQL statement, one SQL statement corresponds to one or more table structures, and each table structure corresponds to the corresponding field information; The integrated interface management platform and the MyBatis information regarding the interception and processing of executed SQL are associated with the interface information and the MyBatis configuration information. This allows for the modification of corresponding fields in the table associated with the corresponding MyBatis statement when adjusting table field information, including: Synchronize the interface information, including the MSID information of the SQL execution corresponding to the interface, to the interface management platform; Synchronize the corresponding table structure and field information to the interface management platform; Synchronize the table information corresponding to the obtained MSID information to the interface management platform; The integrated interface management platform and the MyBatis information for intercepting and processing the executed SQL are associated with the interface information and the MyBatis configuration information. This allows for modification of the corresponding fields in the table associated with the corresponding MyBatis statement when adjusting table field information. It also includes: After adding a new field, the newly added non-built-in field will be synchronized to the preset backend through the interface management platform; When executing SQL in the background, the table structure and field information associated with the new field in the interface management are obtained by intercepting and processing the MSID. Parse the SQL and dynamically modify the executed SQL to add the new field.

2. An interface metadata management device, used to execute the interface metadata management method as described in claim 1, characterized in that, The device includes: The settings module is used to configure the interface management platform for managing all interface information. The interception module is used to intercept and process the executed SQL through MyBatis interceptors and dynamically modify the executed SQL and its parameters; The integration module is used to integrate the information of the interface management platform and the MyBatis's interception and processing of the executed SQL to associate the interface information and the MyBatis configuration information, so that when the table field information is adjusted, the corresponding field in the table associated with the corresponding MyBatis statement can be modified. The settings module includes: The Field Settings submodule is used to set extended fields to be associated with all fields in the table structure; The interception module includes: The interception and processing submodule is used to map each SQL statement in MyBatis to a Mapped StatementId so that the executed SQL can be intercepted and processed by MyBatis' interceptors. The parsing submodule is used to parse the query and CRUD statements in the SQL statement by calling XMLStatementBuilder in the Mapper.xml file; The corresponding submodule is used to represent all SQL statements after parsing using MappedStatement, so that one MSID corresponds to one SQL statement, one SQL statement corresponds to one or more table structures, and each table structure corresponds to the corresponding field information; The integration module includes: The first synchronization submodule is used to synchronize interface information, including the MSID information of the SQL execution corresponding to the interface, to the interface management platform. The second synchronization submodule is used to synchronize the corresponding table structure and field information to the interface management platform. The third synchronization submodule is used to synchronize the table information corresponding to the MSID information obtained by parsing to the interface management platform; The fourth synchronization submodule is used to synchronize newly added non-built-in fields to the preset backend through the interface management platform after adding new fields. The MSID interception submodule is used to obtain the table structure and field information associated with the newly added field in the interface management by intercepting MSID when executing SQL in the background. The field addition submodule is used to parse SQL and dynamically modify the executed SQL to add the new field.

3. A computer-readable storage medium, characterized in that, The storage medium stores multiple instructions, which are adapted to be loaded by a processor to execute the interface metadata management method of claim 1.

Images