CN115422167B - Cross-data source database view visualization construction method and system - Google Patents
Cross-data source database view visualization construction method and system Download PDFInfo
- Publication number
- CN115422167B CN115422167B CN202211178918.6A CN202211178918A CN115422167B CN 115422167 B CN115422167 B CN 115422167B CN 202211178918 A CN202211178918 A CN 202211178918A CN 115422167 B CN115422167 B CN 115422167B
- Authority
- CN
- China
- Prior art keywords
- view
- sql
- database
- condition
- list
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/285—Clustering or classification
- G06F16/287—Visualization; Browsing
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a cross-database source database view visualization construction method and a system, wherein the method comprises the following steps: specifically configuring view information in a visual mode to obtain view configuration information; analyzing the view configuration information to obtain view basic information and SQL query statement information; analyzing each SQL query description unit and converting the SQL query description unit into an SQL fragment; splicing the obtained sql fragments to obtain a complete query sql statement; and executing an instruction for creating a view by adopting a complete query sql statement on a corresponding data source, and creating to obtain a database view consistent with the user configuration. The method can reduce the requirements of the database technology in the process of creating the database view, set each parameter of the view in a visual mode, and finally generate the database view according to the parameters, so that the problems of complicated writing process of the original sql statement and high professional requirements can be avoided, and the view creation is simpler.
Description
Technical Field
The invention belongs to the technical field of computer databases, and particularly relates to a cross-data source database view visualization construction method and system.
Background
The traditional method for creating database views is as follows: firstly, inquiring a database, acquiring metadata information, positioning to a required database table, determining associated fields, screening condition information and the like; secondly, compiling the query requirement on the database table into a structured query language sql statement; and finally, creating a database view according to the written sql statement.
Therefore, the traditional database view creating method needs a user to clearly know metadata information and has professional knowledge of inquiring the positioning metadata of the underlying database; the use technology of the database needs to be mastered, and the technical knowledge for writing sql statements is provided. Therefore, the technical threshold of creating the database view is high, and users without related professional knowledge cannot create the database view.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a cross-database source database view visualization construction method and a cross-database source database view visualization construction system, which can effectively solve the problems.
The technical scheme adopted by the invention is as follows:
the invention provides a cross-data source database view visualization construction method, which comprises the following steps:
step 1, specifically configuring view information in a visual mode on a front-end visual interface to obtain view configuration information;
step 2, analyzing the view configuration information to obtain view basic information and SQL query statement information; the SQL query statement information comprises a plurality of SQL query description units;
step 3, checking the view basic information and the SQL query statement information obtained by analysis, and if the check fails, failing to establish the database view; if the verification is passed, executing the step 4;
step 4, further analyzing each SQL query description unit to obtain the field of each SQL query description unit;
step 5, converting the field of each SQL query description unit into an SQL fragment;
step 6, checking whether each sql fragment meets the requirement, and if not, failing to create the database view; if the requirement is met, executing the step 7;
step 7, splicing the obtained sql fragments to obtain a complete query sql statement;
and 8, executing an instruction for creating a view by adopting a complete query sql statement on a corresponding data source, and creating to obtain a database view consistent with the user configuration.
Preferably, the view basic information includes: view name, data source type and data source name;
the SQL query description unit is as follows: a view element list, a view element relationship list, a sub-query list, a where screening condition list, a having screening condition list, and other condition lists.
Preferably, the view element list includes a plurality of view elements, each view element has three fields, which are: aggregate function name, table name, and column name;
the view element relationship list comprises a plurality of view element relationships, each view element relationship has five fields, which are respectively: the method comprises the following steps of associating types, left associating element ids, right associating element ids, left associating element columns and right associating element columns;
the where screening condition list comprises a plurality of where screening conditions, and each of the where screening conditions comprises the following fields: the left correlation element id, the right correlation element id, the left correlation element column, the right correlation element column, the condition numerical value, the condition symbol and the condition;
the viewing screening condition list comprises a plurality of viewing screening conditions, and each viewing screening condition comprises the following fields: left association element id, right association element id, left association element column, right association element column, condition value, condition symbol, and relationship between conditions.
Preferably, the checking of the view basic information and the SQL query statement information obtained by the parsing includes:
performing value type checking on the view name, the data source type, the data source name and the view element list, judging whether the view name, the data source type, the data source name and the view element list are empty, if so, checking is not passed, and creating the database view fails; if not, the check passes.
Preferably, each SQL query description unit is further analyzed to obtain a field of each SQL query description unit, which specifically includes:
further analyzing the view elements configured by the user in the view element list to obtain view element fields including aggregation function names, table names and column names;
further analyzing the view element relationship configured by the user in the view element relationship list to obtain a view element relationship field, wherein the view element relationship field comprises an association type, a left association element id, a right association element id, a left association element column and a right association element column;
further analyzing the user-configured where screening condition in the where screening condition list to obtain where screening condition fields including the left association element id, the right association element id, the left association element column, the right association element column, the condition value, the condition symbol and the relationship between the conditions;
further analyzing the having screening conditions configured by the user in the having screening condition list to obtain a having screening condition field, wherein the having screening condition field comprises a left associated element id, a right associated element id, a left associated element column, a right associated element column, a condition numerical value, a condition symbol and a condition relation;
and further analyzing the relevant conditions configured by the user in the other condition lists to obtain relevant condition fields.
Preferably, the method further comprises the following steps: and further checking each SQL query description unit:
1) Checking a table corresponding to the table name in the view element list and whether a column corresponding to the column name actually exists in the database;
2) Checking whether each associated element in the view element relation list really exists in the database or not;
3) Checking whether each associated element in the where screening condition list and the having screening condition list really exists in the database or not;
if the check fails, the database view creation fails.
Preferably, the other condition list includes whether to group the identifier, the page size, and the number of page starts.
Preferably, checking whether each sql fragment meets the requirement specifically comprises:
and checking whether each sql fragment conforms to the sql rule.
The invention also provides a system of a cross-data source database view visualization construction method, which comprises the following steps:
the front-end visual interface is used for carrying out specific configuration on the view information in a visual mode to obtain view configuration information;
the first analysis module is used for analyzing the view configuration information configured on the front-end visual interface to obtain view basic information and SQL query statement information; the SQL query statement information comprises a plurality of SQL query description units;
the first checking module is used for checking the view basic information and the SQL query statement information which are analyzed by the first analyzing module, and if the checking fails, the database view is failed to be established;
the second analysis module is used for further analyzing each SQL query description unit verified by the first verification module to obtain a field of each SQL query description unit;
the SQL fragment generation module is used for converting the field of each SQL query description unit obtained by the analysis of the second analysis module into an SQL fragment;
the second checking module is used for checking whether each sql fragment generated by the sql fragment generating module meets the requirement or not, and if not, the database view is failed to be established;
the splicing module is used for splicing the sql fragments verified by the second verification module to obtain a complete query sql statement;
and the database view generating module is used for executing an instruction for creating a view by adopting a complete query sql statement on a corresponding data source to create and obtain a database view consistent with the user configuration.
The cross-data source database view visualization construction method and system provided by the invention have the following advantages:
the cross-data source database view visualization construction method and system can reduce the requirements of database technology in the database view creation process, set each parameter of the view in a visualization mode, and finally generate the database view according to the parameters. The problems that the writing process of the original sql statement is complicated and the requirement on the specialty is high can be avoided, and the view creation is simpler.
Drawings
Fig. 1 is a flowchart of a cross-database view visualization construction method provided by the present invention;
fig. 2 is a composition diagram of view basic information provided by the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantageous effects solved by the present invention more clearly apparent, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The invention provides a method and a system for visually constructing a cross-data source database view, wherein a database view is constructed by adopting a visualization technology, abstract data and information are converted into visual objects by the visualization technology, and the core of the method is to provide a visual and interactive visualization environment for spatial information for a user. In the construction process of the database view, the application of the visualization technology provides a front-end visualization interface, metadata information such as tables, columns and the like in the database is displayed to a user in a graph form, the user can perform association between the database table and the fields through the graph interface, screening conditions and the like are set, and the operation is simple; compared with the method of directly contacting the data of the bottom database, the method is more intuitive, is convenient for users to understand, and reduces the technical threshold of creating the database view.
The invention provides a cross-data source database view visualization construction method, which mainly comprises the following steps:
abstracting the sql statement into an abstract intermediate data structure, and setting various parameters of the abstract intermediate data structure through a front-end visual interface to form front-end parameters; and then, automatically generating an sql query statement by the front-end parameters, and then creating a database view on the bottom-layer data source by adopting the sql query statement.
The visual database view construction method can reduce the requirements of database technology in the database view construction process, set each parameter of the view in a visual mode, and finally generate the database view according to the parameters. The problems that the writing process of the native sql statement is complicated and the requirement on the specialty is high can be avoided, and the view creation is simpler.
Referring to fig. 1, the present invention provides a cross-database source view visualization construction method, including the following steps:
step 1, specifically configuring view information in a visual mode on a front-end visual interface to obtain view configuration information;
step 2, analyzing the view configuration information to obtain view basic information and SQL query statement information; the SQL query statement information comprises a plurality of SQL query description units;
step 3, checking the view basic information and the SQL query statement information obtained by analysis, and if the check is not passed, the database view is failed to be established; if the verification is passed, executing the step 4;
step 4, further analyzing each SQL query description unit to obtain the field of each SQL query description unit;
step 5, converting the field of each SQL query description unit into an SQL fragment;
step 6, checking whether each sql fragment meets the requirement, and if not, failing to create the database view; if the requirements are met, executing the step 7;
step 7, splicing the obtained sql fragments to obtain a complete query sql statement;
and 8, executing an instruction for creating a view by adopting a complete query sql statement on a corresponding data source, and creating to obtain a database view consistent with the user configuration.
To facilitate an understanding of the invention, a specific embodiment is described below:
step 1, carrying out specific configuration on view information in a front-end visual interface in a visual mode to obtain view configuration information;
specifically, the front-end visual interface is used for configuring view information; the view information comprises view basic information and SQL query statement information;
the view basic information includes: view name, data source type and data source name;
the SQL query statement information comprises six categories which are respectively: a view element list, a view element relationship list, a sub-query list, a where screening condition list, a haiving screening condition list and other condition lists;
wherein:
the view element list comprises a plurality of view elements, each view element has three fields, which are respectively: aggregate function name, table name, and column name;
the view element relationship list comprises a plurality of view element relationships, each view element relationship has five fields, which are respectively: the association type, the left association element id, the right association element id, the left association element column and the right association element column;
the where screening condition list comprises a plurality of where screening conditions, and each of the where screening conditions comprises the following fields: the left association element id, the right association element id, the left association element column, the right association element column, the condition numerical value, the condition symbol and the condition;
the list of haiving screening conditions comprises a plurality of haiving screening conditions, and each haiving screening condition comprises the following fields: the left association element id, the right association element id, the left association element column, the right association element column, the condition numerical value, the condition symbol and the condition;
other condition lists include whether a packet identification, page size, and number of page start bars.
In the invention, the front-end visual interface is obtained in the following mode: the composition of the standard SQL query statement is abstracted to obtain an abstract intermediate data structure, and then the abstract intermediate data structure is visualized to form a front-end visual interface. An abstract intermediate data structure comprising view base information and SQL query statement information; the view basic information includes: view name, data source type and data source name; the SQL query statement information includes six categories, which are: view element lists, view element relationship lists, sub-query lists, where filter condition lists, haiving filter condition lists, and other condition lists.
The concrete abstraction and construction process is exemplified as follows:
for example, for the Sql sample: select max (a.id), b.name from repo.dept a Inner join repo.staf b.id = b.dept _ id WHERE a.id <2group by b.name has a.id > 10,3. Standard SQL is denoted as select [ ITEMS ] from [ ITEM _ RELATONS ] [ WHERE _ CLAUSE ] [ HAING _ CLAUSE ] [ OTJLIMITIONS ], WHERE the section contained in brackets [ ] is a section of data structure abstraction, and each section corresponds to a SQL segment and the fields in the abstract data structure are as follows:
it should be emphasized that the view basic information described above includes: view name, data source type and data source name; the SQL query statement information includes six categories, which are: a view element list, a view element relationship list, a sub-query list, a where screening condition list, a haiving screening condition list and other condition lists; the present invention is not limited to specific parameters included in the view basic information and the SQL query statement information, and the specific parameters are flexibly set according to requirements.
On a front-end visual interface, a user performs specific configuration on the view information to obtain view configuration information; the view configuration information is front-end data;
step 2, an analysis module can be adopted to analyze the view configuration information to obtain the view basic information and the SQL query statement information; the SQL query statement information comprises a plurality of SQL query description units;
the specific analysis mode is as follows:
analyzing the view basic information to obtain a view name, a data source type and a data source name; analyzing the SQL query statement information to obtain a view element list, a view element relation list, a sub-query list, a where screening condition list, a haiving screening condition list and other condition lists;
step 3, checking the view basic information and the SQL query statement information obtained by analysis, and if the check fails, failing to establish the database view; if the verification is passed, executing the step 4;
specifically, performing value type basic check on the view name, the data source type, the data source name and the view element list, and judging whether the view name, the data source type, the data source name and the view element list are empty, if so, the check is not passed, and the database view is failed to be created; if not, the basic check is passed, and the following steps are executed;
in this step, the following check may be further performed:
1) Checking whether a table corresponding to the table name in the view element list and column columns corresponding to the column name actually exist in the database or not; if the alias field exists, whether the alias numbers are consistent with the column name numbers or not needs to be checked;
2) Checking whether each associated element in the view element relation list really exists in the database or not; if not, the verification is not passed;
3) And checking whether each associated element in the where screening condition list and the haiving screening condition list really exists in the database. If not, the verification is not passed;
if all the three verification conditions pass, the verification passes.
Step 4 and step 5, further analyzing each SQL query description unit to obtain the field of each SQL query description unit; converting the field of each SQL query description unit into an SQL fragment;
the concrete mode is as follows:
further analyzing the view elements configured by the user in the view element list to obtain view element fields including aggregation function names, table names and column names; converting the analyzed view element field into a 1sql fragment;
further analyzing the view element relationship configured by the user in the view element relationship list to obtain a view element relationship field, wherein the view element relationship field comprises an association type, a left association element id, a right association element id, a left association element column and a right association element column; converting the analyzed view element relation field into a 2sql fragment;
further analyzing the user-configured where screening condition in the where screening condition list to obtain a where screening condition field including a left associated element id, a right associated element id, a left associated element column, a right associated element column, a condition value, a condition symbol and a relationship between conditions; converting the analyzed where screening condition field into a 3sql fragment;
further analyzing the having screening conditions configured by the user in the having screening condition list to obtain a having screening condition field, wherein the having screening condition field comprises a left associated element id, a right associated element id, a left associated element column, a right associated element column, a condition numerical value, a condition symbol and a condition relation; converting the analyzed having screening condition field into a 4sql fragment;
further analyzing the relevant conditions configured by the user in the other condition lists to obtain relevant condition fields; converting the analyzed related condition field into a 5sql fragment;
for example, the front-end parameter names, the front-end parameter values, and the parsed sql fragments may be as shown in the following table: the front-end parameter value is a value configured by a user; the front-end parameter names are parameters displayed on the front-end visual interface:
for analyzing whether grouping is performed or not, when the paging condition is satisfied, the corresponding relationship is as follows:
step 6, checking whether each sql fragment meets the requirement, and if not, failing to create the database view; if the requirements are met, executing the step 7;
specifically, judging whether the 1 st sql fragment, the 2 nd sql fragment, the 3 rd sql fragment, the 4 th sql fragment and the 5 th sql fragment obtained by analysis all accord with an sql rule, and if not, returning a notification of failure in creating the database view; if the view configuration information is consistent with the sub-query, whether the sub-query configured by the user exists in the view configuration information can be further judged, and if not, the step 7 is executed; and if so, returning to the step 2, analyzing information such as a view element list, an element relation list and the like of the internal sub-queries, and analyzing each sub-query into a plurality of sql fragments until all sub-queries are analyzed.
Step 7, splicing the obtained sql fragments to obtain a complete query sql statement;
and 8, executing an instruction for creating a view by adopting a complete query sql statement on a corresponding data source, and creating to obtain a database view consistent with the user configuration.
For example, the partial SQL statements obtained in the above steps are concatenated to obtain a complete query SQL statement SELECT _ SQL = "SELECT max (a.id), b.name from repo.depth a Inner join repo.staf b.id = b.depth _ id where a.id <2group b.name will a.id <10limit 10,3", and a "create view/table as (SELECT _ SQL)" is executed on the underlying data source, and the whole process is ended.
As a specific example, the abstract intermediate data structure:
corresponding to the generated sql statement:
select a.id,b.role_name,c.username from router.router_user a inner join router.router_user_role b on a.username＝b.username left join(select a.id,a.username,b.role_name from router.router_user a inner join router.router_user_role b on a.username＝b.username)c on b.username＝c.username where a.id<9and a.id＝b.id
according to the method and the system for constructing the cross-data source database view visualization, the sql statement is abstracted into an abstract intermediate data structure and is displayed through a front-end visualization interface; a user flexibly configures various view parameters on a front-end visual interface, including: field selection, aggregation function addition, screening condition addition, sub-query and the like, so as to obtain front-end parameters; the front-end parameters can be automatically parsed into sql statements and finally database views are generated. Therefore, the problems that the writing process of the native sql statement is complicated and the requirement on the specialty is high can be avoided, and the view creation is simpler.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements should also be considered within the scope of the present invention.
Claims (9)
1. A cross-data source database view visualization construction method is characterized by comprising the following steps:
step 1, carrying out specific configuration on view information in a front-end visual interface in a visual mode to obtain view configuration information;
step 2, analyzing the view configuration information to obtain view basic information and SQL query statement information; the SQL query statement information comprises a plurality of SQL query description units;
step 3, checking the view basic information and the SQL query statement information obtained by analysis, and if the check is not passed, the database view is failed to be established; if the verification is passed, executing the step 4;
step 4, further analyzing each SQL query description unit to obtain the field of each SQL query description unit;
step 5, converting the field of each SQL query description unit into an SQL fragment;
step 6, checking whether each sql fragment meets the requirement, and if not, failing to create the database view; if the requirement is met, executing the step 7;
step 7, splicing the obtained sql fragments to obtain a complete query sql statement;
and 8, executing a command for creating a view by adopting a complete query sql statement on a corresponding data source, and creating to obtain a database view consistent with the user configuration.
2. The method for visually constructing a cross-database data view according to claim 1, wherein the view basic information includes: view name, data source type and data source name;
the SQL query description unit is as follows: a view element list, a view element relationship list, a sub-query list, a where screening condition list, a having screening condition list, and other condition lists.
3. The method for building the visualization of the source database crossing according to claim 2, wherein the view element list comprises a plurality of view elements, each view element has three fields, which are respectively: aggregate function name, table name, and column name;
the view element relationship list comprises a plurality of view element relationships, each view element relationship has five fields, which are respectively: the method comprises the following steps of associating types, left associating element ids, right associating element ids, left associating element columns and right associating element columns;
the where screening condition list comprises a plurality of where screening conditions, and each of the where screening conditions comprises the following fields: the left association element id, the right association element id, the left association element column, the right association element column, the condition numerical value, the condition symbol and the condition;
the viewing screening condition list comprises a plurality of viewing screening conditions, and each viewing screening condition comprises the following fields: left association element id, right association element id, left association element column, right association element column, condition value, condition symbol, and relationship between conditions.
4. The cross-data source database view visualization construction method according to claim 3, wherein the view basic information and the SQL query statement information obtained by parsing are verified, specifically:
performing value type checking on the view name, the data source type, the data source name and the view element list, judging whether the view name, the data source type, the data source name and the view element list are empty, if so, the checking is not passed, and the database view is failed to be created; if not, the check passes.
5. The visualization construction method for a cross-database source database view according to claim 3, characterized in that, each SQL query description unit is further analyzed to obtain the fields of each SQL query description unit, specifically:
further analyzing the view elements configured by the user in the view element list to obtain view element fields including aggregation function names, table names and column names;
further analyzing the view element relationship configured by the user in the view element relationship list to obtain a view element relationship field, wherein the view element relationship field comprises an association type, a left association element id, a right association element id, a left association element column and a right association element column;
further analyzing the user-configured where screening condition in the where screening condition list to obtain where screening condition fields including the left association element id, the right association element id, the left association element column, the right association element column, the condition value, the condition symbol and the relationship between the conditions;
further analyzing the having screening conditions configured by the user in the having screening condition list to obtain a having screening condition field, wherein the having screening condition field comprises a left associated element id, a right associated element id, a left associated element column, a right associated element column, a condition numerical value, a condition symbol and a condition relation;
and further analyzing the relevant conditions configured by the user in the other condition lists to obtain relevant condition fields.
6. The cross-database source view visualization construction method according to claim 5, further comprising: and further checking each SQL query description unit:
1) Checking a table corresponding to the table name in the view element list and whether a column corresponding to the column name actually exists in a database;
2) Checking whether each associated element in the view element relation list really exists in the database or not;
3) Checking whether each associated element in the where screening condition list and the having screening condition list really exists in the database or not;
if the check fails, the database view creation fails.
7. The method for visually constructing a cross-database view according to claim 2, wherein the other condition list includes whether to group identifier, page size and page starting number.
8. The visualization construction method for a cross-database source view according to claim 1, wherein the step of checking whether each sql fragment meets requirements specifically comprises:
and checking whether each sql fragment conforms to an sql rule.
9. The system for building a visualization of a source database view across data sources according to any one of claims 1-8, comprising:
the front-end visual interface is used for specifically configuring the view information in a visual mode to obtain view configuration information;
the first analysis module is used for analyzing the view configuration information configured on the front-end visual interface to obtain view basic information and SQL query statement information; the SQL query statement information comprises a plurality of SQL query description units;
the first checking module is used for checking the view basic information and the SQL query statement information which are analyzed by the first analyzing module, and if the checking fails, the database view is failed to be established;
the second analysis module is used for further analyzing each SQL query description unit verified by the first verification module to obtain a field of each SQL query description unit;
the SQL fragment generation module is used for converting the field of each SQL query description unit obtained by the analysis of the second analysis module into an SQL fragment;
the second checking module is used for checking whether each sql fragment generated by the sql fragment generating module meets the requirement or not, and if not, the database view is failed to be established;
the splicing module is used for splicing the sql fragments verified by the second verification module to obtain a complete query sql statement;
and the database view generating module is used for executing an instruction for creating a view by adopting a complete query sql statement on a corresponding data source to create and obtain a database view consistent with the user configuration.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211178918.6A CN115422167B (en) | 2022-09-27 | 2022-09-27 | Cross-data source database view visualization construction method and system |
| PCT/CN2022/142004 WO2024066094A1 (en) | 2022-09-27 | 2022-12-26 | Cross-data-source visual construction method and system for database view |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211178918.6A CN115422167B (en) | 2022-09-27 | 2022-09-27 | Cross-data source database view visualization construction method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115422167A CN115422167A (en) | 2022-12-02 |
| CN115422167B true CN115422167B (en) | 2023-02-17 |
Family
ID=84205639
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211178918.6A Active CN115422167B (en) | 2022-09-27 | 2022-09-27 | Cross-data source database view visualization construction method and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115422167B (en) |
| WO (1) | WO2024066094A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115422167B (en) * | 2022-09-27 | 2023-02-17 | 北京柏睿数据技术股份有限公司 | Cross-data source database view visualization construction method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103093000A (en) * | 2013-02-25 | 2013-05-08 | 用友软件股份有限公司 | Database query modeling system and database query modeling method |
| CN111126026A (en) * | 2019-12-17 | 2020-05-08 | 叮当快药科技集团有限公司 | Method and tool for generating visual report form by analyzing SQL statement |
| CN113326314A (en) * | 2021-06-30 | 2021-08-31 | 招商局金融科技有限公司 | Data visualization method and device, electronic equipment and readable storage medium |
| CN113641700A (en) * | 2021-08-30 | 2021-11-12 | 北京沃东天骏信息技术有限公司 | Data processing method and device based on Spring boot frame |
| CN113901135A (en) * | 2021-09-14 | 2022-01-07 | 威讯柏睿数据科技(北京)有限公司 | Cross-source heterogeneous data intelligent visual analysis display method and equipment |
| CN114218336A (en) * | 2021-12-17 | 2022-03-22 | 中国建设银行股份有限公司 | Data warehouse visual chart display method, device and equipment |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8214379B2 (en) * | 2010-01-29 | 2012-07-03 | Microsoft Corporation | Composing views with automatic creation of links |
| US11966568B2 (en) * | 2018-10-22 | 2024-04-23 | Tableau Software, Inc. | Generating data visualizations according to an object model of selected data sources |
| CN111241123A (en) * | 2020-01-07 | 2020-06-05 | 深圳市华宇讯科技有限公司 | View data query method, device, server and storage medium |
| CN111813799B (en) * | 2020-07-23 | 2024-01-19 | 德清云岫科技有限公司 | Database query statement generation method, device, computer equipment and storage medium |
| CN113901083B (en) * | 2021-09-14 | 2023-05-12 | 北京柏睿数据技术股份有限公司 | Heterogeneous data source operation resource analysis positioning method and equipment based on multiple resolvers |
| CN115422167B (en) * | 2022-09-27 | 2023-02-17 | 北京柏睿数据技术股份有限公司 | Cross-data source database view visualization construction method and system |
-
2022
- 2022-09-27 CN CN202211178918.6A patent/CN115422167B/en active Active
- 2022-12-26 WO PCT/CN2022/142004 patent/WO2024066094A1/en unknown
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103093000A (en) * | 2013-02-25 | 2013-05-08 | 用友软件股份有限公司 | Database query modeling system and database query modeling method |
| CN111126026A (en) * | 2019-12-17 | 2020-05-08 | 叮当快药科技集团有限公司 | Method and tool for generating visual report form by analyzing SQL statement |
| CN113326314A (en) * | 2021-06-30 | 2021-08-31 | 招商局金融科技有限公司 | Data visualization method and device, electronic equipment and readable storage medium |
| CN113641700A (en) * | 2021-08-30 | 2021-11-12 | 北京沃东天骏信息技术有限公司 | Data processing method and device based on Spring boot frame |
| CN113901135A (en) * | 2021-09-14 | 2022-01-07 | 威讯柏睿数据科技(北京)有限公司 | Cross-source heterogeneous data intelligent visual analysis display method and equipment |
| CN114218336A (en) * | 2021-12-17 | 2022-03-22 | 中国建设银行股份有限公司 | Data warehouse visual chart display method, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115422167A (en) | 2022-12-02 |
| WO2024066094A1 (en) | 2024-04-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106934062B (en) | Implementation method and system for querying elastic search | |
| CN110717319B (en) | Self-service report generation method, device, computing equipment and system | |
| US9152697B2 (en) | Real-time search of vertically partitioned, inverted indexes | |
| US7870152B2 (en) | Attaching and displaying annotations to changing data views | |
| US7505985B2 (en) | System and method of generating string-based search expressions using templates | |
| US9754010B2 (en) | Generation of cube metadata and query statement based on an enhanced star schema | |
| US8417690B2 (en) | Automatically avoiding unconstrained cartesian product joins | |
| US8244748B2 (en) | Including annotation data with disparate relational data | |
| US8290936B2 (en) | Executing a query plan with display of intermediate results | |
| US20050102613A1 (en) | Generating a hierarchical plain-text execution plan from a database query | |
| CN103186639B (en) | Data creation method and system | |
| US20070168380A1 (en) | System and method for storing text annotations with associated type information in a structured data store | |
| US20070061294A1 (en) | Source code file search | |
| CN115422167B (en) | Cross-data source database view visualization construction method and system | |
| CN114756569A (en) | Multi-layer parsing method of structured query statement, computer device and storage medium | |
| KR100899616B1 (en) | Method and system of management metadata using relational database management system | |
| JP3914081B2 (en) | Access authority setting method and structured document management system | |
| JP2001236352A (en) | Method and device for semistructured document retrieval and storage medium stored with semistructured document retrieval program | |
| US20080040312A1 (en) | Programmatic retrieval of tabular data within a cell of a query result | |
| CN114281845A (en) | Index generation method and device, electronic equipment and readable storage medium | |
| CN114186554A (en) | Script data processing method and device, computer equipment and storage medium | |
| CN114547083A (en) | Data processing method and device and electronic equipment | |
| CN109766480B (en) | Data query method and device | |
| KR101020234B1 (en) | Method of creating application program source for database and device thereof | |
| CN110263055B (en) | Parameter prompting method, device, equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |