CN117632958A - Database view configuration method, device, electronic equipment and storage medium - Google Patents
Database view configuration method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN117632958A CN117632958A CN202311599209.XA CN202311599209A CN117632958A CN 117632958 A CN117632958 A CN 117632958A CN 202311599209 A CN202311599209 A CN 202311599209A CN 117632958 A CN117632958 A CN 117632958A
- Authority
- CN
- China
- Prior art keywords
- view
- version
- database view
- historical
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000012986 modification Methods 0.000 claims abstract description 66
- 230000004048 modification Effects 0.000 claims abstract description 66
- 238000011144 upstream manufacturing Methods 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 7
- 238000001914 filtration Methods 0.000 claims description 5
- 230000008676 import Effects 0.000 claims description 5
- 238000012800 visualization Methods 0.000 claims description 5
- 238000012545 processing Methods 0.000 abstract description 12
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000009191 jumping Effects 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a database view configuration method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: responding to the first input, and displaying a version record table corresponding to the current database view; the version record table comprises version information of a plurality of historical versions corresponding to the current database view; responding to the second input, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version; and responding to the third input, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table. The method and the device provided by the invention realize the configuration and management of multiple versions of the database view, and improve the processing efficiency and the working efficiency of the user on the data.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a database view configuration method, apparatus, electronic device, and storage medium.
Background
With the development of the information age, the processing demands of users on data are higher and higher, and the processing logic of the data is also more and more complex. The database view provides a convenient way to access and manipulate data so that the data is easier for a user to understand and use. Thus, users are increasingly dependent on processing data through database views, and accordingly, the requirements of users for database view configuration are also increasing. On one hand, a user can perform trial calculation and analysis on the data index by continuously adjusting the configuration and the parameters of the database view; on the other hand, the user may view and adjust the configuration logic of the database view based on the results of the data analysis process. As the user performs multiple operations on the database view, multiple versions may be generated.
Therefore, how to configure and manage multiple versions of the database view, and to improve the processing efficiency of the user on the data, is a technical problem to be solved in the industry.
Disclosure of Invention
The application provides a database view configuration method, a device, electronic equipment and a storage medium, which are used for solving the technical problem of how to configure and manage multiple versions of a database view and improving the processing efficiency of a user on data.
The application provides a database view configuration method, which comprises the following steps:
receiving a first input of a user;
responding to the first input, and displaying a version record table corresponding to the current database view; the version record table comprises version information of a plurality of historical versions corresponding to the current database view;
receiving a second input from the user;
responding to the second input, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version;
receiving a third input from the user;
and responding to the third input, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table.
In some embodiments, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table, including:
Comparing the configuration information of the historical database view before modification with the configuration information of the historical database view after modification, and determining modification content corresponding to the configuration information;
determining database operation sentences corresponding to the modified contents;
based on the database operation statement, synchronously modifying configuration information of the associated historical database view corresponding to the historical database view;
generating version modification descriptions of each historical database view based on the modification content of the configuration information of each historical database view;
version information of each historical database view is updated based on the version modification description of each historical database view.
In some embodiments, the version information includes at least one of version basic information, parameter configuration information, view reference information, view field information, and view operation information.
In some embodiments, the version basic information includes at least one of a view number, a storage location, a view name, a version number, a creation time, a creation author, a version description, and a view baseline;
the parameter configuration information comprises at least one of a parameter field, a parameter name, a parameter type and a parameter default value;
The view reference information comprises upstream view information and reference filtering information;
the view field information includes at least one of a field dimension, a field number, a field name, a field type, a field size, a field source, a field definition, and a field operation;
the view operation information includes at least one of modification, import, save, visualization, run, and query.
In some embodiments, the associated historical database view corresponding to the historical database view is determined based on the steps of:
determining an upstream view corresponding to the historical database view;
determining a downstream view corresponding to the historical database view;
determining the upstream view and the downstream view as associated historical database views corresponding to the historical database views;
and associating the version number of the associated historical database view with the version number of the historical database view.
In some embodiments, the displaying the version record table corresponding to the current database view includes:
establishing view links corresponding to a plurality of historical versions based on the association relation among the historical versions corresponding to the current database view;
And visually displaying the historical versions based on the view link.
In some embodiments, the associations are upstream and downstream referencing relationships between the various historical versions.
The application provides a database view configuration device, comprising:
a display unit for receiving a first input of a user; responding to the first input, and displaying a version record table corresponding to the current database view; the version record table comprises version information of a plurality of historical versions corresponding to the current database view;
a selection unit for receiving a second input of a user; responding to the second input, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version;
a configuration unit for receiving a third input of a user; and responding to the third input, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table.
The present application provides an electronic device comprising a memory, in which a computer program is stored, and a processor arranged to execute the database view configuration method by means of the computer program.
The application provides a computer readable storage medium comprising a stored program, wherein the program executes the database view configuration method.
The method, the device, the electronic equipment and the storage medium for configuring the database view, respond to the first input of a user and display a version record table corresponding to the current database view; responding to a second input of the user, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version; responding to a third input of a user, modifying configuration information of the historical database view, synchronizing modification content corresponding to the configuration information to an associated historical database view corresponding to the historical database view, and updating version information of each historical database view in a version record table; the historical versions of the database view are summarized and managed uniformly through the version record table, any historical version can be selected for viewing according to the input of a user, when the configuration information of the historical database view is modified, the associated historical database view can be modified synchronously, and the version record table is updated, so that the configuration and management of multiple versions of the database view are realized, the requirements of actual application scenes can be met, the maintainability, flexibility and traceability of view configuration are improved, and the processing efficiency and the working efficiency of the user on data are improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the technical solutions of the present application or the prior art, the following description will briefly introduce the drawings used in the embodiments or the description of the prior art, and it is obvious that, in the following description, the drawings are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of a database view configuration method provided in the present application;
FIG. 2 is a second flow chart of the database view configuration method provided in the present application;
FIG. 3 is a schematic structural diagram of a database view configuration device provided in the present application;
fig. 4 is a schematic structural diagram of an electronic device provided in the present application.
Detailed Description
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like herein are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or units or modules is not necessarily limited to those steps or units or modules that are expressly listed or inherent to such process, method, article, or apparatus.
In the technical scheme of the application, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the client personal information all accord with the regulations of related laws and regulations, necessary security measures are adopted, and the public order harmony is not violated.
The existing database view configuration method has the following defects when managing multiple versions of the database view: 1. only the operation records of single interface breakpoints can be reserved, static section data accumulation is realized, the information quantity of versions is limited, and flexible and clear venation cannot be provided; 2. version information cannot be hooked with other associated interfaces and can only be identified manually, and under the condition of more version history, a great deal of manpower and time are required to be spent for completion, and then the version information is analyzed and adjusted, so that the cost is high; 3. each interface version can only be checked through the interface, if the historical configuration versions of a plurality of interfaces on the link are required to be checked at the same time, the interfaces need to be manually switched back and forth, and the query condition may also need to be repeatedly input for a plurality of times, which is complicated.
Fig. 1 is a schematic flow chart of a database view configuration method provided in the present application, and as shown in fig. 1, the method includes a step 110, a step 120, and a step 130.
Step 110, receiving a first input of a user; responding to the first input, and displaying a version record table corresponding to the current database view; the version record table comprises version information of a plurality of historical versions corresponding to the current database view.
Specifically, the execution subject of the database view configuration method provided in the embodiment of the present application is a database view configuration device. The apparatus may be implemented in software, for example a database view configuration program running in a computer, for example in Java language; devices that perform the database view configuration method, such as mobile terminals, tablet computers, desktop computers, or servers, may also be used.
The database view configuration apparatus may include a front end and a back end. The front end may include web pages or the like that are displayed to the user for viewing, for example, on a browser running on a computer or mobile terminal or the like. The background may be a server or the like that performs the database view configuration method.
Database view refers to a view in a computer database, which is a virtual table whose contents are defined by queries. As with the real table, the view contains a series of columns and rows with names. The current database view is the database view that the user is operating on. The view configuration is to generate a view by using a configuration method, and package SQL sentences (Structured Query Language, structured query sentences) generated by the view into Shell scripts to be put into a big data platform for operation through front-end interface configuration, so that big data processing and analysis are realized.
The user performs data operation on the current database view, so that the current database view is configured and updated, and a plurality of historical versions can be generated according to different configuration time. The historical version of the view is used for marking the configuration of the view, each time the configuration of the view is updated, a historical version is formed, and the view historical link can be managed by the view historical version.
The version record table is used for recording version information of each history version. The version information may include version number, creation time, creation author and version description, etc. Version information of each history version may be recorded in the version record table in the form of a configuration table.
The first input is an input operation of a user in the front-end page, and the input is used for triggering the database view configuration device to display a version record table corresponding to the current database view. The representation of the first input may include at least one of a physical key input, a touch operation input, and a voice input. For example, the user may implement the first input by clicking the 'history' button of the 'operations' line in the front page.
After the front-end page receives the first input, an operation corresponding to the first input is determined, so that in response to the operation, a version record table corresponding to the current database view is called from the background server, returned to the front-end page and displayed to the user.
Step 120, receiving a second input of the user; and responding to the second input, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version.
Specifically, the second input is an input operation by the user in the front-end page, the input being used to select the determination target history version in the version record table. The target historical version is the historical version that the user wants to view or configure. The second input has the same representation as the first input and will not be described here.
After receiving the second input, the front-end page determines an operation corresponding to the second input, so that in response to the operation, a target historical version selected by the user is determined in a plurality of version record tables, a historical database view corresponding to the target historical version is called from a background server, and the historical database view is returned to the front-end page and displayed for the user.
Step 130, receiving a third input of a user; and responding to the third input, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table.
Specifically, the third input is an input operation of the user in the front-end page, the input being used to modify the configuration information of the historical database view. The configuration information mainly includes parameter fields and the like in the historical database view, such as parameter fields, parameter names, parameter types, parameter default values and the like. The third input has the same representation as the first input and will not be described here.
Because the incidence relations may exist among the historical database views, the incidence relations can be data reference relations, and when configuration information of the historical database views is modified, modification contents corresponding to the configuration information can be synchronized to the incidence historical database views corresponding to the historical database views, so that incidence modification is realized. After the associated modification is completed, the version information of each historical database view can be correspondingly modified in the version record table, for example, the modification type, the modification reason and the modification time in the version information can be updated.
According to the database view configuration method, a version record table corresponding to a current database view is displayed in response to first input of a user; responding to a second input of the user, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version; responding to a third input of a user, modifying configuration information of the historical database view, synchronizing modification content corresponding to the configuration information to an associated historical database view corresponding to the historical database view, and updating version information of each historical database view in a version record table; the historical versions of the database view are summarized and managed uniformly through the version record table, any historical version can be selected for viewing according to the input of a user, when the configuration information of the historical database view is modified, the associated historical database view can be modified synchronously, and the version record table is updated, so that the configuration and management of multiple versions of the database view are realized, the requirements of actual application scenes can be met, the maintainability, flexibility and traceability of view configuration are improved, and the processing efficiency and the working efficiency of the user on data are improved.
It should be noted that each embodiment of the present application may be freely combined, permuted, or executed separately, and does not need to rely on or rely on a fixed execution sequence.
In some embodiments, step 130 comprises:
comparing the configuration information of the history database view before modification with the configuration information of the history database view after modification, and determining modification content corresponding to the configuration information;
determining database operation sentences corresponding to the modified content;
based on the database operation sentences, synchronously modifying the configuration information of the associated historical database view corresponding to the historical database view;
generating version modification descriptions of each historical database view based on the modification content of the configuration information of each historical database view;
version information of each historical database view is updated based on the version modification description of each historical database view.
Specifically, the configuration information of the history database view before modification may be compared with the configuration information of the history database view after modification, so as to determine modification content corresponding to the configuration information. For example, modification content may include field modifications, parameter modifications, filter or hold logic modifications, and the like.
Database operation sentences (such as SQL sentences and the like) corresponding to the modification contents can be determined, and the configuration information of the associated historical database view corresponding to the historical database view is synchronously modified by using the database operation sentences. After the synchronous modification is completed, version modification description of each historical database view is generated according to the modification content of the configuration information of each historical database view, the version information of each historical database view is updated, and meanwhile, the version number and other information of the historical database view can be updated.
According to the database view configuration method, when configuration information of the historical database view is modified, the historical database view can be synchronously modified and the version record table can be updated, so that configuration and management of multiple versions of the database view are realized, and configuration efficiency of a user on the database view is improved.
In some embodiments, the version information includes at least one of version basic information, parameter configuration information, view reference information, view field information, and view operation information.
Specifically, the version information may be set according to user requirements, and may include version basic information, parameter configuration information, view reference information, view field information, and view operation information.
The version basic information refers to the view number, storage location, view name, version number, and the like of the history version. The parameter configuration information refers to information related to parameter configuration in the history version. View reference information refers to information such as data reference relationships among various historical versions. The view field information refers to fields defined in the database view, contents corresponding to the fields, and the like. View operation information refers to information such as various operations that a user can perform in a database view.
According to the database view configuration method, the version information can describe the related information of a plurality of historical versions corresponding to the current database view more comprehensively, and the user can check and configure the related information conveniently.
In some embodiments, the version base information includes at least one of a view number, a storage location, a view name, a version number, a creation time, a creation author, a version description, and a view baseline;
the parameter configuration information comprises at least one of a parameter field, a parameter name, a parameter type and a parameter default value;
the view reference information includes upstream view information and reference filter information;
the view field information includes at least one of a field dimension, a field number, a field name, a field type, a field size, a field source, a field definition, and a field operation;
The view operation information includes at least one of modification, import, save, visualization, run, and query.
In particular, the version basic information may include a view number, a storage location, a view name, a version number, a creation time, a creation author, a version description (version description), a view baseline, and the like. Where the view baseline is a snapshot or standard version of the database view at some point in time. It records the structure and definition of the database view and can be used to compare and restore changes to database objects.
The parameter configuration information includes a parameter field, a parameter name, a parameter type, and a parameter default value. The parameter field may be a custom field, or may be a field referencing an upstream view.
The view reference information includes upstream view information and reference filter information. The upstream view information may include, among other things, view aliases, reference types, source locations, association conditions and operations, etc. The reference filtering information refers to set filtering conditions for selectively filtering data.
View field information includes field dimensions, field numbers, field names, field types, field sizes, field sources, field definitions, and field operations. The view field information includes a field directly referring to an upstream view and also includes a custom field, and can show the content (dimension, number, name, type, length, source, definition, null, hierarchy, partition and operation) of the field, reserve condition logic, operation reason, annotation and the like, and suspend a mouse cursor on the field definition, so that detailed logic of the field definition can be checked.
View operation information includes modification, import, save, visualization, run, and query. Wherein, the operation refers to trial calculation of data in the view. For example, clicking the 'query' button jumps to the operation result interface, the trial calculation operation result record corresponding to the view history configuration version can be checked, and the view can be directly traced back and checked on the query interface.
In some embodiments, the associated history database view corresponding to the history database view is determined based on the steps of:
determining an upstream view corresponding to the historical database view;
determining a downstream view corresponding to the historical database view;
determining the upstream view and the downstream view as associated historical database views corresponding to the historical database views;
and associating the version number of the associated historical database view with the version number of the historical database view.
In particular, an upstream view and a downstream view of a database view refer to other views or tables associated with the database view.
An upstream view refers to a table or view that provides data to a current view. These upstream objects may be tables that are directly connected to the current view, or tables that are indirectly connected to the current view through other views. Upstream views are important for the correct function and data accuracy of the view.
Downstream views refer to other views or tables that depend on the current view. These downstream objects may use the data in the current view for further operations, data analysis, or presentation.
The upstream view and the downstream view can be determined as the associated historical database view corresponding to the historical database view, the version number of the associated historical database view is associated with the version number of the historical database view, and the associated historical database view can be conveniently queried through the associated version number.
In some embodiments, step 110 comprises:
establishing view links corresponding to a plurality of historical versions based on the association relation among the plurality of historical versions corresponding to the current database view;
based on the view links, multiple historical versions are visually presented.
Specifically, view links corresponding to a plurality of history versions may be established according to an association relationship between a plurality of history versions corresponding to a current database view. For example, each history version is taken as a node, and the association relationship between the history versions is taken as an edge, so that a view link is established.
And according to the established view link, the plurality of historical versions are visually displayed in the front-end page, so that a user can more intuitively view the plurality of historical versions corresponding to the current database view. The user can freely and flexibly switch back and forth in the visual interface, and directly select the target historical version, so that the processing efficiency and the working efficiency of the user on data are improved.
In some embodiments, the associations are upstream and downstream referencing relationships between the various historical versions.
Specifically, the association relationship may be an upstream-downstream reference relationship between the history versions. The reference relationship herein may be a data reference relationship.
Fig. 2 is a second flow chart of a method for configuring a database view, as shown in fig. 2, where the method is performed by a database view configuring device, and the database view configuring device may include a client, a server, and the like.
The client displays a front page, is used for realizing configuration of a front end view, displaying historical versions, tracing each historical version (including inquiry and modification), viewing views and the like.
The user configures descriptions, parameters, upstream references, fields, filters, reservation conditions, etc. of the view at the view configuration interface, the parameters and upstream references being direct choices of the existing corresponding view version. After the configuration is completed, clicking and storing are carried out, the configuration information can be inserted into each background configuration table, and version information is formed.
The user creates a new version record for each new or updated saving of the front end view configuration.
After the user modifies the view content, clicking the modification input modification reason and the user, clicking and saving a version record which can be newly added in the history, and clicking the history can view the basic information of all version records of the view configuration.
Multi-version traceback includes traceback queries and traceback modifications. Any record in the history version list is selected, clicking is performed to jump to a view configuration interface corresponding to the version, and information corresponding to any version of an upstream and downstream system used for viewing the view can be continuously traced, so that multi-version tracing of view configuration is realized, automatic association jumping is performed, jumping can be repeatedly performed, and layer-by-layer progressive or gyration is performed. And the new traceability link can be formed by updating and storing at any view interface at any time, so that traceability modification is realized.
The user can look at details by jumping to the corresponding front end view interface for multi-version retrospective queries.
The server executes background logic, which includes generating corresponding sentences according to the views, inserting configuration content into a plurality of configuration tables (views), saving version records and association relations, inquiring the configuration tables of the associated views through association fields, associating upstream and downstream records through the association fields, modifying and saving a traceable link into which new records and new versions of the records are inserted, and the like.
The method can realize the following functions:
(1) Implementing multi-version record presentation
And each history version record of the configured view is stored below the front page, the history version record can be displayed by clicking a history button, and the current version is blackened, thickened and prominently displayed, so that the view and the subsequent update are convenient to use. A complete view configuration version management background framework can be built, and a series of view configuration tables are built in a database. And each time the configuration of the view is saved, all the modified configuration contents are inserted into one or more corresponding configuration tables through the generated statement, the information such as the version number of the view configuration is automatically generated and saved, and the version management record table is inserted for traceability.
(2) Implementing skip-view of view configuration history version
And selecting one version number in the history version list, and clicking to jump to a view configuration detail interface corresponding to the version number. When view configuration details corresponding to the version are required to be checked, the view configuration corresponding to the version is accurately inquired through the association of the version number, and the view configuration interface is jumped to, and the detailed contents of the view corresponding to the version number are quoted and displayed, wherein the detailed contents comprise all contents such as fields, parameters, a quotation table or views, screening conditions, reserved logic and the like.
(3) Implementing retrospective viewing of view configuration history versions
In the detailed configuration interface of the view of the jump to version, all contents of the view and other configuration or operation record results of the upstream and downstream links can be checked, including basic information, parameter configuration, upstream references, view fields, view operations and the like. When the parameter configuration is checked, basic information, history version, real parameters, associated views and the like of the parameter view can be checked, and the corresponding information interface can be further checked in a jumping manner.
A series of view configuration tables can be established in the database, configuration details and association relations of views are reserved layer by layer, versions are formed for each operation, the details are recorded in the sub-tables, the whole view configuration links are hooked into a plurality of configuration links through association fields, the configuration links are buckled in a ring, and the configuration tables are similar to a complex route diagram, and the multi-version tracing of the view configuration is realized through the upstream and downstream relation of each link.
(4) Implementing updates to view configuration history versions
The view configuration interface is used for jumping to the selected version through the view configuration history version, so that the view configuration of the version can be modified, the modification can be saved to generate a new view version, and meanwhile, the new version can be checked and traced.
A series of configuration tables may be built up in the database. The tracing of the multiple versions of the video configuration is realized by carrying out association inquiry on key fields (such as version numbers), so that each time one view or parameter is saved, all the configured contents are inserted into one or more corresponding configuration tables through generated sentences, and a new association relation table is required to be saved. If the contents are to be traced and inquired, the related inquiry such as version number and the like can be completed.
According to the database view configuration method, dynamic modes are adopted for multi-version management of the database view, each version record can be dynamically linked to the corresponding view configuration and is progressive layer by layer, and the defect of static version management scattered fault is overcome; only the basic version information is recorded and displayed on the current page, and flexible jump can be realized when the user needs to check details, so that redundancy of information storage is avoided; each view configuration version record can be traced, details of the whole operation link can be traced and checked, the service parameters and the operation parameter versions of the view configuration can be included, trial calculation version result details can be checked, meanwhile, related view configuration can be directly modified and adjusted to form a new version record, the back and forth manual switching check is not needed, the system can be directly related to the configuration of each environment, manual identification is not needed by a user, a large amount of time is saved, and the efficiency is greatly improved.
The apparatus provided in the embodiments of the present application will be described below, and the apparatus described below and the method described above may be referred to correspondingly.
Fig. 3 is a schematic structural diagram of a database view configuration device provided in the present application, as shown in fig. 3, where the device includes:
a display unit 310 for receiving a first input of a user; responding to the first input, and displaying a version record table corresponding to the current database view; the version record table comprises version information of a plurality of historical versions corresponding to the current database view;
a selection unit 320 for receiving a second input of the user; responding to the second input, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version;
a configuration unit 330 for receiving a third input of the user; and responding to the third input, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table.
The database view configuration device provided by the embodiment of the application responds to the first input of the user and displays a version record table corresponding to the current database view; responding to a second input of the user, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version; responding to a third input of a user, modifying configuration information of the historical database view, synchronizing modification content corresponding to the configuration information to an associated historical database view corresponding to the historical database view, and updating version information of each historical database view in a version record table; the historical versions of the database view are summarized and managed uniformly through the version record table, any historical version can be selected for viewing according to the input of a user, when the configuration information of the historical database view is modified, the associated historical database view can be modified synchronously, and the version record table is updated, so that the configuration and management of multiple versions of the database view are realized, the requirements of actual application scenes can be met, the maintainability, flexibility and traceability of view configuration are improved, and the processing efficiency and the working efficiency of the user on data are improved.
In some embodiments, the configuration unit is to:
comparing the configuration information of the history database view before modification with the configuration information of the history database view after modification, and determining modification content corresponding to the configuration information;
determining database operation sentences corresponding to the modified content;
based on the database operation sentences, synchronously modifying the configuration information of the associated historical database view corresponding to the historical database view;
generating version modification descriptions of each historical database view based on the modification content of the configuration information of each historical database view;
version information of each historical database view is updated based on the version modification description of each historical database view.
In some embodiments, the version information includes at least one of version basic information, parameter configuration information, view reference information, view field information, and view operation information.
In some embodiments, the version base information includes at least one of a view number, a storage location, a view name, a version number, a creation time, a creation author, a version description, and a view baseline;
the parameter configuration information comprises at least one of a parameter field, a parameter name, a parameter type and a parameter default value;
The view reference information includes upstream view information and reference filter information;
the view field information includes at least one of a field dimension, a field number, a field name, a field type, a field size, a field source, a field definition, and a field operation;
the view operation information includes at least one of modification, import, save, visualization, run, and query.
In some embodiments, the configuration unit is to:
determining an upstream view corresponding to the historical database view;
determining a downstream view corresponding to the historical database view;
determining the upstream view and the downstream view as associated historical database views corresponding to the historical database views;
and associating the version number of the associated historical database view with the version number of the historical database view.
In some embodiments, the display unit is to:
establishing view links corresponding to a plurality of historical versions based on the association relation among the plurality of historical versions corresponding to the current database view;
based on the view links, multiple historical versions are visually presented.
In some embodiments, the associations are upstream and downstream referencing relationships between the various historical versions.
Fig. 4 is a schematic structural diagram of an electronic device provided in the present application, and as shown in fig. 4, the electronic device may include: processor (Processor) 410, communication interface (Communications Interface) 420, memory (Memory) 430, and communication bus (Communications Bus) 440, wherein Processor 410, communication interface 420, and Memory 430 complete communication with each other via communication bus 440. The processor 410 may invoke logic commands in the memory 430 to perform the following method:
Receiving a first input of a user; responding to the first input, and displaying a version record table corresponding to the current database view; the version record table comprises version information of a plurality of historical versions corresponding to the current database view; receiving a second input from the user; responding to the second input, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version; receiving a third input from the user; and responding to the third input, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table.
In addition, the logic commands in the memory described above may be implemented in the form of software functional units and may be stored in a computer readable storage medium when sold or used as a stand alone product. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several commands for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The processor in the electronic device provided by the embodiment of the present application may call the logic instruction in the memory to implement the above method, and the specific implementation manner of the processor is consistent with the implementation manner of the foregoing method, and may achieve the same beneficial effects, which are not described herein again.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, is implemented to perform the methods provided by the above embodiments.
The specific embodiment is consistent with the foregoing method embodiment, and the same beneficial effects can be achieved, and will not be described herein.
Embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements a method as described above.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.
Claims (10)
1. A method for configuring a database view, comprising:
receiving a first input of a user;
responding to the first input, and displaying a version record table corresponding to the current database view; the version record table comprises version information of a plurality of historical versions corresponding to the current database view;
receiving a second input from the user;
responding to the second input, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version;
receiving a third input from the user;
and responding to the third input, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table.
2. The method according to claim 1, wherein modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table, includes:
Comparing the configuration information of the historical database view before modification with the configuration information of the historical database view after modification, and determining modification content corresponding to the configuration information;
determining database operation sentences corresponding to the modified contents;
based on the database operation statement, synchronously modifying configuration information of the associated historical database view corresponding to the historical database view;
generating version modification descriptions of each historical database view based on the modification content of the configuration information of each historical database view;
version information of each historical database view is updated based on the version modification description of each historical database view.
3. The database view configuration method according to claim 1, wherein the version information includes at least one of version basic information, parameter configuration information, view reference information, view field information, and view operation information.
4. The database view configuration method according to claim 3, wherein the version basic information includes at least one of view number, storage location, view name, version number, creation time, creation author, version description, and view baseline;
The parameter configuration information comprises at least one of a parameter field, a parameter name, a parameter type and a parameter default value;
the view reference information comprises upstream view information and reference filtering information;
the view field information includes at least one of a field dimension, a field number, a field name, a field type, a field size, a field source, a field definition, and a field operation;
the view operation information includes at least one of modification, import, save, visualization, run, and query.
5. The database view configuration method according to claim 1, wherein the associated history database view corresponding to the history database view is determined based on the steps of:
determining an upstream view corresponding to the historical database view;
determining a downstream view corresponding to the historical database view;
determining the upstream view and the downstream view as associated historical database views corresponding to the historical database views;
and associating the version number of the associated historical database view with the version number of the historical database view.
6. The method for configuring a database view according to claim 1, wherein displaying the version record table corresponding to the current database view comprises:
Establishing view links corresponding to a plurality of historical versions based on the association relation among the historical versions corresponding to the current database view;
and visually displaying the historical versions based on the view link.
7. The method of claim 6, wherein the association is an upstream-downstream reference between historical versions.
8. A database view configuration apparatus, comprising:
a display unit for receiving a first input of a user; responding to the first input, and displaying a version record table corresponding to the current database view; the version record table comprises version information of a plurality of historical versions corresponding to the current database view;
a selection unit for receiving a second input of a user; responding to the second input, determining a target history version in the version record table, and displaying a history database view corresponding to the target history version;
a configuration unit for receiving a third input of a user; and responding to the third input, modifying the configuration information of the historical database view, synchronizing the modification content corresponding to the configuration information to the associated historical database view corresponding to the historical database view, and updating the version information of each historical database view in the version record table.
9. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the database view configuration method according to any of claims 1 to 7 by means of the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a stored program, wherein the program when run performs the database view configuration method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311599209.XA CN117632958A (en) | 2023-11-27 | 2023-11-27 | Database view configuration method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311599209.XA CN117632958A (en) | 2023-11-27 | 2023-11-27 | Database view configuration method, device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117632958A true CN117632958A (en) | 2024-03-01 |
Family
ID=90033254
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311599209.XA Pending CN117632958A (en) | 2023-11-27 | 2023-11-27 | Database view configuration method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117632958A (en) |
-
2023
- 2023-11-27 CN CN202311599209.XA patent/CN117632958A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111177231B (en) | Report generation method and report generation device | |
| CN110928772B (en) | Test method and device | |
| US7979267B2 (en) | Specifying a subset of dynamic inter-related data | |
| US9183561B2 (en) | Automatic generation of trend charts | |
| US9021440B1 (en) | System and method for automated test script generation | |
| US8671084B2 (en) | Updating a data warehouse schema based on changes in an observation model | |
| EP3472766A1 (en) | Workflow visualization platform | |
| US20110209042A1 (en) | Information Technology Standard Inventory Utility | |
| US20070162273A1 (en) | Natural language tool for specifying a subset of dynamic inter-related data | |
| CN109376153B (en) | System and method for writing data into graph database based on NiFi | |
| CN104679500B (en) | Method and device for realizing automatic generation of entity class | |
| CN113191139A (en) | Data blood margin analysis method and device based on column-level data | |
| CN112560422A (en) | Chart processing method, device, equipment and medium | |
| CN115576974A (en) | Data processing method, device, equipment and medium | |
| US20100070893A1 (en) | Data quality administration framework | |
| CN109033157B (en) | Complex data retrieval method and system based on user-defined search condition tree | |
| CN111984882A (en) | Data processing method, system and equipment | |
| CN113010208A (en) | Version information generation method, version information generation device, version information generation equipment and storage medium | |
| CN117632958A (en) | Database view configuration method, device, electronic equipment and storage medium | |
| CN114936152A (en) | Application testing method and device | |
| CN115469849A (en) | Service processing system, method, electronic device and storage medium | |
| CN114003329A (en) | Data display component creating method and device, storage medium and electronic device | |
| US10198150B2 (en) | Cross database data selection and correlation interface | |
| CN116136880A (en) | Data display method and device, electronic equipment and storage medium | |
| CN109977104B (en) | Data management method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |