CN112965995A - Data interaction method and device based on PSQL of postgreSQL client - Google Patents
Data interaction method and device based on PSQL of postgreSQL client Download PDFInfo
- Publication number
- CN112965995A CN112965995A CN202110418278.0A CN202110418278A CN112965995A CN 112965995 A CN112965995 A CN 112965995A CN 202110418278 A CN202110418278 A CN 202110418278A CN 112965995 A CN112965995 A CN 112965995A
- Authority
- CN
- China
- Prior art keywords
- statement
- data definition
- definition statement
- syntax
- postgresql
- 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.)
- Granted
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/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/253—Grammatical analysis; Style critique
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computational Linguistics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Mathematical Physics (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- General Health & Medical Sciences (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a data interaction method and device based on a postgreSQL client PSQL, wherein the method comprises the following steps: judging whether the data definition statement is a PL/SQL object data definition statement; when the data definition statement is not a PL/SQL object data definition statement, analyzing the data definition statement according to SQL syntax; when the data definition statement is a PL/SQL object data definition statement, judging whether the PL/SQL object data definition statement is a PostgreSQL syntax statement or an Oracle syntax statement; if the statement is the PostgreSQL grammar statement, analyzing the data definition statement according to the preset grammar of the PostgreSQL; if the syntax statement of Oracle is available, analyzing the data definition statement according to the preset syntax of Oracle; and sending the analyzed data definition statement to a database. According to the data interaction method based on the PSQL of the postgreSQL client, the grammar difference between the postgreSQL and the Oracle can be correctly filtered, and smooth compatibility and automatic switching of two grammar modes are realized. In addition, the learning cost of a PostgreSQL user can be reduced, and the application migration efficiency is improved.
Description
Technical Field
The invention relates to the technical field of data interaction, in particular to a data interaction method and device based on a PSQL (pseudo-random QL) of a postgreSQL client.
Background
PSQL is a command line interactive client tool in PostgreSQL that allows for the interactive input of SQL commands and sends them in their entirety to the PostgreSQL server.
Existing PSQLs have an inherent rule in the interaction model that a user needs to enter functions in the PL/SQL syntax or store procedures, i.e., the PL procedure blocks must be wrapped using dollar symbols or quotation marks. Because PSQL is not compatible with the PL/SQL syntax in Oracle, application migration from Oracle to PostgreSQL becomes stuttered in the throat, and free-run work is invested.
Disclosure of Invention
The invention provides a data interaction method and device based on a PSQL client, aiming at solving the technical problem of how to improve the compatibility of the PSQL to different grammatical data.
The data interaction method based on the PSQL of the postgreSQL client side comprises the following steps:
judging whether the data definition statement is a PL/SQL object data definition statement;
when the data definition statement is not a PL/SQL object data definition statement, analyzing the data definition statement according to SQL syntax;
when the data definition statement is a PL/SQL object data definition statement, judging whether the PL/SQL object data definition statement is a PostgreSQL syntax statement or an Oracle syntax statement;
if the statement is a PostgreSQL grammar statement, analyzing the data definition statement according to a preset grammar of the PostgreSQL; if the syntax statement of Oracle is available, analyzing the data definition statement according to the preset syntax of Oracle;
and sending the analyzed data definition statement to a database.
According to the data interaction method based on the PSQL of the postgreSQL client, the grammar difference between the postgreSQL and the Oracle can be filtered correctly, and smooth compatibility and automatic switching of two grammar modes are achieved. In addition, the learning cost of a PostgreSQL user can be reduced, and the application migration efficiency is improved.
According to some embodiments of the invention, the determining whether the data definition statement is a PL/SQL object data definition statement comprises:
identifying whether AS or IS keywords exist in the data definition statement;
if not, judging that the data definition statement is not a PL/SQL object data definition statement;
and if so, judging whether the data definition statement IS a PL/SQL object data definition statement or not according to the character combination in front of the AS or IS key words.
In some embodiments of the present invention, the determining whether the data definition statement IS a PL/SQL object data definition statement according to a character combination before an AS or IS keyword includes:
identifying whether the character combination before the AS or IS keyword IS CREATE FUNCTION, PROCEDURE, PACKAGE;
if yes, judging that the data definition statement is a PL/SQL object data definition statement.
According to some embodiments of the present invention, when the data definition statement is a PL/SQL object data definition statement, determining whether the PL/SQL object data definition statement is a PostgreSQL syntax statement or an Oracle syntax statement includes:
identifying whether the AS or IS key words are character string qualifiers;
if yes, judging that the data PL/SQL object data definition statement is a PostgreSQL syntax statement; if not, judging that the data PL/SQL object data definition statement is an Oracle syntax statement.
In some embodiments of the present invention, when the statement definition statement is an Oracle syntax statement and the data definition statement is parsed according to a preset syntax of Oracle, whether the statement definition statement exits from a preset syntax parsing mode of Oracle is determined according to a begin and end number relationship in the statement definition statement.
The data interaction device based on the PSQL of the postgreSQL client comprises the following components:
the first judgment module is used for judging whether the data definition statement is a PL/SQL object data definition statement;
the first analysis module is used for analyzing the data definition statement according to SQL syntax when the data definition statement is not a PL/SQL object data definition statement;
the second judging module is used for judging whether the PL/SQL object data definition statement is a PostgreSQL syntax statement or an Oracle syntax statement when the data definition statement is the PL/SQL object data definition statement;
the second analysis module is used for analyzing the data definition statement according to the preset syntax of the PostgreSQL when the statement is judged to be the PostgreSQL syntax statement;
the third analysis module is used for analyzing the data definition statement according to the preset syntax of Oracle when the second judgment module judges that the statement is the Oracle syntax statement;
and the sending module is used for sending the analyzed data definition statement to a database.
According to the data interaction device based on the PSQL of the postgreSQL client, the grammar difference between the postgreSQL and the Oracle can be filtered correctly, and smooth compatibility and automatic switching of two grammar modes are achieved. In addition, the learning cost of a PostgreSQL user can be reduced, and the application migration efficiency is improved.
According to some embodiments of the present invention, the first determining module is specifically configured to:
identifying whether AS or IS keywords exist in the data definition statement;
if not, judging that the data definition statement is not a PL/SQL object data definition statement;
and if so, judging whether the data definition statement IS a PL/SQL object data definition statement or not according to the character combination in front of the AS or IS key words.
In some embodiments of the present invention, the first determining module is further configured to:
identifying whether the character combination before the AS or IS keyword IS CREATE FUNCTION, PROCEDURE, PACKAGE;
if yes, judging that the data definition statement is a PL/SQL object data definition statement.
According to some embodiments of the invention, the second determining module is specifically configured to:
identifying whether the AS or IS key words are character string qualifiers;
if yes, judging that the data PL/SQL object data definition statement is a PostgreSQL syntax statement; if not, judging that the data PL/SQL object data definition statement is an Oracle syntax statement.
In some embodiments of the invention, the interaction means further comprises:
and the mode management module is used for judging whether the statement definition statement exits from the preset syntax analysis mode of Oracle according to the begin and end number relation in the statement definition statement when the statement definition statement is the Oracle syntax statement and the data definition statement is analyzed according to the preset syntax of Oracle.
Drawings
FIG. 1 is a diagram illustrating PSQL and lex lexical parser interaction relationships according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a PSQL versus PL/SQL parsing method in the related art;
FIG. 3 is a flowchart of a data interaction method based on a postgreSQL client PSQL according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a data interaction method based on a postgreSQL client PSQL according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a data interaction device based on a postgreSQL client PSQL according to an embodiment of the present invention.
Reference numerals:
the interaction means (100) is provided with,
the first determining module 110, the second determining module 120,
a first parsing module 210, a second parsing module 220, a third parsing module 230,
a sending module 30 and a mode management module 40.
Detailed Description
To further explain the technical means and effects of the present invention adopted to achieve the intended purpose, the present invention will be described in detail with reference to the accompanying drawings and preferred embodiments.
First, the related concepts related to the present invention will be described.
SQL statements are divided into basic SQL and extended SQL (PL/SQL), and are introduced as follows:
SQL: SQL is a structured query language, which is relatively close to natural language, and only needs to say what, not how much, by using SQL. The system is composed of a data definition language, a data manipulation language and a data control language, and is not process-oriented, namely a previous statement is independent of a next statement. SQL is a standard language.
PL/SQL: PL/SQL (Procedural Language/SQL) is an extension to SQL that has absorbed many of the highest design features of programming languages in recent years: such as data encapsulation, information hiding, overloading, exception handling, etc. It allows the SQL data manipulation language and query statement to be contained in both block structures (PL/SQL blocks) and code procedural languages (e.g., C-functions, java scripts), making PL/SQL a powerful transactional language. In short, the following are: the process-oriented functionality is added so that stored procedures, stored functions, triggers, etc. can be written.
As shown in fig. 1, PSQL processes SQL input in the terminal through a lex lexical parser, which processes the input SQL statement into an identifier sequence. The lex lexical parser recognizes the identifier and returns the corresponding input state. If the identifier is a semicolon, the SQL input is marked to be ended. The complete sql is sent immediately to the database backend.
Due to the unique parsing rule of PSQL, it is difficult for multi-statement blocks composed of multiple basic SQL, such as PL/SQL blocks, to be correctly parsed and input.
As shown in fig. 2, the current solution to the above problem is: and converting the PL/SQL block into a character string to be contained in the data definition statement of the basic SQL, so that the PSQL mistakes that the current statement is a simple data definition statement, and sending the PL/SQL block as the character string to a background for further processing.
The PostgreSQL string qualifiers are single quotation marks or two consecutive dollar symbols, respectively. For example, the string "abc" may be expressed as 'abc' or $ $ abc $.
The scheme mainly aims to increase the compatible function of PSQL and PostgreSQL on the PL/SQL grammar of Oracle, improve the application migration efficiency and improve the usability of products.
As shown in fig. 3, the data interaction method based on the PSQL of the postgreSQL client according to the embodiment of the present invention includes:
s110, judging whether the data definition statement is a PL/SQL object data definition statement;
s120, when the data definition statement is not a PL/SQL object data definition statement, analyzing the data definition statement according to SQL syntax;
s130, when the data definition statement is a PL/SQL object data definition statement, judging whether the PL/SQL object data definition statement is a PostgreSQL syntax statement or an Oracle syntax statement;
s140, if the syntax statement is PostgreSQL, analyzing the data definition statement according to the preset syntax of the PostgreSQL; if the syntax statement of Oracle is available, analyzing the data definition statement according to the preset syntax of Oracle;
and S150, sending the analyzed data definition sentence to a database.
According to the data interaction method based on the PSQL of the postgreSQL client, the grammar difference between the postgreSQL and the Oracle can be filtered correctly, and smooth compatibility and automatic switching of two grammar modes are achieved. In addition, the learning cost of a PostgreSQL user can be reduced, and the application migration efficiency is improved.
According to some embodiments of the present invention, as shown in fig. 4, step S110 includes:
s111, identifying whether AS or IS keywords exist in the data definition statement;
s112, if the data definition statement does not exist, judging that the data definition statement is not a PL/SQL object data definition statement;
and S113, if yes, judging whether the data definition statement IS a PL/SQL object data definition statement according to the character combination in front of the AS or IS key words.
It should be noted that the data definition statements for creating PL/SQL objects are all fixed syntax, and the data definition statements always use the key AS or IS AS the guide key of the PL/SQL block. Therefore, whether the data definition statement IS a PL/SQL object data definition statement can be judged by whether the AS or IS key words exist in the data definition statement.
In some embodiments of the invention, step S113 comprises:
it IS identified whether the character combination preceding the AS or IS key IS a CREATE FUNCTION, or PROCEDURE, or PACKAGE. If yes, judging the data definition statement as a PL/SQL object data definition statement.
That IS, the present invention determines whether the data definition statement IS a PL/SQL object data definition statement by identifying whether the key AS or IS preceded by a key combination such AS CREATE FUNCTION/process/PACKAGE.
According to some embodiments of the invention, step S130 comprises:
s131, identifying whether the AS or IS key words are character string qualifiers;
s132, if yes, judging that the PL/SQL object data definition statement is a PostgreSQL syntax statement; if not, judging that the PL/SQL object data definition statement is an Oracle syntax statement.
That IS, in the embodiment of the present invention, if the data definition statement IS found to be the data definition statement of the PL/SQL object, the condition IS set according to whether the first non-blank identifier after the AS/IS key IS the string qualifier. If so, the data definition statement is parsed in the native syntax style of PostgreSQL. If not, analyzing the PL/SQL data definition statement according to the syntax style of Oracle. For example, whether the first non-blank identifier after the AS/IS keyword IS a string qualifier can be identified by lex, so that the PostgreSQL mode IS entered, and otherwise the Oracle mode IS entered.
In some embodiments of the present invention, when the statement definition statement is an Oracle syntax statement and the data definition statement is parsed according to a preset syntax of Oracle, whether the preset syntax parsing mode of Oracle exits is determined according to a begin and end number relationship in the statement definition statement.
Referring to fig. 4, the management method of the mode of the present invention includes: while in Oracle mode, it is necessary to determine when to exit the mode. The invention is similar to the method of the stack, and when the keyword BEGIN is encountered, the next layer of Oracle mode is entered. And when END is met, exiting the current layer mode and judging whether the current layer mode is in the Oracle mode, otherwise entering the PostgreSQL mode until the semicolon indicates that the sentence input is completed.
Wherein, when the PL/SQL style grammar is input, except for recognizing the keywords begin and end, all the other identifiers need to be added to buff, and a shaping variable count is initialized to 0, when the keyword begin is recognized, the count is added to 1, and when the keyword end is recognized, it is determined whether the count is greater than zero? If yes, count performs a subtract 1 operation, equal to 0, and resumes the parsing mode of PostgreSQL until a semicolon is encountered indicating that the input is complete.
The data interaction device based on the PSQL of the postgreSQL client comprises the following components: the device comprises a first judgment module, a second judgment module, a first analysis module, a second analysis module, a third analysis module and a sending module.
The first judging module is used for judging whether the data definition statement is a PL/SQL object data definition statement;
the first analysis module is used for analyzing the data definition statements according to SQL syntax when the data definition statements are not PL/SQL object data definition statements;
the second judging module is used for judging whether the PL/SQL object data definition statement is a PostgreSQL syntax statement or an Oracle syntax statement when the data definition statement is the PL/SQL object data definition statement;
the second parsing module is used for parsing the data definition statement according to the preset syntax of the PostgreSQL when the statement is judged to be the PostgreSQL syntax statement;
the third analysis module is used for analyzing the data definition statement according to the preset syntax of Oracle when the second judgment module judges that the statement is the Oracle syntax statement;
and the sending module is used for sending the analyzed data definition statement to a database.
According to the data interaction device based on the PSQL of the postgreSQL client, the grammar difference between the postgreSQL and the Oracle can be filtered correctly, and smooth compatibility and automatic switching of two grammar modes are achieved. In addition, the learning cost of a PostgreSQL user can be reduced, and the application migration efficiency is improved.
According to some embodiments of the present invention, the first determining module is specifically configured to:
identifying whether AS or IS keywords exist in the data definition statement;
if not, judging that the data definition statement is not a PL/SQL object data definition statement;
if yes, judging whether the data definition statement IS a PL/SQL object data definition statement or not according to the character combination in front of the AS or IS key words.
It should be noted that the data definition statements for creating PL/SQL objects are all fixed syntax, and the data definition statements always use the key AS or IS AS the guide key of the PL/SQL block. Therefore, whether the data definition statement IS a PL/SQL object data definition statement can be judged by whether the AS or IS key words exist in the data definition statement.
In some embodiments of the present invention, the first determining module is further configured to:
identifying whether the character combination before the AS or IS keyword IS CREATE FUNCTION, PROCEDURE, PACKAGE; if yes, judging the data definition statement as a PL/SQL object data definition statement.
That IS, the first judgment module judges whether the data definition sentence IS a PL/SQL object data definition sentence by identifying whether the key AS or IS key IS preceded by a combination of keys such AS CREATE FUNCTION/PROCEDURE/PACKAGE.
According to some embodiments of the invention, the second determining module is specifically configured to:
identifying AS or IS keywords followed by string qualifiers. If yes, judging that the data PL/SQL object data definition statement is a PostgreSQL syntax statement; if not, judging that the PL/SQL object data definition statement is an Oracle syntax statement.
That IS, in the embodiment of the present invention, if the data definition statement IS found to be the data definition statement of the PL/SQL object, the condition IS set according to whether the first non-blank identifier after the AS/IS key IS the string qualifier. If so, the data definition statement is parsed in the native syntax style of PostgreSQL. If not, analyzing the PL/SQL data definition statement according to the syntax style of Oracle. For example, whether the first non-blank identifier after the AS/IS keyword IS a string qualifier can be identified by lex, so that the PostgreSQL mode IS entered, and otherwise the Oracle mode IS entered.
In some embodiments of the invention, the interaction means further comprises: and the mode management module is used for judging whether the statement definition statement exits from the preset syntax analysis mode of Oracle according to the begin and end number relation in the statement definition statement when the statement definition statement is the Oracle syntax statement and the data definition statement is analyzed according to the preset syntax of Oracle.
Referring to fig. 4, the management method of the mode of the present invention includes: while in Oracle mode, it is necessary to determine when to exit the mode. The invention is similar to the method of the stack, and when the keyword BEGIN is encountered, the next layer of Oracle mode is entered. And when END is met, exiting the current layer mode and judging whether the current layer mode is in the Oracle mode, otherwise entering the PostgreSQL mode until the semicolon indicates that the sentence input is completed.
Wherein, when the PL/SQL style grammar is input, except for recognizing the keywords begin and end, all the other identifiers need to be added to buff, and a shaping variable count is initialized to 0, when the keyword begin is recognized, the count is added to 1, and when the keyword end is recognized, it is determined whether the count is greater than zero? If yes, count performs a subtract 1 operation, equal to 0, and resumes the parsing mode of PostgreSQL until a semicolon is encountered indicating that the input is complete.
While the invention has been described in connection with specific embodiments thereof, it is to be understood that it is intended by the appended drawings and description that the invention may be embodied in other specific forms without departing from the spirit or scope of the invention.
Claims (10)
1. A data interaction method based on a postgreSQL client PSQL is characterized by comprising the following steps:
judging whether the data definition statement is a PL/SQL object data definition statement;
when the data definition statement is not a PL/SQL object data definition statement, analyzing the data definition statement according to SQL syntax;
when the data definition statement is a PL/SQL object data definition statement, judging whether the PL/SQL object data definition statement is a PostgreSQL syntax statement or an Oracle syntax statement;
if the statement is a PostgreSQL grammar statement, analyzing the data definition statement according to a preset grammar of the PostgreSQL; if the syntax statement of Oracle is available, analyzing the data definition statement according to the preset syntax of Oracle;
and sending the analyzed data definition statement to a database.
2. The method for data interaction based on the postgreSQL client PSQL according to claim 1, wherein the determining whether the data definition statement is a PL/SQL object data definition statement comprises:
identifying whether AS or IS keywords exist in the data definition statement;
if not, judging that the data definition statement is not a PL/SQL object data definition statement;
and if so, judging whether the data definition statement IS a PL/SQL object data definition statement or not according to the character combination in front of the AS or IS key words.
3. The method for data interaction based on the PSQL of the postgreSQL client according to claim 2, wherein the determining whether the data definition statement IS a PL/SQL object data definition statement according to a character combination before an AS or IS keyword comprises:
identifying whether the character combination before the AS or IS keyword IS CREATE FUNCTION, PROCEDURE, PACKAGE;
if yes, judging that the data definition statement is a PL/SQL object data definition statement.
4. The method of claim 2, wherein when the data definition statement is a PL/SQL object data definition statement, determining whether the PL/SQL object data definition statement is a postgreSQL syntax statement or an Oracle syntax statement comprises:
identifying whether the AS or IS key words are character string qualifiers;
if yes, judging that the data PL/SQL object data definition statement is a PostgreSQL syntax statement; if not, judging that the data PL/SQL object data definition statement is an Oracle syntax statement.
5. The method as claimed in claim 1, wherein when the statement definition sentence is an Oracle syntax sentence and the data definition sentence is parsed according to a preset syntax of Oracle, determining whether to exit from a preset syntax parsing mode of Oracle according to a relation between begin and end numbers in the statement definition sentence.
6. A data interaction device based on a postgreSQL client PSQL is characterized by comprising:
the first judgment module is used for judging whether the data definition statement is a PL/SQL object data definition statement;
the first analysis module is used for analyzing the data definition statement according to SQL syntax when the data definition statement is not a PL/SQL object data definition statement;
the second judging module is used for judging whether the PL/SQL object data definition statement is a PostgreSQL syntax statement or an Oracle syntax statement when the data definition statement is the PL/SQL object data definition statement;
the second analysis module is used for analyzing the data definition statement according to the preset syntax of the PostgreSQL when the statement is judged to be the PostgreSQL syntax statement;
the third analysis module is used for analyzing the data definition statement according to the preset syntax of Oracle when the second judgment module judges that the statement is the Oracle syntax statement;
and the sending module is used for sending the analyzed data definition statement to a database.
7. The data interaction device based on the PSQL of the postgreSQL client according to claim 6, wherein the first determining module is specifically configured to:
identifying whether AS or IS keywords exist in the data definition statement;
if not, judging that the data definition statement is not a PL/SQL object data definition statement;
and if so, judging whether the data definition statement IS a PL/SQL object data definition statement or not according to the character combination in front of the AS or IS key words.
8. The apparatus according to claim 7, wherein the first determining module is further configured to:
identifying whether the character combination before the AS or IS keyword IS CREATE FUNCTION, PROCEDURE, PACKAGE;
if yes, judging that the data definition statement is a PL/SQL object data definition statement.
9. The data interaction device based on the postgreSQL client PSQL according to claim 7, wherein the second determining module is specifically configured to:
identifying whether the AS or IS key words are character string qualifiers;
if yes, judging that the data PL/SQL object data definition statement is a PostgreSQL syntax statement; if not, judging that the data PL/SQL object data definition statement is an Oracle syntax statement.
10. The postgreSQL client PSQL-based data interaction device according to claim 6, further comprising:
and the mode management module is used for judging whether the statement definition statement exits from the preset syntax analysis mode of Oracle according to the begin and end number relation in the statement definition statement when the statement definition statement is the Oracle syntax statement and the data definition statement is analyzed according to the preset syntax of Oracle.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110418278.0A CN112965995B (en) | 2021-04-19 | 2021-04-19 | Data interaction method and device based on PSQL of postgreSQL client |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110418278.0A CN112965995B (en) | 2021-04-19 | 2021-04-19 | Data interaction method and device based on PSQL of postgreSQL client |
Publications (2)
Publication Number | Publication Date |
---|---|
CN112965995A true CN112965995A (en) | 2021-06-15 |
CN112965995B CN112965995B (en) | 2023-03-31 |
Family
ID=76280852
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110418278.0A Active CN112965995B (en) | 2021-04-19 | 2021-04-19 | Data interaction method and device based on PSQL of postgreSQL client |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112965995B (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113626465A (en) * | 2021-08-09 | 2021-11-09 | 瀚高基础软件股份有限公司 | Database and method for realizing session-level variable in postgresql database |
CN113722351A (en) * | 2021-08-30 | 2021-11-30 | 杭州安恒信息安全技术有限公司 | Parameter restoration method and device in access flow of Oracle database |
CN113901449A (en) * | 2021-09-07 | 2022-01-07 | 燕山大学 | Static and dynamic execution-based second-order SQL injection defense and detection method |
CN115757339A (en) * | 2022-11-16 | 2023-03-07 | 恒辉信达技术有限公司 | Method for automatically converting Oracle script into Postgresql script |
CN116150250A (en) * | 2023-04-20 | 2023-05-23 | 瀚高基础软件股份有限公司 | PostgreSQL-based dual-port analysis method and device |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170103106A1 (en) * | 2015-10-07 | 2017-04-13 | International Business Machines Corporation | Processing sql statement in alternating modes |
US20180218032A1 (en) * | 2017-01-31 | 2018-08-02 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing conditional statement execution within a multi-tenant aware structured query language |
CN110019291A (en) * | 2017-09-04 | 2019-07-16 | 中国移动通信集团浙江有限公司 | A kind of SQL analytic method and SQL resolver |
CN111143330A (en) * | 2019-12-27 | 2020-05-12 | 湖南亚信软件有限公司 | Method and device for realizing multi-mode database analysis engine |
-
2021
- 2021-04-19 CN CN202110418278.0A patent/CN112965995B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170103106A1 (en) * | 2015-10-07 | 2017-04-13 | International Business Machines Corporation | Processing sql statement in alternating modes |
US20180218032A1 (en) * | 2017-01-31 | 2018-08-02 | Salesforce.Com, Inc. | Systems, methods, and apparatuses for implementing conditional statement execution within a multi-tenant aware structured query language |
CN110019291A (en) * | 2017-09-04 | 2019-07-16 | 中国移动通信集团浙江有限公司 | A kind of SQL analytic method and SQL resolver |
CN111143330A (en) * | 2019-12-27 | 2020-05-12 | 湖南亚信软件有限公司 | Method and device for realizing multi-mode database analysis engine |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113626465A (en) * | 2021-08-09 | 2021-11-09 | 瀚高基础软件股份有限公司 | Database and method for realizing session-level variable in postgresql database |
CN113626465B (en) * | 2021-08-09 | 2023-06-20 | 瀚高基础软件股份有限公司 | Database and method for realizing session-level variables in postgresql database |
CN113722351A (en) * | 2021-08-30 | 2021-11-30 | 杭州安恒信息安全技术有限公司 | Parameter restoration method and device in access flow of Oracle database |
CN113722351B (en) * | 2021-08-30 | 2024-01-30 | 杭州安恒信息安全技术有限公司 | Parameter restoration method and device in Oracle database access flow |
CN113901449A (en) * | 2021-09-07 | 2022-01-07 | 燕山大学 | Static and dynamic execution-based second-order SQL injection defense and detection method |
CN113901449B (en) * | 2021-09-07 | 2023-08-15 | 燕山大学 | Method for defending and detecting second-order SQL injection loopholes based on static and dynamic execution |
CN115757339A (en) * | 2022-11-16 | 2023-03-07 | 恒辉信达技术有限公司 | Method for automatically converting Oracle script into Postgresql script |
CN116150250A (en) * | 2023-04-20 | 2023-05-23 | 瀚高基础软件股份有限公司 | PostgreSQL-based dual-port analysis method and device |
Also Published As
Publication number | Publication date |
---|---|
CN112965995B (en) | 2023-03-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN112965995B (en) | Data interaction method and device based on PSQL of postgreSQL client | |
US11126798B1 (en) | Applied artificial intelligence technology for conversational inferencing and interactive natural language generation | |
US9710243B2 (en) | Parser that uses a reflection technique to build a program semantic tree | |
CN109033410B (en) | SQL (structured query language) analysis method based on regular and character string cutting | |
CN107680588B (en) | Intelligent voice navigation method, device and storage medium | |
CN108228173B (en) | Visual data interface development system and method | |
CN105512105A (en) | Semantic parsing method and device | |
CN112817876B (en) | Code diagnosis method, device, server, user equipment and storage medium | |
CN110597844A (en) | Heterogeneous database data unified access method and related equipment | |
CN112416962A (en) | Data query method, device and storage medium | |
CN107169092A (en) | Intelligent Recognition and the method and system of sensitive content are handled in interaction | |
CN110263121B (en) | Table data processing method, apparatus, electronic apparatus and computer readable storage medium | |
CN105095180A (en) | Chinese name broadcasting method and device | |
JP2012003704A (en) | Faq candidate extraction system and faq candidate extraction program | |
CN113792542A (en) | Intention understanding method fusing syntactic analysis and semantic role pruning | |
CN114064601B (en) | Storage process conversion method, device, equipment and storage medium | |
CN111241130A (en) | SQL language-based grammar statement extension method and system | |
CN115794857A (en) | Query request processing method and device | |
US20140195306A1 (en) | Enterprise decision management | |
CN112835925B (en) | SQL statement analysis method for embedded chip | |
CN112162738B (en) | Data conversion method and device, terminal equipment and storage medium | |
CN111651348B (en) | Debugging system of chat robot | |
KR100290623B1 (en) | A method of controlling data of database | |
CN117539752A (en) | Difference generation method, display method, device, equipment and storage medium | |
CN115455910A (en) | Method and system for converting WAF rule into IPS rule |
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 |