CN117312334A - Data dictionary management method, system, equipment and storage medium - Google Patents

Abstract

Embodiments of the present invention disclose a data dictionary management method, system, equipment and storage medium. After developers log in to the data dictionary management system through a client, the data dictionary management system will display an interactive interface in the client, and in the interactive interface The type adding control, data type label and data adding control are displayed on the screen. By operating the type adding control, data type label and data adding control respectively, developers can add the dictionary type of the data dictionary, view the dictionary data in the dictionary type and add Dictionary data for data dictionary. In the embodiment of the present invention, developers can log in to the data dictionary management system through the client and use the data dictionary management system to view and modify the data dictionary. There is no need for a specific database administrator to manage the data dictionary on the server. , improves the management efficiency of the data dictionary, and solves the technical problem of low efficiency of data dictionary management in the existing technology.

Description

A data dictionary management method, system, equipment and storage medium

Technical field

Embodiments of the present application relate to the field of data management, and in particular, to a data dictionary management method, system, device and storage medium.

Background technique

Data dictionary is the cornerstone of large-scale systems and mainly serves the development phase of the system. The data dictionary is used to define and describe data items, data structures, data flows, data storage, and processing logic. Its purpose is to provide a detailed explanation of each element in the data flow diagram. In the prior art, when managing data in a data dictionary, a specific database administrator often needs to modify the data dictionary on the server. However, this modification method will prevent non-database administrators from participating in the overview and modification of the data dictionary. The update process of the data dictionary is cumbersome, and manual updates are prone to problems such as data errors and omissions, and the management efficiency of the data dictionary is low.

To sum up, the management method of data dictionary in the existing technology has the technical problem of low management efficiency.

Contents of the invention

Embodiments of the present invention provide a data dictionary management method, system, equipment and storage medium, which can improve the efficiency of data dictionary management and solve the technical problem of low data dictionary management efficiency in the prior art.

In the first aspect, embodiments of the present invention provide a data dictionary management method. The data dictionary management method is suitable for a data dictionary management system. The data dictionary management system logs in through a client, and the client communicates with the server that stores the data dictionary. The data dictionary includes at least one dictionary type. The dictionary type is used to record dictionary data. The data dictionary management method includes:

Display the interactive interface of the data dictionary management system on the client. The interactive interface displays type addition controls and data type labels. Each data type label corresponds to a dictionary type;

In response to the first trigger operation acting on the type adding control, display the type adding sub-interface;

Add the first dictionary type to the data dictionary according to the first input data received through the type addition sub-interface, and update the display data type label;

In response to the second trigger operation acting on the data type label, obtain the dictionary data corresponding to the second dictionary type from the data dictionary and display it in the data display area, and display the data adding control in the data display area. The second dictionary type is based on The data type tag confirmation of the second trigger operation effect;

In response to the third trigger operation acting on the data adding control, display the data adding sub-interface;

According to the second input data received through the data adding sub-interface, add dictionary data to a third dictionary type in the data dictionary and update the display data display area. The third dictionary type is the dictionary type corresponding to the dictionary data currently displayed in the data display area.

In the second aspect, embodiments of the present invention provide a data dictionary management system. The data dictionary management system logs in through a client. The client communicates with a server that stores a data dictionary. The data dictionary includes at least one dictionary type. Type is used to record dictionary data;

The data dictionary management system is used to display the interactive interface of the data dictionary management system on the client. The interactive interface displays type addition controls and data type labels. Each data type label corresponds to a dictionary type;

The data dictionary management system is used to respond to the first trigger operation acting on the type adding control and display the type adding sub-interface;

The data dictionary management system is configured to add the first dictionary type to the data dictionary according to the first input data received through the type adding sub-interface, and update the display data type label;

The data dictionary management system responds to the second trigger operation acting on the data type tag, obtains the dictionary data corresponding to the second dictionary type from the data dictionary and displays it in the data display area, and displays the data adding control in the data display area. The second dictionary type is confirmed according to the data type tag of the second trigger operation;

The data dictionary management system is used to respond to the third trigger operation acting on the data adding control and display the data adding sub-interface;

The data dictionary management system is used to add dictionary data to the third dictionary type in the data dictionary and update the display data display area according to the second input data received through the data adding sub-interface. The third dictionary type is the dictionary currently displayed in the data display area. The dictionary type corresponding to the data.

In a third aspect, embodiments of the present invention provide a data dictionary management device. The data dictionary management device includes a processor and a memory;

Memory is used to store computer programs and transmit computer programs to the processor;

The processor is configured to execute a data dictionary management method according to the first aspect according to instructions in the computer program.

In a fourth aspect, embodiments of the present invention provide a storage medium that stores computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a data dictionary management method as in the first aspect.

As mentioned above, the embodiment of the present invention provides a data dictionary management method. After the developer logs in to the data dictionary management system through the client, the data dictionary management system will display the interactive interface on the client and display the type adding control on the interactive interface. , data type label and data adding control. By operating the type adding control, data type label and data adding control respectively, developers can add the dictionary type of the data dictionary, view the dictionary data in the dictionary type and add the dictionary data of the data dictionary. . In the embodiment of the present invention, developers can log in to the data dictionary management system through the client and use the data dictionary management system to view and modify the data dictionary. There is no need for a specific database administrator to manage the data dictionary on the server. , the management process of the data dictionary is more flexible, the management efficiency of the data dictionary is improved, and the technical problem of low efficiency of data dictionary management in the existing technology is solved.

Description of drawings

Figure 1 is a schematic diagram of a connection between a client and a server according to an embodiment of the present invention.

Figure 2 is a schematic flow chart of a data dictionary management method provided by an embodiment of the present invention.

Figure 3 is a schematic diagram of an interactive interface provided by an embodiment of the present invention.

Figure 4 is a schematic diagram of one type of adding sub-interface provided by an embodiment of the present invention.

Figure 5 is a schematic diagram of another type of adding sub-interface provided by an embodiment of the present invention.

Figure 6 is a schematic diagram of a data adding control provided by an embodiment of the present invention.

Figure 7 is a schematic diagram of a data adding sub-interface provided by an embodiment of the present invention.

FIG. 8 is a schematic diagram of another data adding sub-interface provided by an embodiment of the present invention.

Figure 9 is a schematic diagram of dictionary data displayed in a data display area according to an embodiment of the present invention.

Figure 10 is a schematic diagram of a label editing control provided by an embodiment of the present invention.

Figure 11 is a schematic diagram of a data editing control and a data deletion control provided by an embodiment of the present invention.

Figure 12 is a schematic flow chart of another data dictionary management method provided by an embodiment of the present invention.

Figure 13 is a schematic diagram of a synchronized environment control provided by an embodiment of the present invention.

Figure 14 is a schematic diagram of a synchronization environment sub-interface provided by an embodiment of the present invention.

Figure 15 is a timing diagram of a synchronization environment provided by an embodiment of the present invention.

Figure 16 is a schematic structural diagram of a data dictionary management device provided by an embodiment of the present invention.

Reference signs:

Client 10, server 20.

Detailed ways

The following description and drawings illustrate specific embodiments of the application sufficiently to enable those skilled in the art to practice them. The examples represent only possible variations. Unless explicitly required, individual components and features are optional and the order of operations may vary. Portions and features of some embodiments may be included in or substituted for those of other embodiments. The scope of embodiments of the present application includes the entire scope of the claims, and all available equivalents of the claims. Each embodiment may be referred to herein, individually or collectively, by the term "invention" for convenience only and is not intended to automatically limit the scope of the application to any one if the fact that more than one invention is disclosed is disclosed. A single invention or inventive concept. Herein, relational terms such as first, second, etc. are used only to distinguish one entity or operation from another entity or operation without requiring or implying that any actual relationship exists between these entities or operations or order. Furthermore, the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, or apparatus that includes a list of elements includes not only those elements, but also others not expressly listed. elements. Each embodiment in this article is described in a progressive manner. Each embodiment focuses on its differences from other embodiments. The same and similar parts between the various embodiments can be referred to each other. For the structures, products, etc. disclosed in the embodiments, since they correspond to the parts disclosed in the embodiments, the descriptions are relatively simple. For relevant details, please refer to the description of the method section.

In the prior art, when managing the data in the data dictionary, a specific database administrator needs to log in to the data dictionary in the server through a specific account, and then add, delete, and other operations to the data in the data dictionary. However, since the data in the data dictionary is stored on the server, and due to the lack of support from visual components on the server, it is difficult for non-database administrators to understand the meaning of each data in the data dictionary, making it difficult for non-database administrators to participate in the overview and review of the data dictionary. Changing. In addition, since only the database administrator can modify the data dictionary, when the data dictionary needs to be modified during the project development process, the developer needs to determine the location that needs to be modified in the data dictionary and then inform the database administrator. The database administrator modifies the data dictionary, and the update process of the data dictionary is cumbersome. Secondly, because the database administrator intelligently and manually modifies the data dictionary, it is very easy for problems such as data errors and omissions to occur when the data dictionary needs to be manually synchronized during multi-environment development.

Based on this, in order to solve the above problems, embodiments of the present invention provide a data dictionary management method. The data dictionary management method is suitable for a data dictionary management system, and the data dictionary management system is logged in through a client.

Among them, the client refers to the program (which can also be recorded as an application, software program or APP, etc.) in the development equipment used by developers to implement local services for project development. The development equipment used by developers includes but is not limited to: mobile phones, tablets, laptops, desktop computers and other devices.

In one embodiment, a development device used by developers includes a processor, a display screen, a memory, and a communication module. The processor, display screen, memory, and communication module can be connected through a communication bus or other means.

The processor may include processing units such as an application processor (AP), a graphics processing unit (GPU), and a central processing unit (CPU). The processor executes various functional applications and data processing of the development device by running computer executable programs (such as software programs, instructions, modules, etc.) stored in the memory. For example, the processor runs a program as a developer to implement project development functions.

The memory may be used to store a computer executable program including instructions for the development device and the like. The memory may include an area for storing programs and an area for storing data. Among them, the stored program area can store the operating system and at least one application program required for the function. The storage data area can store data created based on the use of the development device, etc. The memory may include high-speed random access memory and may also include non-volatile memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory may further include memory located remotely from the processor, and these remote memories may be connected to the development device through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.

The number of display screens can be one or more. The display screen can be a liquid crystal display (Liquid Crystal Display), an LED display (LED display), an organic light-emitting diode (OLED) display or a flexible light-emitting diode (FLED) display, etc. . The display may display based on instructions from the processor.

In some cases, the display screen may also have a touch function, which is a touch display screen. The touch display screen includes a display panel and a touch panel. The display panel is used to complete the visual output. The touch panel may be a component that supports infrared touch, electromagnetic touch, capacitive touch, resistive touch, etc. The touch panel can transmit touch data corresponding to the detected touch operation to the processor, and the display panel can provide visual output related to the touch operation.

The communication module may include a wired communication module and/or a wireless communication module. The wired communication module includes at least one communication interface, such as a universal serial bus (Universal Serial Bus, USB) interface, a network interface, etc. The wireless communication module includes one or more of a Bluetooth module, an infrared module, a wireless fidelity (Wi-Fi) module, and a near field communication (Near Field Communication, NFC) module. Currently, the processor can communicate with external devices through the communication module, such as communicating with the background server, communicating with other devices, and communicating with external devices adapted to the development device. The external device may be one or more of a writing pen (also called a smart pen, a stylus, etc.), a keyboard, a mouse, etc.

Based on the above structure, the development device supports at least one type of operating system, where the operating system can be an Android system, a Windows system, a Linux system, an IOS system, or macOS, etc. The development device has at least one application installed under the operating system. The application program may be an application program that comes with the operating system, or may be an application program downloaded from a third-party device or server. For example, the development device is installed with an application program (i.e., client) used to implement project development.

In some cases, the development device used by the developer can also act as a client.

In the embodiment, the developer can log in to the data dictionary management system through the client, where logging in refers to entering the data dictionary management system. The developer can use the dictionary management system only after logging in to the data dictionary management system through the client. For example, the data dictionary management system is SAAS (Software as a Service, software operation service). Developers can log in to the data dictionary management system through the browser on the client, so there is no need to install the data dictionary management system on the developer's computer. on the device. It is understandable that currently, developers need to log in to the data dictionary management system through their account before the data dictionary management system can be used. At this time, the developer indicates the identity of the developer when registering an account. On this basis, different developers have different functional permissions to ensure that developers with higher permissions can control the data dictionary management system.

In the embodiment, the data dictionary is stored in the server, and the server is used to provide services to the client. The server is located in the server, which refers to a computer system in the network that can provide certain services to other machines. The server can be one physical entity or multiple physical entities. In the embodiment, as shown in Figure 1, the server 20 is connected to the client 10, and the server 20 can communicate with the client 10, so that the data dictionary management system can access the data dictionary stored in the server, where the communication The implementation method is currently not limited. The server and client can use multiple communication methods, and different implementation methods can be selected based on different communication requirements. In one embodiment, the data dictionary management system is encapsulated with a universal data dictionary model layer, so that the data dictionary management system supports obtaining dictionary data through HyperText Transfer Protocol (HTTP).

The data dictionary includes at least one dictionary type, where the dictionary type is used to record dictionary data. For example, the dictionary type can be a data type, a label style, a label name, etc. The dictionary type can be set according to actual needs, and is not detailed in this embodiment. limited. Dictionary data is used to record specific data under dictionary type. For example, the dictionary data includes a key-value pair, in which the key data and the value data correspond one-to-one. The key data is used for transmission in the front-end and back-end or for logical judgment in the code, while the value data is used for making judgments to developers in the front-end. Display so that developers can understand the specific meaning of the key, and the value data can be set according to actual needs. For example, the key data of one key-value pair is "string" and the value data is "string"; the key data of another key-value pair is "number" and the value data is "data", etc.

In one embodiment, the data dictionary management system is encapsulated with a universal dictionary translation method. After inputting the data dictionary and the key data to be converted in the data dictionary, the data dictionary management system can complete the conversion from key data to value data by calling the universal dictionary translation method. conversion between. In another embodiment, the data dictionary management system also encapsulates general React components, where components are encapsulated interface components with independent functions. React components define each module with relatively independent functions on the interface as a component, and then Small components are combined or nested to form large components, and finally the overall interface is constructed. The data dictionary management system supports consuming <DictSelectkey={DictionaryType.PropertyDataType}/> by passing in the dictionary type, that is, searching for key data from the dictionary type.

As shown in Figure 2, Figure 2 is a schematic flow chart of the data dictionary management method provided by the embodiment of the present invention. The data dictionary management method provided by the embodiment of the present invention includes steps 110 to 160:

Step 110: Display the interactive interface of the data dictionary management system on the client. The interactive interface displays type adding controls and data type labels. Each data type label corresponds to a dictionary type.

After developers log in to the data dictionary management system through the client, the data dictionary management system will display an interactive interface on the client. The interactive interface is the interface for developers to interact with the data dictionary management system. For example, the interactive interface may be a graphical user interface (GUI). A graphical user interface refers to a computer operation interface displayed graphically. Developers can manipulate the graphical user interface by using input devices such as a mouse or a trackpad. icons, controls or menu options to control the data dictionary management system to perform corresponding functions, such as adding, deleting or editing dictionary data in the data dictionary. In the embodiment, when the data dictionary management system is SAAS, the client is a browser on an electronic device, and after the developer logs in to the data dictionary management system through the browser, the interactive interface displayed by the data dictionary management system is a web page in the browser. Open interface.

In the embodiment, the interactive interface of the data dictionary management system displays type adding controls and data type labels, where the control is an object that developers can interact with through an interactive device to input or operate data, and the way developers interact with the control It can be set according to actual needs. For example, the developer can click the control with the mouse or operate the control with gestures, etc., which are not specifically limited in this embodiment. In the embodiment, the type adding control is used to add a dictionary type, and the data type label is used to select a dictionary type. Each data type label corresponds to a dictionary type, that is, the developer can select the corresponding dictionary type by operating different data type labels. dictionary type. In one embodiment, after the developer starts the data dictionary management system, the initial interface displayed by the data dictionary management system is as shown in Figure 3. The type addition controls in Figure 3 are "Add Type", "A Dictionary Type" and "B Dictionary type"..."N dictionary type" is the data type tag.

Step 120: In response to the first trigger operation acting on the type adding control, display the type adding sub-interface.

In the embodiment, when the developer needs to add a dictionary type to the data dictionary, he or she can perform a first triggering operation on the type adding control in the interactive interface, where the first triggering operation refers to an operation of triggering the type adding control. For example, the developer can Click the type adding control in the interactive interface by operating the mouse, thereby performing the first triggering operation on the type adding control. The data dictionary management system responds to the first trigger operation acting on the type adding control and displays the adding sub-interface, where the type adding sub-interface is used for developers to input the dictionary type that needs to be added.

Step 130: Add the first dictionary type to the data dictionary according to the first input data received through the type adding sub-interface, and update the display data type label.

After the data dictionary management system displays the type adding sub-interface, the developer can enter the first input data in the type adding sub-interface, where the first input data is used to set the new dictionary type. For example, as shown in Figure 4, the first input box for entering the dictionary type is displayed in the type adding sub-interface. The developer enters the first dictionary type in the first input box and then triggers the "OK" control, that is The first input data (including the first dictionary type) may be sent to the data dictionary management system. After receiving the first input data, the data dictionary management system determines the first dictionary type input by the developer, and adds the developer's information to the data dictionary stored on the server by calling the interface for modifying the data dictionary in the server. The input first dictionary type is updated at the same time, and the currently displayed data type label is updated, and a data type label corresponding to the newly added first dictionary type is added and displayed. In one embodiment, the data dictionary management system can directly display the first dictionary type on the data type label; in another embodiment, in order to make it easier for other developers to distinguish and identify the data type label, the type adding sub-interface also has A second input box for inputting the Chinese name of the dictionary type is displayed. As shown in Figure 5, the developer entered the first dictionary type in the first input box and entered the corresponding name of the first dictionary type in the second input box. After the Chinese name of the first dictionary type, the "OK" control is triggered to send the first input data (including the first dictionary type and the Chinese name of the first dictionary type) to the data dictionary management system. After receiving the first input data, the data dictionary management system determines the mapping relationship between the first dictionary type and the Chinese name of the first dictionary type, and when updating the display data type label, in the data type corresponding to the first dictionary type The Chinese name of the first dictionary type associated with the first dictionary type is displayed on the label. The data dictionary management system can also save the first dictionary type and the Chinese name of the first dictionary type together in the data dictionary, and subsequently obtain the Chinese name of the first dictionary type together when obtaining the first dictionary type.

It can be understood that the type adding sub-interface in Figures 4 and 5 is displayed on the interactive interface. Figures 4 and 5 are just examples of the type adding sub-interface. The type adding sub-interface is not specifically limited in this embodiment.

Step 140: In response to the second trigger operation acting on the data type label, obtain the dictionary data corresponding to the second dictionary type from the data dictionary and display it in the data display area, and display the data adding control in the data display area. Second The dictionary type is determined based on the data type tag acted upon by the second triggering operation.

For dictionary data contained in different dictionary types, developers can view the dictionary data by operating the data type tag corresponding to the dictionary type. Specifically, for the data type labels displayed on the interactive interface, developers can select the data type labels by operating the data type labels. For example, the developer can select the data type label by clicking the data type label displayed on the interactive interface with the mouse, thereby sending the second trigger operation to the data dictionary management system. The data dictionary management system responds to the second trigger operation after receiving it, determines the data type tag acted upon by the second trigger operation, and determines the second dictionary type corresponding to the data type tag.

After determining the second dictionary type, the data dictionary management system can obtain dictionary data corresponding to the second dictionary type from the data dictionary, and display the dictionary corresponding to the second dictionary type on the data display area of the interactive interface data, and display the data adding control, which is used to add dictionary data. The data display area refers to the area used to display dictionary data. The location and area of the data display area can be set during the development process of the data dictionary management system. For example, the data display area can be set on the right side of the interactive interface, as shown in Figure 6 As shown, the data adding control in Figure 6 is "Add Data". It can be understood that the position and area of the data display area are not specifically limited in this embodiment.

Step 150: In response to the third trigger operation acting on the data adding control, display the data adding sub-interface.

In the embodiment, when dictionary data is displayed in the data display area of the interactive interface, the developer can further add dictionary data. Specifically, after the developer operates the data type tag corresponding to the third dictionary type, the data dictionary management system displays the dictionary data corresponding to the third dictionary type in the data display area. At this time, the developer can further operate the data adding control displayed on the data display area to add dictionary data in the third dictionary type. For example, the developer can click the data adding control displayed on the data display area with the mouse, thereby sending the third triggering operation to the data dictionary management system. The data dictionary management system responds to the third trigger operation after receiving it, and displays a data adding sub-interface on the interactive interface, where the data adding sub-interface is used for developers to input the dictionary data that needs to be added.

Step 160: According to the second input data received through the data adding sub-interface, add dictionary data to the third dictionary type in the data dictionary and update the display data display area. The third dictionary type is corresponding to the dictionary data currently displayed in the data display area. Dictionary type.

When the data adding sub-interface is displayed on the interactive interface, the developer can enter the second input data in the data adding sub-interface, where the second input data is used to set the newly added dictionary data. In the embodiment, an input box for inputting dictionary data is displayed in the data adding sub-interface, as shown in Figure 7. After the developer inputs the dictionary data in the input box and confirms it, the developer can send it to the data dictionary management system in the input box. Enter the second input data. The data dictionary management system receives the second input data through the data adding sub-interface, determines the dictionary data in the second input data, and adds the dictionary data added by the developer to the third dictionary type of the data dictionary. After the data dictionary management system adds new dictionary data to the data dictionary, the data dictionary management system will re-update the dictionary data in the data display area to display the newly added dictionary data.

It can be understood that the data adding sub-interface in Figure 7 is displayed on the interactive interface. Figure 7 is only an example of the data adding sub-interface. In this embodiment, the data adding sub-interface is not specifically limited. In addition, it should be noted that the steps of the data dictionary management method provided by the embodiment of the present invention do not have a strict execution sequence. For example, the developer can also directly execute step 140 after the data dictionary management system is started. In this embodiment The execution order of the steps is not strictly limited.

As mentioned above, the embodiment of the present invention provides a data dictionary management method. After the developer logs in to the data dictionary management system through the client, the data dictionary management system will display the interactive interface on the client and display the type adding control on the interactive interface. , data type label and data adding control. By operating the type adding control, data type label and data adding control respectively, developers can add the dictionary type of the data dictionary, view the dictionary data in the dictionary type and add the dictionary data of the data dictionary. . In the embodiment of the present invention, developers can log in to the data dictionary management system through the client and use the data dictionary management system to view and modify the data dictionary. There is no need for a specific database administrator to manage the data dictionary on the server. , the management process of the data dictionary is more flexible, the management efficiency of the data dictionary is improved, and the technical problem of low efficiency of data dictionary management in the existing technology is solved.

In the process of managing the data dictionary based on the above data dictionary management method, it was found that for developers, because the developer's professional knowledge is not as good as that of the database administrator, even after the dictionary data is displayed in the data display area, the developer cannot It may be difficult to read and understand the dictionary data. Based on this, the present invention provides another embodiment. In this embodiment, the dictionary data includes key data and value data.

In this embodiment, when the dictionary data is displayed in the data display area, the developer can clarify the corresponding meaning of the dictionary data. The dictionary data includes key data and value data. When adding dictionary data, the developer needs to add the dictionary data to the data display area. Add sub-interface to input key data and value data. For example, as shown in Figure 8, the data adding sub-interface includes a third input box for entering key data and a fourth input box for entering value data. The developer enters the third input box and the fourth input box respectively. After entering the key data and value data into the box, click the OK button to send the second input data (including key data and value data) to the data dictionary management system, so that the data dictionary management system can add the key data and value data to In the dictionary type corresponding to the data dictionary.

In step 140, dictionary data corresponding to the second dictionary type is obtained from the data dictionary and displayed in the data display area, including:

Step 141: Obtain key data and value data corresponding to the second dictionary type from the data dictionary.

Step 142: Display key data and value data corresponding to the second dictionary type in the data display area.

Correspondingly, when obtaining dictionary data in this embodiment, it is necessary to obtain key data and value data corresponding to the second dictionary type, and display the key data and value data in the data display area. In this embodiment, key data and value data are displayed simultaneously in the data display area, so that developers can know the specific meaning of the corresponding key data by viewing the value data in the data display area, which facilitates developers to understand the data dictionary. Specific content, so that non-database administrators can also participate in the modification and management of the data dictionary. In one embodiment, when displaying dictionary data, the data display area also displays the dictionary type to which the dictionary data belongs and the ID (Identity document) of the dictionary data. For example, as shown in Figure 9, the current document in Figure 9 The selected data type label is the data type, and the dictionary type corresponding to the data type is PropertyDataType.

Based on the above embodiments, the data dictionary management method also includes:

Step 170: In response to the third trigger operation acting on the data type tag, display the type management interface. The type management interface includes a type editing control and a type deletion control.

In one embodiment, developers can further manage dictionary types that already exist in the data dictionary. Specifically, the developer can perform the third trigger operation on the data type label displayed on the interactive interface, so that the data dictionary management system displays the type management interface. The type management interface is used by the developer to perform the third trigger operation on the data type. The dictionary type corresponding to the label is managed. For example, the developer can use the mouse to double-click or right-click the data type label to perform a third triggering operation on the data type label. In another embodiment, each data type label is also correspondingly displayed with a label editing control, and developers can also perform a third triggering operation on the data type label by triggering the label editing control.

After the data dictionary management system receives the third trigger operation that acts on the data type tag, it will display the type management interface. The type management interface includes a type editing control and a type deletion control. The type editing control is used to edit dictionary types, and the type The delete control is used to delete dictionary types. As shown in Figure 10, the "..." displayed after the data type label in Figure 10 is the label editing control. After clicking the label editing control, the data dictionary management system will display the type management interface. In the type management interface, "Edit" "Delete" is the type to edit the control, and "Delete" is the type to delete the control.

Step 180: In response to the fourth trigger operation acting on the type editing control, display the type editing sub-interface.

After the data dictionary management system displays the type management interface, the developer can perform the fourth triggering operation on the type editing control through the interactive device. The data dictionary management system responds to the fourth triggering operation on the type editing control and further displays the type editing subroutine. Interface, the type editing sub-interface is used to edit dictionary types.

Step 190: Edit the fourth dictionary type in the data dictionary according to the third input data received through the type editing sub-interface, and update the display data type label. The fourth dictionary type is confirmed according to the data type label of the third trigger operation. .

After the data dictionary management system displays the type editing sub-interface, the developer can re-edit the fourth dictionary type corresponding to the data type label affected by the third triggering operation in the type editing sub-interface. Exemplarily, the type editing sub-interface displays a fifth input box for re-entering the dictionary type and a sixth input box for re-entering the Chinese name of the dictionary type. Similar to the interface in Figure 5, the developer enters the fifth input box in the fifth input box. After the dictionary type is entered in and the Chinese name of the dictionary type is entered in the sixth input box, the "OK" control is triggered to send the third input data (including the entered dictionary type and the entered Chinese name of the dictionary type) to the data dictionary management system. . After receiving the third input data, the data dictionary management system can modify and edit the fourth dictionary type in the data dictionary according to the dictionary type in the third input data, and at the same time, according to the Chinese name of the dictionary type in the third input data, The data type label corresponding to the fourth dictionary type displayed on the interactive interface is updated and displayed.

Step 1100: In response to the fifth trigger operation acting on the type deletion control, delete the fourth dictionary type and the dictionary data corresponding to the fourth dictionary type in the data dictionary, and update the display data type label and data display area.

In addition, developers can also delete dictionary types in the display type management interface. Specifically, the developer can perform the fifth trigger operation on the type delete control through the interactive device, such as clicking the type delete control with the mouse, etc. The data dictionary management system responds to the fifth trigger operation on the type delete control. In the data dictionary , delete the fourth dictionary type corresponding to the data type label of the third trigger operation and the dictionary data corresponding to the fourth dictionary type, and at the same time update the data type label and data display area displayed on the interactive interface show.

On the basis of the above embodiment, a data editing control and a data deleting control corresponding to each dictionary data are also displayed in the data display area.

In embodiments, developers can also manage the dictionary data displayed in the data display area in the data dictionary management system, such as editing and deleting. Specifically, the data display area also displays a data editing control and a data deletion control corresponding to each dictionary data. The data editing control is used to edit the dictionary data, and the data deletion control is used to display the dictionary data. The display positions of the edit control and the data deletion control in the data display area can be set according to actual needs. For example, they can be displayed at the head of the dictionary data or at the tail of the dictionary data. There are no specific limitations in this embodiment, as shown in Figure As shown in Figure 11, the "edit" and "delete" displayed at the end of each dictionary data in Figure 11 are data editing controls and data deleting controls respectively.

Data dictionary management methods also include:

Step 1110: In response to the sixth trigger operation acting on the data editing control, display the data editing sub-interface.

In this embodiment, the developer can edit the dictionary data by operating the data editing control displayed on the data display area. Specifically, the developer can perform the sixth triggering operation on the data editing control through an interactive device, such as clicking the data editing control with a mouse. The data dictionary management system responds to the sixth trigger operation acting on the data editing control and displays the data editing sub-interface, where the data editing sub-interface is used by the developer to display the first dictionary corresponding to the data editing control acted on by the sixth triggering operation. Data is edited.

Step 1120: Edit the first dictionary data in the data dictionary according to the fourth input data received through the data editing sub-interface, and update the display data display area. The first dictionary data is confirmed according to the data editing control functioned by the sixth trigger operation. .

After the data dictionary management system displays the data editing sub-interface, the developer can re-edit the first dictionary data in the data editing sub-interface. Exemplarily, the data editing sub-interface displays a seventh input box for re-entering key data and an eighth input box for re-entering value data. Similar to Figure 8, the developer enters the key in the seventh input box. After the data and value data are entered in the eighth input box, the "OK" control is triggered to send the fourth input data (including the input value data and key data) to the data dictionary management system. After receiving the fourth input data, the data dictionary management system can modify and edit the first dictionary data in the data dictionary based on the value data and key data in the fourth input data, and update the data display area of the interactive interface. show.

Step 1130: In response to the seventh trigger operation acting on the data deletion control, delete the second dictionary data in the data dictionary and update the display data display area. The second dictionary data is confirmed according to the data deletion control acting on the seventh trigger operation.

In addition, when developers need to delete dictionary data, developers can do so by operating the data display area to the data deletion control corresponding to the dictionary data. Specifically, for the second dictionary data that needs to be deleted, the developer can perform the seventh trigger operation on the data deletion control corresponding to the second dictionary data, and the data dictionary management system performs the seventh trigger operation on the data deletion control. Correspondingly, delete the second dictionary data in the data dictionary, and update the data display area.

As mentioned above, when the developer needs to manage the dictionary types in the data dictionary, the developer can perform the third triggering operation on the data type label displayed on the data dictionary management system, so that the data dictionary management system displays the type management interface. Developers can further trigger the type editing control and type deletion control in the type management interface to edit and delete the dictionary types in the data dictionary. In addition, the data display area of the data dictionary management system also displays data editing controls and data deletion controls corresponding to each dictionary data. Developers can modify the dictionary in the data dictionary by triggering the data editing controls and data deletion controls. Data can be edited and deleted. In the embodiment of the present invention, developers can manage dictionary types and dictionary data in the data dictionary through the data dictionary management system. There is no need for a specific database administrator to manage the data dictionary on the server, which further improves the efficiency of the data dictionary. Management efficiency.

During the entire process from development to release of a project, multiple environments will be used to test and run the project, and this environment is the project environment. In the process of multi-project environment development, as the project progresses, for different project environments, developers need to set up data dictionaries corresponding to different project environments, such as a data dictionary corresponding to the development environment, and a data dictionary corresponding to the test environment. The data dictionary and the data dictionary corresponding to the production environment, etc. During the development process of the project, it is often necessary to synchronize the data dictionaries of different project environments. Synchronizing the data dictionaries of different project environments can ensure data consistency in different project environments and avoid errors and exceptions caused by data inconsistency. In the prior art, when synchronizing data dictionaries in a multi-project environment, the database administrator generally needs to perform manual synchronization. This synchronization method is very prone to errors and omissions, resulting in data dictionary synchronization failure. Based on this, embodiments of the present invention also provide another data dictionary management method. The data dictionary management method in the flow chart shown in FIG. 12 is a specific embodiment of the aforementioned data dictionary management method. In this embodiment, the server stores dictionary data corresponding to different project environments, and the interactive interface also displays synchronization environment controls. The "synchronization environment" in Figure 13 is the synchronization environment control. The synchronization environment control is used to Synchronize dictionary data corresponding to different project environments, where the purpose of synchronization is to make the two dictionary data the same. The data dictionary management method includes steps 210 to 290:

Step 210: Display the interactive interface of the data dictionary management system on the client. The interactive interface displays type adding controls and data type labels. Each data type label corresponds to a dictionary type.

Step 220: In response to the first trigger operation acting on the type adding control, display the type adding sub-interface.

Step 230: Add the first dictionary type to the data dictionary according to the first input data received through the type adding sub-interface, and update the display data type label.

Step 240: In response to the second trigger operation acting on the data type label, obtain the dictionary data corresponding to the second dictionary type from the data dictionary and display it in the data display area, and display the data adding control in the data display area. Second The dictionary type is determined based on the data type tag acted upon by the second triggering operation.

Step 250: In response to the third trigger operation acting on the data adding control, display the data adding sub-interface.

Step 260: According to the second input data received through the data adding sub-interface, add dictionary data to the third dictionary type in the data dictionary and update the display data display area. The third dictionary type is corresponding to the dictionary data currently displayed in the data display area. Dictionary type.

Step 270: In response to the eighth trigger operation acting on the synchronization environment control, display the synchronization environment sub-interface.

In the embodiment, when the developer needs to synchronize the dictionary data of different project environments, the developer can perform the eighth triggering operation on the synchronization environment control displayed on the interactive interface, such as clicking the synchronization environment control through the mouse. The data dictionary management system responds to the eighth trigger operation acting on the synchronization environment control and displays the synchronization environment sub-interface. The synchronization environment sub-interface is used for developers to select the data dictionary that needs to be synchronized.

Step 280: Determine the first project environment and the second project environment according to the fifth input data received through the synchronization environment sub-interface.

After the data dictionary management system displays the synchronization environment sub-interface, developers can select the dictionary data of the two development environments that need to be synchronized by entering the fifth input data in the synchronization environment sub-interface. For example, the synchronization environment sub-interface displays a selection box for the first project environment and a selection box for the second project environment. As shown in Figure 14, the developer can click the selection box with the mouse, and the drop-down displayed under the selection box Select the first project environment and the second project environment from the list. It can be understood that both the first project environment and the second project environment are project environments corresponding to the dictionary data stored on the server. After the developer selects the first project environment and the second project environment, he can click the "Confirm" button in the synchronization environment sub-interface to send the fifth input data (including the selected first project environment and the second project environment) to the data dictionary management system. 2 project environment). The data dictionary management system determines the first project environment and the second project environment that need to be synchronized based on the received fifth input data.

It can be understood that the synchronization environment sub-interface in Figure 14 is displayed on the interactive interface. Figure 14 is only an example of the synchronization environment sub-interface. In this embodiment, the synchronization environment sub-interface is not specifically limited.

Step 290: Synchronize the second data dictionary corresponding to the second project environment in the server to the first data dictionary corresponding to the first project environment.

After the data dictionary management system determines the first project environment and the second project environment that need to be synchronized, the data dictionary management system can synchronize the second data dictionary corresponding to the second project environment to the first project environment corresponding to the server. first data dictionary so that the second data dictionary is the same as the first data dictionary. For example, in the process of synchronizing the first data dictionary and the second data dictionary, the data dictionary management system can obtain dictionary data corresponding to different dictionary types in the first data dictionary and the second data dictionary, And compare the differences between the dictionary data corresponding to the same dictionary type in the first data dictionary and the second data dictionary, obtain the comparison result, and modify the dictionary data in the second data dictionary according to the comparison result, so that the second data The dictionary data in the dictionary is the same as the dictionary data in the first data dictionary.

Based on the above embodiment, in step 290, the second data dictionary corresponding to the second project environment in the server is synchronized to the first data dictionary corresponding to the first project environment, including:

Step 291: Obtain the first login credentials corresponding to the first data dictionary of the first project environment and the second login credentials corresponding to the second data dictionary of the second project environment.

In this embodiment, the data dictionary management system can obtain the data dictionary by directly logging in to the data dictionary in the server. However, considering that the method of directly logging in to the data dictionary has a poor security factor and risks being restricted from the request source. Therefore, this embodiment proposes a new login method to obtain the data dictionary. The implementation principle is to simulate the login process and obtain the data dictionary through the login credentials of the data dictionary, where the login credentials are the credentials used by the data dictionary to distinguish the identities of different developers. . In embodiments, the login credentials can be tokens or cookies, where cookies are small text files stored on the client. They are set by the server in the HTTP response header and sent to the client. After the client receives the cookie, it will be automatically stored locally. Token is an encrypted string that is usually stored in the client's browser cache or can also be stored in the server.

Specifically, during the synchronization process, the data dictionary management system first needs to obtain the first login credentials corresponding to the first data dictionary of the first project environment, and the second login credentials corresponding to the second data dictionary of the second project environment. Login credentials. In the embodiment, the data dictionary management system can call the headless browser to access the first data dictionary and the second data dictionary in the server, enable the highest kernel authority of the headless browser, and thereby obtain the first login credentials carrying the httponly attribute and The second login credential, where the httponly attribute is used to inform the headless browser that the first login credential and the second login credential are not allowed to be read by other devices, prohibiting the headless browser from opening the first login credential and the second login credential, thereby avoiding the third login credential. The first and second login credentials are leaked to ensure data security.

Based on the above embodiment, in step 291, the first login credentials corresponding to the first data dictionary of the first project environment and the second login credentials corresponding to the second data dictionary of the second project environment are respectively obtained, include:

Step 2911: Obtain the first account in the first project environment and the second account in the second project environment. The first account and the second account only have data dictionary synchronization permissions.

In one embodiment, when obtaining the first login credential and the second login credential, the data dictionary management system may obtain the first account in the first project environment and the second account in the second project environment, where the first account and the second account are The second account is used to access the first data dictionary and the second data dictionary respectively, and the first account and the second account only have data dictionary synchronization permissions. The data dictionary synchronization permissions are the permissions for synchronizing the data dictionary. The first account and the second account can be applied for in advance by the developer in the first project environment and the second project environment respectively during the project development process.

Step 2912: Log in to the first data dictionary through the first account, and obtain the first login credentials of the first data dictionary.

Step 2913: Log in to the second data dictionary through the second account, and obtain the second login credentials of the second data dictionary.

After obtaining the first account and the second account, the data dictionary management system can log in to the first data dictionary and the second data dictionary through the first account and the second account respectively, thereby obtaining the login credentials and credentials of the first data dictionary. Login credentials for the second data dictionary.

The above is the specific process of obtaining login credentials.

Step 292: Obtain the first dictionary type list corresponding to the first data dictionary from the server based on the first login credential, and obtain the second dictionary type list corresponding to the second data dictionary from the server based on the second login credential. , the dictionary type list includes the dictionary type that contains the data dictionary.

After obtaining the first login credential of the first data dictionary and the second login credential of the second data dictionary, the data dictionary management system can obtain the third login credential corresponding to the first data dictionary from the server based on the first login credential. a dictionary type list, and obtaining a second dictionary type list corresponding to the second data dictionary in the server according to the second login credentials. Among them, it should be noted that the dictionary type list includes all dictionary types of data dictionaries. That is, the first dictionary type list includes all dictionary types of the first data dictionary, and the second dictionary type list includes all dictionary types of the second data dictionary.

Step 293: Synchronize the second data dictionary in the server to the first data dictionary according to the first dictionary type list and the second dictionary type list.

After the data management system obtains the first dictionary type list and the second dictionary type list, it can compare the first data dictionary and the second data dictionary under different dictionary types based on the first dictionary type list and the second dictionary type list. Dictionary data is obtained to obtain a comparison result, which includes the difference in dictionary data between the first data dictionary and the second data dictionary under each dictionary type. Finally, the data management system can modify the dictionary data in the second data dictionary in the server based on the comparison result, thereby keeping the second data dictionary synchronized with the first data dictionary.

Based on the above embodiment, in step 293, the second data dictionary in the server is synchronized to the first data dictionary according to the first dictionary type list and the second dictionary type list, including:

Step 2931: Obtain the third dictionary data under each dictionary type of the first data dictionary according to the first dictionary type list.

After obtaining the first dictionary type list, the data dictionary management system can traverse each dictionary type in the first dictionary type list, thereby obtaining the third dictionary data under each dictionary type.

Step 2932: Obtain the fourth dictionary data under each dictionary type of the second data dictionary according to the second dictionary type list.

Similarly, after obtaining the second dictionary type list, the data dictionary management system can traverse each dictionary type in the second dictionary type list, thereby obtaining the fourth dictionary data under each dictionary type.

Step 2933: Compare the third dictionary data and the fourth dictionary data under each dictionary type to obtain the comparison result.

After obtaining the third dictionary data and the fourth dictionary data under each dictionary type, data management can compare the third dictionary data and the fourth dictionary data under each dictionary type to determine the third dictionary data under each dictionary type. The difference between the third dictionary data and the fourth dictionary data. The types of differences include redundant dictionary data, missing dictionary data, and different dictionary data. Redundant dictionary data means that the third dictionary data of the same dictionary type is more than the fourth dictionary data. , the dictionary data is missing, that is, the third dictionary data under the same dictionary type is less than the fourth dictionary data, and the dictionary data is different, that is, the values of the fourth dictionary data corresponding to the third dictionary data under the same dictionary type are different. In one embodiment, the data dictionary management system can compare the differences between the third dictionary data and the fourth dictionary data under multiple dictionary types at the same time to speed up the comparison efficiency. It is understandable that the number of dictionary types that can be compared at the same time is Determined by the computing power of the server.

Step 2934: Synchronize the second data dictionary in the server according to the comparison result, so that the second data dictionary is the same as the first data dictionary.

