For fourth-layer branch node N, the second syntax parsing rule can be used as the target rule, to parse fourth-layer branch node N into fifth-layer branch node D. For fourth-layer branch node D and fifth-layer branch node D, the second syntax parsing rule can be used as the target rule, to parse fourth-layer branch node D and fifth-layer branch node D into 0 and 1. Further, the statement “1011” can be derived based on a corresponding terminal symbol 0 or 1 at each layer. The syntax parsing tree can be obtained based on the above-mentioned parsing process.

S104: In response to determining, by using the compiler, that the data operation statement includes a command field that does not belong to syntax supported by the compiler, determine, by using a field translation relation pre-deployed in the compiler, a field corresponding to the command field in the syntax supported by the compiler, and use the field as a target field.

S106: Perform an operation corresponding to the data operation statement by using the compiler based on the target field, to process data to be processed corresponding to the data operation statement.

Further, when determining, by using the predetermined compiler, that the data operation statement includes a field that does not belong to the syntax supported by the compiler, the service area determines, by using the field translation relation pre-deployed in the compiler, the field corresponding to the command field in the syntax supported by the compiler, uses the field as the target field, and performs the operation corresponding to the data operation statement by using the compiler based on the target field, to process the data to be processed corresponding to the data operation statement. The syntax supported by the compiler here can be Neo4j syntax.

Specifically, after determining the syntax parsing tree corresponding to the data operation statement input by the user, the server can determine an execution sequence of machine code corresponding to the fields included in the data operation statement, use machine code corresponding to the target field as machine code corresponding to the command field, and perform the operation corresponding to the data operation statement based on the execution sequence.

For example, for a command field update in specified syntax, after determining that the command field is a field that does not belong to the syntax supported by the compiler, the compiler can determine a field set as a field corresponding to update by using the field translation relation pre-deployed in the compiler, so that when the data operation statement is compiled into machine code, machine code corresponding to set can be used as machine code corresponding to update.

It can be seen from the above-mentioned content that lexical analysis and syntax analysis can be performed on the data operation statement that is input by the user, is written based on specified syntax, and is used to process data in a graph database, and the syntax parsing tree can be generated based on an analysis result. Therefore, when the data operation statement input by the user is executed by using the compiler based on the generated syntax parsing tree, a command field that is included in the data operation statement, belongs to the specified syntax, and is not supported by the complier can be translated into a field in the syntax supported by the compiler, so as to process data to be processed stored in the graph database.

The data processing methods provided in one or more embodiments of this specification are described above. Based on the same idea, this specification further provides corresponding data processing apparatuses, as shown in FIG. 3.

FIG. 3 is a schematic diagram illustrating a data processing apparatus, according to this specification. The apparatus includes: an acquisition module 301, configured to obtain a data operation statement; a parsing module 302, configured to parse the data operation statement by using a predetermined compiler; a conversion module 303, configured to: in response to determining, by using the compiler, that the data operation statement includes a command field that does not belong to syntax supported by the compiler, determine, by using a field translation relation pre-deployed in the compiler, a field corresponding to the command field in the syntax supported by the compiler, and use the field as a target field; and an execution module 304, configured to perform an operation corresponding to the data operation statement by using the compiler based on the target field, to process data to be processed corresponding to the data operation statement.

Optionally, the execution module 304 is specifically configured to use machine code corresponding to the target field as machine code corresponding to the command field, and perform the operation corresponding to the data operation statement based on the machine code corresponding to the target field.

Optionally, the parsing module 302 is specifically configured to perform lexical analysis on the data operation statement by using the compiler, to extract fields included in the data operation statement, and parse the data operation statement based on the fields.

Optionally, the parsing module 302 is specifically configured to determine, from syntax parsing rules predetermined in the compiler, a syntax parsing rule that matches each field, and use the syntax parsing rule as a target rule; and generate a syntax parsing tree for the data operation statement based on the target rule, where each node corresponds to a field in the syntax parsing tree.

Optionally, the parsing module 302 is specifically configured to determine, based on the syntax parsing tree, an execution sequence of machine code corresponding to the fields included in the data operation statement, use machine code corresponding to the target field as machine code corresponding to the command field, and perform the operation corresponding to the data operation statement based on the execution sequence.

Optionally, the syntax supported by the compiler includes Neo4j syntax, and the syntax not supported by the compiler includes structured query language (SQL) syntax.

This specification further provides a computer-readable storage medium. The storage medium stores a computer program, and the computer program can be configured to perform the above-mentioned data processing method provided in FIG. 1.

This specification further provides a schematic diagram illustrating a structure of an electronic device, shown in FIG. 4, corresponding to FIG. 1. As shown in FIG. 4, in terms of hardware, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and certainly can further include hardware needed by another service. The processor reads a corresponding computer program from the non-volatile memory into the memory and runs the computer program, to implement the above-mentioned data processing method in FIG. 1. Certainly, in addition to software implementations, this specification does not exclude other implementations, for example, a logic device or a combination of hardware and software. In other words, an execution body of the following processing procedure is not limited to logical units, and can be hardware or a logic device.