CN113239044A - Management device and application system of SQL records for query - Google Patents
Management device and application system of SQL records for query Download PDFInfo
- Publication number
- CN113239044A CN113239044A CN202110538126.4A CN202110538126A CN113239044A CN 113239044 A CN113239044 A CN 113239044A CN 202110538126 A CN202110538126 A CN 202110538126A CN 113239044 A CN113239044 A CN 113239044A
- Authority
- CN
- China
- Prior art keywords
- sql
- record
- query
- management
- template
- 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
- 230000003993 interaction Effects 0.000 claims abstract description 6
- 230000004048 modification Effects 0.000 claims description 5
- 238000012986 modification Methods 0.000 claims description 5
- 238000007792 addition Methods 0.000 claims description 4
- 238000012217 deletion Methods 0.000 claims description 4
- 230000037430 deletion Effects 0.000 claims description 4
- 238000012423 maintenance Methods 0.000 abstract description 8
- 238000011161 development Methods 0.000 abstract description 5
- 239000000284 extract Substances 0.000 abstract description 3
- 238000007726 management method Methods 0.000 description 48
- 230000006872 improvement Effects 0.000 description 8
- 230000002688 persistence Effects 0.000 description 4
- 238000012795 verification Methods 0.000 description 3
- 241000208340 Araliaceae Species 0.000 description 2
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 description 2
- 235000003140 Panax quinquefolius Nutrition 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 235000008434 ginseng Nutrition 0.000 description 2
- 238000000034 method Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000052 comparative effect Effects 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2291—User-Defined Types; Storage management thereof
-
- 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/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- 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/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- 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
Abstract
The invention discloses a management device and an application system of SQL records for query, wherein the device comprises: the service database connection module is used for defining a connection interface of the service database based on the connection information of the service database; the template definition module is used for defining an SQL record template for query and providing a management interface for defining an SQL record for query by using the SQL record template for query; the record management module is used for managing and inquiring SQL records by using the management interface and performing data interaction with the corresponding service database through the connection interface; and the API interface module is used for providing a corresponding API interface for the application software according to the query SQL record. Compared with the prior art, the management device for the query SQL records extracts and encapsulates the query SQL command or the template from the code or the configuration file into the record which can be queried through the user interface, and then performs unified management on all the records, thereby improving the management efficiency and reducing the complexity and the cost of development and maintenance.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a management device and an application system for SQL records for query.
Background
For an application system, whether a C/S (Client/Server) or B/S (Browser/Server) structure, the essence is to provide information services for users. And the data is the core of informatization, so the informatization service can be understood as the data service in a narrow sense. From a system implementation level, providing data services is a series of processes, typically including: request data → get data → process data → present data.
The business data is usually stored in a database system on a database server, and most database systems currently use a relational database (e.g., Oracle, MySQL, etc.). The mode of interaction between the application system and the database system is as follows: first, registering a database driver, then calling an API (Application Programming Interface) provided by the database driver to establish a connection with a database system, and then performing a database operation by way of an API executing an SQL (Structured Query Language) statement, which generally includes: creation and update of data tables, query, addition, update, deletion and the like of records.
For the data access API, ODBC (Open Database Connectivity) in a Windows environment and JDBC (JAVA Database Connectivity) in a JAVA environment are commonly used in the industry.
Therefore, from the system implementation level, the management of the data service can be simply understood as the management of the SQL statement. For example: inquiring student information service, wherein the SQL Statement (SELECT) of the student is inquired correspondingly; newly adding student record service, and correspondingly adding SQL sentences (INSERT INTO) of newly added students; and updating the student information service, wherein the corresponding is to UPDATE the SQL statement (UPDATE) of the student.
The larger the system and the more complex the service, the more and more SQL statements are used. From the system implementation level, a large number of SQL statements exist in the system, and effective management is bound to be carried out, otherwise the maintainability and development efficiency of the system is directly influenced.
With the development of technical specifications (such as an ORM (object relational mapping) framework and a JPA (Java persistence API) specification), data access is no longer a JDBC API of a comparative bottom layer, and various persistence layer frameworks are replaced, and most of the persistence layer frameworks used in the industry are Hibernate and MyBatis, and Query statements supported by the Hibernate are not native SQL but are SQL-like, the Hibernate supports HQL (Hibernate Query Language), and the MyBatis supports custom SQL.
In fact, the underlying mechanism of the persistence framework is also to execute SQL, except that SQL syntax and definition are different. MyBatis is defined in configuration files (XML), while Hibernate is defined directly in code.
For such a definition mode, once the application system performs business rule adjustment, SQL is inevitably changed, and codes need to be modified, recompiled and distributed in a Hibernate framework; the MyBatis framework needs to modify the configuration file and restart the Web service in order to reload the configuration definition. Restarting the service and redistributing the code, which both affect the service provision for the information system, are even significant.
Moreover, the flooding of a large amount of SQL into configuration files and code directly increases the complexity of code maintenance and also increases the difficulty of testing. Moreover, the execution of the SQL statement and the business logic processing are mixed together, and the problem of database access or the problem of business logic cannot be accurately distinguished.
Disclosure of Invention
The invention aims to provide a management device and an application system for SQL records for query.
In order to achieve one of the above objects, an embodiment of the present invention provides a device for managing SQL records for queries, the device including:
the service database connection module is used for defining a connection interface of the service database based on the connection information of the service database;
the template definition module is used for defining an SQL record template for query and providing a management interface for defining an SQL record for query by using the SQL record template for query;
the record management module is used for managing and inquiring SQL records by using the management interface and performing data interaction with the corresponding service database through the connection interface;
and the API interface module is used for providing a corresponding API interface for the application software according to the query SQL record.
As a further improvement of an embodiment of the present invention, the connection interface is a JNDI identifier, and the JNDI identifier is a connection descriptor defining connection information of the service database;
the parameters of the SQL record template for query comprise the JNDI identification.
As a further improvement of an embodiment of the present invention, the parameters of the SQL record template for query further include:
record identification, record title, query SQL command template as the main key.
As a further improvement of an embodiment of the present invention, the parameters of the query SQL record template further include a block identifier, where the block identifier is used to distinguish a service block to which the query SQL record belongs.
As a further improvement of an embodiment of the present invention, the parameters of the SQL recording template for query further include a recording status, where the recording status includes draft, to-be-checked, on-shelf, and off-shelf, and the recording status is modified to control activation or deactivation of the corresponding SQL recording template, where only the SQL recording template whose recording status is on-shelf can be normally used.
As a further improvement of an embodiment of the present invention, the apparatus further includes:
and the record database is used for storing the SQL record for query, and after the record management module adds, deletes or modifies the SQL record for query, the addition, deletion or modification of the SQL record for query is synchronously stored in the record database.
As a further improvement of an embodiment of the present invention, the apparatus includes a plurality of record management modules, and the API interface module is further configured to, when receiving a plurality of query requests recorded by the application software in query SQL, allocate the plurality of query requests to different record management modules according to idle states of the plurality of record management modules, thereby implementing load balancing of the plurality of record management modules.
As a further improvement of an embodiment of the present invention, the record management module is further configured to verify a function of the SQL record for query online.
As a further improvement of an embodiment of the present invention, the record management module is further configured to automatically generate version information of an SQL record for query after the SQL record for query is changed.
In order to achieve one of the above objects, an embodiment of the present invention provides an application system, which includes application software, a service database, and a management apparatus for querying the SQL record as described above, wherein:
the application software is connected with the service database through the management device;
the application software acquires definition information recorded by SQL for query through an API interface provided by the management device, or remotely executes SQL commands through the API interface and the context parameters and acquires command execution results.
Compared with the prior art, the management device for the SQL record for query extracts and encapsulates the SQL command or the template for query from the code or the configuration file into the record which can be queried through the user interface, and then performs unified management on all the records, thereby improving the management efficiency and reducing the complexity and the cost of development and maintenance. Furthermore, the management device is provided with a record database, and the record database can be synchronously stored after the SQL record for query is changed, so that the application software does not need to be restarted after the SQL record for query is changed, the service provision of the application software is not influenced, and the operation and maintenance cost of the application software is reduced.
Drawings
FIG. 1 is a schematic structural diagram of a management apparatus for querying SQL records according to the present invention.
Fig. 2 is a schematic structural diagram of an application system of the present invention.
Detailed Description
The present invention will be described in detail below with reference to specific embodiments shown in the drawings. These embodiments are not intended to limit the present invention, and structural, methodological, or functional changes made by those skilled in the art according to these embodiments are included in the scope of the present invention.
The SQL command for query is an SQL command for querying database records, and the SQL command template for query is an SQL command without specific parameters. For example, the following two SQL statements represent the SQL command template and the SQL command, respectively:
SELECT*FROM t_prom_order WHERE(type＝？1)AND(status＝？2)；
SELECT*FROM t_prom_order WHERE(type＝1)AND(status＝3)。
since a large number of SQL statements (mainly including SQL commands and templates) are filled in the configuration files and codes, the complexity of application software code maintenance is directly increased, and the difficulty of application system testing is also increased.
Therefore, the invention provides a management device for SQL records for query, which extracts and encapsulates the SQL sentences used for query from codes or configuration files into SQL records for query, and performs unified maintenance and management on the records, thereby improving the management efficiency and reducing the complexity and cost of development and maintenance. The SQL record for query is used for packaging the SQL command template for query.
As shown in fig. 1, the management apparatus of the present invention includes a service database connection module, a template definition module, a record management module, and an API interface module.
Service database connection module
And the service database connection module is used for defining a connection interface of the service database based on the connection information of the service database. Specifically, the connection Interface is a JNDI (Java Naming and Directory Interface) identifier, and the JNDI identifier is a connection descriptor defining connection information of the service database. The following code is a definition example of JNDI identification, and after definition is completed, JNDI describes a character string as java:
<Resource name＝"jdbc/FOO"
scope＝"Shareable"
auth＝"Container"
factory＝"org.apache.naming.factory.BeanFactory"
type＝"com.mchange.v2.c3p0.ComboPooledDataSource"
driverClass＝"com.mysql.jdbc.Driver"
jdbcUrl＝"jdbc:mysql://<ip>:<port>/<db>？…"
password＝"xxxx"
user＝"xxxx"
…/>。
it should be noted that the connection information of different service databases is defined as different JNDI identifiers, and then different JNDI identifiers are selected to connect corresponding service databases, so that the device of the present invention can support different database sources and different data types.
Template definition module
The template definition module is used for defining an SQL record template for query and providing a management interface for defining an SQL record for query by using the SQL record template for query.
The query SQL record template is used for defining query SQL records, and the parameters of the query SQL record template comprise the JNDI identifier, so that a specific JNDI identifier needs to be defined when the query SQL records are defined, and the query SQL records can be connected to a corresponding service database through the JNDI identifier when a corresponding query SQL command is issued.
Further, the parameters of the query SQL record template further include:
record identification, record header, and SQL command template for query as a Primary Key PK (Primary Key of data table, whose value is used to uniquely identify a record in table).
Furthermore, for the situation that the number of SQL records for query is large, the SQL records can be isolated and managed according to the service plate by increasing the plate identification. Thus. The parameters of the query SQL record template further comprise a plate identification, and the plate identification is used for distinguishing the service plate to which the query SQL record belongs. For example: dividing the order and the commodity into 2 plates, collecting SQL records related to the order under the order plate, and collecting SQL records related to the commodity under the commodity plate. Such partitioning also facilitates the extension of rights, for example: the order related personnel can only manage the SQL records under the order plate, but cannot relate to the SQL records under the commodity plate.
Furthermore, the parameters of the SQL record template for query further comprise record states, the record states comprise drafts, to-be-examined, loading and unloading, and the start or stop of the corresponding SQL record template is controlled by modifying the record states, wherein only the SQL record template with the record state of loading can be normally used. The default state after the query is generated by the SQL record is draft, the state can be modified to be on shelf after the audit is passed, and the application system can use the SQL record to issue the SQL command after the on shelf is passed. In addition, when the SQL record is not needed for a while, the state can be modified to be off-shelf.
Table 1 below is an example of a query SQL record template:
table 1: tab _ SQL _ template (SQL record template definition table for query)
An example of an SQL command template entry for a query ("SQL _ templ") is as follows:
SELECT*FROM t_order_goods WHERE(order_id＝‘？1’)
wherein "? 1' is a context parameter placeholder, and the device supports at most 9 context parameters.
The page size entry ("page _ size") is used to control query paging, and may also pass a paging parameter in via a context parameter.
The record state ("status") is used for state control in query SQL, and only SQL in the on-shelf state can be referenced.
Record management module
The record management module is used for managing SQL records for query by using the management interface and carrying out data interaction with the corresponding service database through the connection interface. The record management module manages records according to the SQL record template for query (the management operation includes adding, deleting, modifying, querying and the like to the SQL records), and the record management module can also generate a specific SQL command according to specific parameters issued by application software received through the API interface module and perform data interaction with a corresponding service database through the service database connection module.
In a preferred embodiment, the record management module comprises a visual user interface for the administrator to perform the management operation, and the user interface is preferably provided by means of a web page.
Further, in order to check whether the query SQL record is grammatically correct or check the execution efficiency of the query SQL record, the record management module is further configured to verify the function of the query SQL record on line. One specific example of online verification is as follows:
the interactive operation of online verification is carried out on the webpage, and the operation mode is as follows: the input parameters are filled in first, and then verification is carried out. The parameters are of the form:
p1 ═ value of ginseng 1 > & p2 ═ value of ginseng 2 >
After the page is submitted and verified, the back end establishes connection with a target database system according to the JNDI recorded by the query SQL, analyzes the input parameters, takes out the parameter values, generates complete SQL sentences according to the SQL command template, executes and acquires results. Thereby verifying whether the syntax of the SQL command template is correct.
An example of generating a complete SQL statement is as follows:
SQL command template: SELECT FROM t _ prom _ order WHERE (type
Secondly, inputting parameters by a page: p1 ═ 1& p ═ 3
And the SQL statement is finally generated and executed: SELECT FROM t _ prom _ order WHERE (type 1) AND (status 3)
In addition, whether the execution efficiency of the SQL statement has a problem or not can be judged through the running time of the SQL statement.
In order to trace back the modification of the SQL record and facilitate the following inventors or managers to know the historical change condition of the SQL record, in another preferred embodiment, the record management module is further configured to automatically generate version information of the SQL record for query after the SQL record for query is changed.
API interface module
And the API interface module is used for providing a corresponding API interface for the application software according to the query SQL record. The corresponding API interface is provided to the application software, typically by querying the record identifier recorded in SQL. And the application software acquires the definition information of the corresponding SQL record or executes the corresponding SQL command according to the record identifier and acquires the result.
In a preferred embodiment, the device further comprises a record database.
Record database
The record database is used for storing the SQL record for query, and after the record management module adds, deletes or modifies the SQL record for query, the addition, deletion or modification of the SQL record for query is synchronously stored in the record database. Therefore, after the SQL records for query are changed, the application software does not need to be restarted, the service provision of the application software is not influenced, and the operation and maintenance cost of the application software is reduced.
Further, the device comprises a plurality of record management modules, and the API interface module is further configured to, when receiving a plurality of query requests for querying SQL records from application software, allocate the plurality of query requests to different record management modules according to idle states of the plurality of record management modules, thereby implementing load balancing of the plurality of record management modules.
As shown in fig. 2, the present invention further provides an application system, which includes application software, a service database, and the management apparatus for querying SQL records, wherein:
the application software is connected with the service database through the management device;
the application software acquires definition information recorded by SQL for query through an API interface provided by the management device, or remotely executes SQL commands through the API interface and the context parameters and acquires command execution results.
It should be noted that there may be a plurality of application software, and there may also be a plurality of service databases.
It should be understood that although the present description refers to embodiments, not every embodiment contains only a single technical solution, and such description is for clarity only, and those skilled in the art should make the description as a whole, and the technical solutions in the embodiments can also be combined appropriately to form other embodiments understood by those skilled in the art.
The above-listed detailed description is only a specific description of a possible embodiment of the present invention, and they are not intended to limit the scope of the present invention, and equivalent embodiments or modifications made without departing from the technical spirit of the present invention should be included in the scope of the present invention.
Claims (10)
1. A management apparatus for querying SQL records, the apparatus comprising:
the service database connection module is used for defining a connection interface of the service database based on the connection information of the service database;
the template definition module is used for defining an SQL record template for query and providing a management interface for defining an SQL record for query by using the SQL record template for query;
the record management module is used for managing and inquiring SQL records by using the management interface and performing data interaction with the corresponding service database through the connection interface;
and the API interface module is used for providing a corresponding API interface for the application software according to the query SQL record.
2. The apparatus for managing SQL records for queries according to claim 1, wherein:
the connection interface is a JNDI identifier, and the JNDI identifier is a connection descriptor for defining connection information of the service database;
the parameters of the SQL record template for query comprise the JNDI identification.
3. The apparatus for managing SQL records for query according to claim 2, wherein the parameters of the SQL record template for query further include:
record identification, record title, query SQL command template as the main key.
4. The apparatus for managing SQL records for queries according to claim 3, wherein:
the parameters of the query SQL record template further comprise a plate identification, and the plate identification is used for distinguishing the service plate to which the query SQL record belongs.
5. The apparatus for managing SQL records for queries according to claim 3, wherein:
the parameters of the SQL record template for query further comprise record states, the record states comprise drafts, to-be-audited, on-shelf and off-shelf, the start or stop of the corresponding SQL record template is controlled by modifying the record states, and only the SQL record template with the record state on-shelf can be normally used.
6. The apparatus for managing SQL records for query according to claim 1, wherein the apparatus further comprises:
and the record database is used for storing the SQL record for query, and after the record management module adds, deletes or modifies the SQL record for query, the addition, deletion or modification of the SQL record for query is synchronously stored in the record database.
7. The apparatus for managing SQL records for queries according to claim 6, wherein:
the device comprises a plurality of record management modules, wherein the API interface module is also used for distributing a plurality of query requests to different record management modules according to the idle states of the plurality of record management modules when receiving the plurality of query requests recorded by the application software in the SQL for query, thereby realizing the load balance of the plurality of record management modules.
8. The apparatus for managing SQL records for queries according to claim 1, wherein:
the record management module is also used for verifying the function of SQL record for query on line.
9. The apparatus for managing SQL records for queries according to claim 1, wherein:
the record management module is also used for automatically generating the version information of the SQL record for query after the SQL record for query is changed.
10. An application system, characterized in that the system comprises application software, a business database and a management device for query SQL recording according to claims 1-9, wherein:
the application software is connected with the service database through the management device;
the application software acquires definition information recorded by SQL for query through an API interface provided by the management device, or remotely executes SQL commands through the API interface and the context parameters and acquires command execution results.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110538126.4A CN113239044A (en) | 2021-05-18 | 2021-05-18 | Management device and application system of SQL records for query |
| PCT/CN2022/093283 WO2022242634A1 (en) | 2021-05-18 | 2022-05-17 | Sql record management apparatus for querying and application system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110538126.4A CN113239044A (en) | 2021-05-18 | 2021-05-18 | Management device and application system of SQL records for query |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113239044A true CN113239044A (en) | 2021-08-10 |
Family
ID=77135073
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110538126.4A Pending CN113239044A (en) | 2021-05-18 | 2021-05-18 | Management device and application system of SQL records for query |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113239044A (en) |
| WO (1) | WO2022242634A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022242634A1 (en) * | 2021-05-18 | 2022-11-24 | 安翰科技(武汉)股份有限公司 | Sql record management apparatus for querying and application system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106599015A (en) * | 2016-08-31 | 2017-04-26 | 重庆车杰盟科技有限公司 | Data service management system and method |
| CN108132987A (en) * | 2017-12-14 | 2018-06-08 | 浙江航天恒嘉数据科技有限公司 | A kind of data query system and method |
| CN109871393A (en) * | 2019-03-05 | 2019-06-11 | 云南电网有限责任公司信息中心 | A kind of access method based on label system |
| CN110019350A (en) * | 2017-07-28 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Data query method and apparatus based on configuration information |
| CN110990400A (en) * | 2019-11-20 | 2020-04-10 | 浙江大搜车软件技术有限公司 | Database query method and device, computer equipment and storage medium |
| CN111027720A (en) * | 2019-08-16 | 2020-04-17 | 中国人民解放军69007部队 | Novel equipment for integrated construction and realization of maintenance support information platform |
| CN111782923A (en) * | 2020-06-24 | 2020-10-16 | 平安科技（深圳）有限公司 | Data query method and device, electronic equipment and storage medium |
| CN112015752A (en) * | 2020-08-31 | 2020-12-01 | 杭州小电科技股份有限公司 | Method and device for dynamically querying data, electronic equipment and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8782081B2 (en) * | 2011-05-11 | 2014-07-15 | Google Inc. | Query template definition and transformation |
| CN111078702B (en) * | 2019-12-17 | 2022-08-26 | 南京南瑞继保工程技术有限公司 | SQL sentence classification management and unified query method and device |
| CN113239044A (en) * | 2021-05-18 | 2021-08-10 | 安翰科技(武汉)股份有限公司 | Management device and application system of SQL records for query |
-
2021
- 2021-05-18 CN CN202110538126.4A patent/CN113239044A/en active Pending
-
2022
- 2022-05-17 WO PCT/CN2022/093283 patent/WO2022242634A1/en unknown
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106599015A (en) * | 2016-08-31 | 2017-04-26 | 重庆车杰盟科技有限公司 | Data service management system and method |
| CN110019350A (en) * | 2017-07-28 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Data query method and apparatus based on configuration information |
| CN108132987A (en) * | 2017-12-14 | 2018-06-08 | 浙江航天恒嘉数据科技有限公司 | A kind of data query system and method |
| CN109871393A (en) * | 2019-03-05 | 2019-06-11 | 云南电网有限责任公司信息中心 | A kind of access method based on label system |
| CN111027720A (en) * | 2019-08-16 | 2020-04-17 | 中国人民解放军69007部队 | Novel equipment for integrated construction and realization of maintenance support information platform |
| CN110990400A (en) * | 2019-11-20 | 2020-04-10 | 浙江大搜车软件技术有限公司 | Database query method and device, computer equipment and storage medium |
| CN111782923A (en) * | 2020-06-24 | 2020-10-16 | 平安科技（深圳）有限公司 | Data query method and device, electronic equipment and storage medium |
| CN112015752A (en) * | 2020-08-31 | 2020-12-01 | 杭州小电科技股份有限公司 | Method and device for dynamically querying data, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022242634A1 (en) * | 2021-05-18 | 2022-11-24 | 安翰科技(武汉)股份有限公司 | Sql record management apparatus for querying and application system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022242634A1 (en) | 2022-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8065323B2 (en) | Offline validation of data in a database system for foreign key constraints | |
| US7401085B2 (en) | System and method for controlling the release of updates to a database configuration | |
| US9280568B2 (en) | Zero downtime schema evolution | |
| US8346747B2 (en) | Extending database tables in a multi-tenant environment | |
| US7814459B2 (en) | System and method for automated on demand replication setup | |
| US7917607B2 (en) | Software management systems and methods, including use of such systems and methods in a provider-tenant environment | |
| US7693851B2 (en) | Systems and methods for implementing a shared space in a provider-tenant environment | |
| US7698284B2 (en) | Systems and methods for deploying a tenant in a provider-tenant environment | |
| US7739348B2 (en) | Systems and methods for accessing a shared space in a provider-tenant environment by using middleware | |
| US20070156849A1 (en) | Systems and methods for delivering software upgrades in a provider-tenant environment | |
| US20080162509A1 (en) | Methods for updating a tenant space in a mega-tenancy environment | |
| US20030028550A1 (en) | Method, system, and program for maintaining information in database tables and performing operations on data in the database tables. | |
| US20070162969A1 (en) | Provider-tenant systems, and methods for using the same | |
| US20070156902A1 (en) | Systems and methods for implementing a tenant space in a provider-tenant environment | |
| US20070156650A1 (en) | Systems and methods for accessing a shared space in a provider-tenant environment | |
| US20070156700A1 (en) | Systems and methods for generating tenant-specific properties for use in a provider-tenant environment | |
| US8095570B2 (en) | Decorated model architecture for efficient model-driven application development | |
| US20070156699A1 (en) | Systems and methods for generating tenant templates for use in a provider-tenant environment | |
| US10445675B2 (en) | Confirming enforcement of business rules specified in a data access tier of a multi-tier application | |
| US20070162451A1 (en) | Systems and methods for linking a tenant to a provider | |
| US20150317331A1 (en) | Unified platform for application development | |
| KR20060045622A (en) | Extraction, transformation and loading designer module of a computerized financial system | |
| US20070156714A1 (en) | Systems and methods for analyzing tenant-specific properties for use in a provider-tenant environment | |
| US20080162483A1 (en) | Methods and systems for protecting shared tables against unauthorized overwriting from a tenant space in a mega-tenancy environment | |
| US10585909B2 (en) | Task-execution in a DBMS using stored procedures |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210810 |
|
| RJ01 | Rejection of invention patent application after publication |