After obtaining the comparison results, the data dictionary management system can respectively request the interface in the server to modify the second data dictionary according to the comparison results to complete the synchronization between the second data dictionary and the first data dictionary, so that The first data dictionary and the second data dictionary are the same. For example, for the difference types that are redundant in the dictionary data, the data dictionary management system can add the missing dictionary data in the second data dictionary. For the difference types that are missing from the data dictionary, the data dictionary management system can add the missing dictionary data in the second data dictionary. Delete redundant dictionary data in the data dictionary. For different difference types in the data dictionary, the data dictionary management system can modify the different dictionary data in the second data dictionary to be the same as the dictionary data in the first data dictionary. In one embodiment, after calling the server's interface to modify the second data dictionary, the data dictionary management system can further count the success and failure of each interface in modifying the second data dictionary, and generate a synchronization report based on the success and failure. , developers can know the synchronization results of the data dictionary by viewing the synchronization report.

The above is the specific process of synchronizing the data dictionary.

In another embodiment, when synchronizing the first data dictionary and the second data dictionary, the data management system can also call a preset script to cause the preset script to synchronize the second data dictionary corresponding to the second project environment in the server. The data dictionary is synchronized to the first data dictionary corresponding to the first project environment, where the preset script refers to a preset script. The script is an executable file written in a certain format using a specific descriptive language. Development Personnel can write the steps for synchronizing the data dictionary into a preset script in advance, so that the preset script can automatically execute the steps for synchronizing the data dictionary. The sequence diagram is shown in Figure 15. It can be understood that the process of synchronizing the first data dictionary and the second data dictionary by the preset script is the same as the above-mentioned synchronization process. For details, reference can be made to the above-mentioned synchronization process, which will not be described again in this embodiment.

In addition, it should be noted that the steps of the data dictionary management method provided by the embodiment of the present invention do not have a strict execution sequence. For example, after the data dictionary management system is started, the developer can also directly execute step 270 to perform data processing. In the process of dictionary synchronization, the execution order of the steps is not strictly limited in this embodiment.

As mentioned above, the data dictionary management system of the embodiment of the present invention also has the function of synchronizing data dictionaries in different environments. Developers only need to input the two data dictionaries that need to be synchronized on the interactive interface, and the data dictionary management system can The two data dictionaries are automatically synchronized without human intervention during the synchronization process, which greatly improves the probability of synchronization of the data dictionaries and avoids the problem of data inconsistency caused by repeated manual input of dictionary data. In addition, automatic synchronization of dictionary data can also improve maintainability during project development and reduce maintenance costs.

Embodiments of the present invention also provide a data dictionary management system. The data dictionary management system logs in through a client. The client communicates with the server that stores the data dictionary. The data dictionary includes at least one dictionary type. The dictionary type is used for Record dictionary data.

The data dictionary management system is used to display the interactive interface of the data dictionary management system on the client. The interactive interface displays type adding controls and data type labels. Each data type label corresponds to a dictionary type.

The data dictionary management system is configured to respond to the first trigger operation acting on the type adding control and display the type adding sub-interface.

The data dictionary management system is configured to add a first dictionary type to the data dictionary according to the first input data received through the type adding sub-interface, and update the display data type label.

The data dictionary management system is used to respond to the second trigger operation acting on the data type tag, obtain the dictionary data corresponding to the second dictionary type from the data dictionary and display it in the data display area, and display the data adding control in the data display area. , the second dictionary type is confirmed according to the data type tag acted upon by the second triggering operation.

The data dictionary management system is used to respond to the third trigger operation acting on the data adding control and display the data adding sub-interface.

The data dictionary management system is used to add dictionary data to the third dictionary type in the data dictionary and update the display data display area according to the second input data received through the data adding sub-interface. The third dictionary type is the dictionary currently displayed in the data display area. The dictionary type corresponding to the data.

It can be understood that the data dictionary management system provided by the embodiment of the present invention can be used to execute the above-mentioned data dictionary management method. For the specific process, reference can be made to the data dictionary management method described in the above-mentioned embodiment, which will not be described again in this embodiment.

This embodiment also provides a data dictionary management device, as shown in Figure 16. Figure 16 is a schematic structural diagram of the data dictionary management device provided by this embodiment of the present invention. The data dictionary management device 30 includes a processor 300 and a memory 301;

The memory 301 is used to store the computer program 302 and transmit the computer program 302 to the processor 300;

The processor 300 is configured to execute the steps in the above-mentioned data dictionary management method embodiment according to the instructions in the computer program 302.

For example, the computer program 302 can be divided into one or more modules/units, and one or more modules/units are stored in the memory 301 and executed by the processor 300 to complete the present application. One or more modules/units may be a series of computer program instruction segments capable of completing specific functions. The instruction segments are used to describe the execution process of the computer program 302 in the data dictionary management device 30 .

The data dictionary management device 30 can be a computing device such as a desktop computer, a notebook, a handheld computer, a cloud server, etc. The data dictionary management device 30 may include, but is not limited to, a processor 300 and a memory 301. Those skilled in the art can understand that FIG. 16 is only an example of the data dictionary management device 30 and does not constitute a limitation on the data dictionary management device 30. It may include more or fewer components than shown in the figure, or some components may be combined. Or different components, for example, the data dictionary management device 30 may also include input and output devices, network access devices, buses, etc.

The processor 300 may be a central processing unit (CPU), or other general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), Ready-made field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

The memory 301 may be an internal storage unit of the data dictionary management device 30 , such as a hard disk or memory of the data dictionary management device 30 . The memory 301 can also be an external storage device of the data dictionary management device 30, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SD) card, or a flash memory equipped on the data dictionary management device 30. Flash Card, etc. Further, the memory 301 may also include both an internal storage unit of the data dictionary management device 30 and an external storage device. The memory 301 is used to store computer programs and other programs and data required by the data dictionary management device 30 . The memory 301 can also be used to temporarily store data that has been output or is to be output.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

A unit described as a separate component may or may not be physically separate. A component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

Integrated units may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as independent products. Based on this understanding, the technical solution of the present invention is essentially or contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store computer programs. .

Embodiments of the present invention also provide a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to execute a data dictionary management method, which is suitable for a data dictionary management system. The data dictionary management system adopts The client logs in, and the client communicates with the server that stores the data dictionary. The data dictionary includes at least one dictionary type. The dictionary type is used to record dictionary data. The data dictionary management method includes:

Display the interactive interface of the data dictionary management system on the client. The interactive interface displays type addition controls and data type labels. Each data type label corresponds to a dictionary type;

In response to the first trigger operation acting on the type adding control, display the type adding sub-interface;

Add the first dictionary type to the data dictionary according to the first input data received through the type addition sub-interface, and update the display data type label;

In response to the second trigger operation acting on the data type label, obtain the dictionary data corresponding to the second dictionary type from the data dictionary and display it in the data display area, and display the data adding control in the data display area. The second dictionary type is based on The data type tag confirmation of the second trigger operation effect;

In response to the third trigger operation acting on the data adding control, display the data adding sub-interface;

According to the second input data received through the data adding sub-interface, add dictionary data to a third dictionary type in the data dictionary and update the display data display area. The third dictionary type is the dictionary type corresponding to the dictionary data currently displayed in the data display area.

Note that the above are only the preferred embodiments and the technical principles used in the embodiments of the present invention. Those skilled in the art will understand that the embodiments of the present invention are not limited to the specific embodiments here. Various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the embodiments of the present invention. Therefore, although the embodiments of the present invention have been described in detail through the above embodiments, the embodiments of the present invention are not limited to the above embodiments, and may also include more other equivalents without departing from the concept of the embodiments of the present invention. embodiments, and the scope of the embodiments of the present invention is determined by the scope of the appended claims.

Claims (12)

1. The data dictionary management method is suitable for a data dictionary management system, the data dictionary management system logs in through a client, the client is in communication connection with a server storing a data dictionary, the data dictionary comprises at least one dictionary type, the dictionary type is used for recording dictionary data, and the data dictionary management method comprises the following steps:

Displaying an interactive interface of the data dictionary management system at a client, wherein the interactive interface is provided with a type adding control and data type labels, and each data type label corresponds to one dictionary type respectively;

responding to a first triggering operation acting on the type adding control, and displaying a type adding sub-interface;

adding a first dictionary type into the data dictionary according to the first input data received through the type adding sub-interface, and updating and displaying the data type label;

responding to a second triggering operation acting on the data type label, acquiring dictionary data corresponding to a second dictionary type from the data dictionary, displaying the dictionary data in a data display area, and displaying a data adding control in the data display area, wherein the second dictionary type is confirmed according to the data type label acted by the second triggering operation;

responding to a third triggering operation acting on the data adding control, and displaying a data adding sub-interface;

and adding dictionary data to a third dictionary type in the data dictionary according to the second input data received through the data adding sub-interface, and updating and displaying the data display area, wherein the third dictionary type is the dictionary type corresponding to the dictionary data currently displayed in the data display area.

2. The method of claim 1, wherein the dictionary data includes key data and value data;

the obtaining dictionary data corresponding to the second dictionary type from the data dictionary and displaying the dictionary data in a data display area includes:

acquiring key data and value data corresponding to the second dictionary type from the data dictionary;

and displaying key data and value data corresponding to the second dictionary type in the data display area.

3. The data dictionary management method of claim 1, further comprising:

responding to a third triggering operation acting on the data type label, and displaying a type management interface, wherein the type management interface comprises a type editing control and a type deleting control;

responding to a fourth triggering operation acting on the type editing control, and displaying a type editing sub-interface;

editing a fourth dictionary type in the data dictionary according to third input data received through the type editing sub-interface, updating and displaying the data type label, and confirming the fourth dictionary type according to the data type label with the third triggering operation function;

And deleting a fourth dictionary type and dictionary data corresponding to the fourth dictionary type in the data dictionary in response to a fifth triggering operation acting on the type deleting control, and updating and displaying the data type label and the data display area.

4. The data dictionary management method of claim 1, wherein the data display area further displays a data editing control and a data deleting control corresponding to each dictionary data, and the data dictionary management method further comprises:

responding to a sixth triggering operation acting on the data editing control, and displaying a data editing sub-interface;

editing first dictionary data in the data dictionary according to fourth input data received through the data editing sub-interface, updating and displaying the data display area, and confirming the first dictionary data according to the data editing control with the sixth triggering operation function;

and deleting the second dictionary data in the data dictionary in response to a seventh triggering operation acting on the data deleting control, updating and displaying the data display area, and confirming the second dictionary data according to the data deleting control acting on the seventh triggering operation.

5. The data dictionary management method of claim 1, wherein dictionary data corresponding to different project environments are stored in the server, the interactive interface further displays a synchronous environment control, and the data dictionary management method further comprises:

responding to an eighth triggering operation acting on the synchronous environment control, and displaying a synchronous environment sub-interface;

determining a first project environment and a second project environment according to fifth input data received through the synchronous environment sub-interface;

and synchronizing the second data dictionary corresponding to the second project environment in the server to be the first data dictionary corresponding to the first project environment.

6. The method according to claim 5, wherein synchronizing the second data dictionary corresponding to the second project environment in the server to the first data dictionary corresponding to the first project environment comprises:

and calling a preset script, and enabling the preset script to synchronize a second data dictionary corresponding to the second project environment in the server to be a first data dictionary corresponding to the first project environment.

7. The method according to claim 5, wherein synchronizing the second data dictionary corresponding to the second project environment in the server to the first data dictionary corresponding to the first project environment comprises:

respectively acquiring a first login credential corresponding to a first data dictionary of the first project environment and a second login credential corresponding to a second data dictionary of the second project environment;

acquiring a first dictionary type list corresponding to the first data dictionary from the server according to the first login credential, and acquiring a second dictionary type list corresponding to the second data dictionary from the server according to the second login credential, wherein the dictionary type list comprises dictionary types of the data dictionary;

and synchronizing the second data dictionary in the server to the first data dictionary according to the first dictionary type list and the second dictionary type list.

8. The method according to claim 7, wherein the acquiring the first login credentials corresponding to the first data dictionary of the first project environment and the second login credentials corresponding to the second data dictionary of the second project environment, respectively, comprises:

Acquiring a first account in the first project environment and a second account in the second project environment, wherein the first account and the second account only have data dictionary synchronization rights;

logging in the first data dictionary through the first account number to obtain a first login credential of the first data dictionary;

and logging in the second data dictionary through the second account number to obtain a second login certificate of the second data dictionary.

9. The method of claim 7, wherein synchronizing the second data dictionary in the server as the first data dictionary based on the first dictionary type list and the second dictionary type list, comprises:

acquiring third dictionary data of each dictionary type of the first data dictionary according to the first dictionary type list;

acquiring fourth dictionary data of each dictionary type of the second data dictionary according to the second dictionary type list;

comparing the third dictionary data with the fourth dictionary data under each dictionary type to obtain a comparison result;

and synchronizing a second data dictionary in the server according to the comparison result so that the second data dictionary is identical to the first data dictionary.

10. The data dictionary management system is characterized in that the data dictionary management system logs in through a client, the client is in communication connection with a server storing a data dictionary, the data dictionary comprises at least one dictionary type, and the dictionary type is used for recording dictionary data;

the data dictionary management system is used for displaying an interactive interface of the data dictionary management system on a client, wherein the interactive interface is displayed with a type adding control and data type labels, and each data type label corresponds to one dictionary type respectively;

the data dictionary management system is used for responding to a first trigger operation acting on the type adding control and displaying a type adding sub-interface;

the data dictionary management system is used for adding a first dictionary type into the data dictionary according to the first input data received through the type adding sub-interface, and updating and displaying the data type label;

the data dictionary management system responds to a second triggering operation acting on the data type label, dictionary data corresponding to a second dictionary type are obtained from the data dictionary and displayed in a data display area, a data adding control is displayed in the data display area, and the second dictionary type is confirmed according to the data type label acted by the second triggering operation;

The data dictionary management system is used for responding to a third triggering operation acting on the data adding control and displaying a data adding sub-interface;

and the data dictionary management system is used for adding dictionary data to a third dictionary type in the data dictionary according to the second input data received through the data adding sub-interface and updating and displaying the data display area, wherein the third dictionary type is the dictionary type corresponding to the dictionary data currently displayed in the data display area.

11. A data dictionary management apparatus, characterized in that the data dictionary management apparatus comprises a processor and a memory;

the memory is used for storing a computer program and transmitting the computer program to the processor;

the processor is configured to perform a data dictionary management method according to any one of claims 1-9 according to instructions in the computer program.

12. A storage medium storing computer executable instructions which, when executed by a computer processor, are adapted to carry out a data dictionary management method according to any one of claims 1-9.