WO2019148671A1

WO2019148671A1 - Xml file parsing method, device, computer apparatus, and storage medium

Info

Publication number: WO2019148671A1
Application number: PCT/CN2018/084227
Authority: WO
Inventors: 杨启正
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-01-30
Filing date: 2018-04-24
Publication date: 2019-08-08
Also published as: CN108255494A

Abstract

Embodiments of the present application disclose an XML file parsing method, a device, a computer apparatus, and a storage medium. The method comprises: replacing invalid characters in an XML file by means of a pre-determined file compiler, so as to generate a target XML file; successively loading, according to a pre-determined loading rule, child node objects in the target XML file to a memory; and parsing the child node objects to generate corresponding line record data until all the child node objects in the target XML file have been parsed to obtain the corresponding line record data.

Description

XML file parsing method, device, computer device and storage medium

This application claims priority to Chinese Patent Application No. 201810091360.5, filed on January 30, 2018, and entitled "An XML file parsing method, apparatus, computer equipment, and storage medium", the entire contents of which are incorporated herein by reference. This is incorporated herein by reference.

Technical field

The present application relates to the field of computer technologies, and in particular, to an XML file parsing method, apparatus, computer device, and storage medium.

Background technique

In the Linux operating environment, Linux commands are generally used to parse XML files in full. However, when using the Linux command to parse the XML file, it takes up more memory space and takes longer. In particular, when multiple XML files need to be parsed, it is easy to cause memory overflow errors by parsing multiple XML files in parallel. If multiple XML files are serially parsed, it takes longer and the parsing efficiency is low.

Summary of the invention

The embodiment of the present application provides an XML file parsing method, apparatus, computer device, and storage medium, so as to reduce the memory size occupied by the parsing process and reduce the time taken for parsing.

In a first aspect, an embodiment of the present application provides an XML file parsing method, including:

The illegal text substitution of the XML file by the preset text compiler to generate the target XML file;

Loading the child node object in the target XML file into the memory one by one according to a preset loading rule;

Parsing the child node object according to the label text pair form to generate row record data corresponding to the child node object;

Determining whether the child node object is the last child node object in the target XML file;

If the child node object is not the last child node object in the target XML file, loading the next child node object into the memory, and returning to perform the step of parsing the child node object according to the label text pair form Until the row record data corresponding to all the child node objects in the target XML file is parsed.

In a second aspect, an embodiment of the present application provides an XML file parsing apparatus, including:

a character replacement unit, configured to perform an illegal character replacement on the XML file by using a preset text compiler to generate a target XML file;

a loading unit, configured to load the child node object in the target XML file into the memory one by one according to a preset loading rule;

a parsing unit, configured to parse the child node object according to a label text pair form to generate row record data corresponding to the child node object;

An object determining unit, configured to determine whether the child node object is the last child node object in the target XML file;

The loading unit is further configured to: if the child node object is not the last child node object in the target XML file, load the next one of the child node objects into the memory, so that the parsing unit is to the child The node object is parsed according to the form of the label text until the row record data corresponding to all the child node objects in the target XML file is parsed.

In a third aspect, the embodiment of the present application further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program The XML file parsing method according to any one of the embodiments of the present application is implemented.

In a fourth aspect, the embodiment of the present application further provides a storage medium, wherein the storage medium stores a computer program, where the computer program includes program instructions, and the program instructions, when executed by the processor, cause the processor to execute The XML file parsing method according to any one of the embodiments of the present application.

The embodiment of the present application provides an XML file parsing method, apparatus, computer device, and storage medium. This method can make the parsing process occupy less memory and does not affect the terminal running other processes, especially for some terminals with lower memory configuration, so as to avoid memory overflow or insufficient memory. At the same time, the method can parse several or dozens of XML files in parallel, improve the parsing efficiency and reduce the time taken for parsing.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. Obviously, the drawings in the following description are some embodiments of the present application, For the ordinary technicians, other drawings can be obtained based on these drawings without any creative work.

FIG. 1 is a schematic flowchart of a method for parsing an XML file according to an embodiment of the present application;

FIG. 2 is another schematic flowchart of an XML file parsing method according to an embodiment of the present application;

3 is a schematic flowchart of a method for parsing an XML file shown in FIG. 1;

FIG. 4 is a schematic block diagram of an XML file parsing apparatus according to an embodiment of the present disclosure;

FIG. 5 is another schematic block diagram of an XML file parsing apparatus according to an embodiment of the present disclosure;

6 is a detailed schematic block diagram of the XML file parsing apparatus shown in FIG. 4;

FIG. 7 is a schematic block diagram of a computer device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of an XML file parsing method according to an embodiment of the present application. The XML file parsing method is applied to terminals such as desktop computers, laptop computers, and tablet computers. As shown in FIG. 1, the XML file parsing method includes steps S101 to S105.

S101. Perform an illegal character replacement on the XML file by using a preset text compiler to generate a target XML file.

In an embodiment, the preset text compiler may be a shell language sed command. For example, the sed command format can be: sed-i's∧(<userid>.*\)<\(.*<∨.*>\)∧1<\2/g'filename. Of course, in other embodiments, the preset text compiler may also be a tr command of the shell language. For example, the tr command format can be: tr-d"\46"<input_file>output_file. The preset text compiler can also be used for other commands for implementing illegal character replacement on the XML file, and is not specifically limited herein.

In general, when the encoding format of an XML file is not compatible with the text font in the XML file, an error is easily reported during parsing. For example, the XML file is in the latin-1 encoding format, and the text font in the XML file has both English font and Chinese font. Since the Chinese font is not compatible with the latin-1 encoding format, if the encoding format is not converted, in the subsequent parsing, Will report an error.

In an embodiment, as shown in FIG. 2, FIG. 2 is a schematic flowchart of an XML file parsing method according to an embodiment of the present application. Before step S101, steps S106 to S109 are further included.

S106. Obtain an encoding format of the XML file.

In an embodiment, the encoding format may be a Latin-1 encoding format or a other encoding format such as a UTF-8 encoding format, and is not specifically limited herein.

S107. Determine whether the text font of the XML file is compatible with the encoding format.

In an embodiment, determining whether the text font of the XML file is compatible with the encoding format, specifically: acquiring a type of the text font in the XML file, and determining whether the type of the text font is related to the encoding format compatible. The type of the text font includes a Chinese font, an English font, and the like.

If it is determined that the text font of the XML file is compatible with the encoding format, then the encoding format conversion is not required. In this case, step S101 may be performed, that is, the illegal character replacing step is performed.

If it is determined that the text font of the XML file is incompatible with the encoding format, in order to avoid an error in parsing, step S108 is performed at this time.

S108. If the text font of the XML file is incompatible with the encoding format, the XML file is encoded and converted by a preset character set encoding conversion command.

The preset character set encoding conversion command may be a piconv command in the Perl language. Specifically, the XML file can be encoded and converted in a byte stream by the piconv command. For example, the piconv command can convert the format of an XML file from a Latin-1 encoding format to a UTF-8 encoding format, thereby solving the problem of garbled errors when there are Chinese fonts in the XML file.

Since the piconv command is encoded in a byte stream format, the entire XML file is not placed in memory at one time, which avoids the problem of memory overflow caused by placing the entire XML file in memory at one time. Can slow down memory pressure and save memory.

S109. The XML file converted by the encoding format is set as the XML file, and the process returns to step S101.

After the encoding format conversion of the XML file, the XML file converted by the encoding format is replaced with the original XML file, and then step S101 is performed.

It should be noted that, in the embodiment shown in FIG. 2, the steps of encoding format compatibility judgment and encoding format conversion are performed first, and then illegal character replacement is performed. In other embodiments, the step of illegal character replacement may be performed first, and then the encoding format compatibility judgment and the encoding format conversion of the XML file after the illegal character replacement may be performed. It may be understood that, in this case, The encoded formatted XML file will be used as the target XML file, and then step S102 is performed. There is no restriction on the order of the two processes of encoding format conversion and illegal character replacement.

S102. Load the child node object in the target XML file into the memory one by one according to a preset loading rule.

Specifically, in an embodiment, loading the child node object in the target XML file into the memory according to the preset loading rule includes: when identifying a start tag of the root node object in the target XML file, Loading the child node object in the target XML file into the memory one by one by using the child node object of the next level of the root node object as a loading unit, wherein the root node object includes at least one of the child node objects .

For example, the content of the target XML file is:

In the above code example, the target XML file includes a root node object with a <book store> as a start tag and a </bookstore> as an end tag. The root node object includes four child node objects, each of which has a <book> as a start tag and </book> as an end tag. The four child nodes are child node objects of the next level of the root node object. Each child node object includes a start tag <book>, an end tag </book>, and a plurality of elements between the two. For example, one of the four elements of the first child object is <title>Harry Potter</title>.

It can be understood that in other code instances, the child node object may also include a grandchild node object, and the rule may nest the multi-layer node object. When there are at least three layer node objects in the target XML file, the child node object of the next level of the root node object is still the loading unit.

After reading the start tag <book store> of the root node object, the terminal loads the child node object into the memory unit by loading the child node object of the following level into the memory unit. That is, each time the content between the start tag <book> to the end tag </book> is loaded into memory. Each time a child node object is loaded, steps S103 and the like are performed to complete the parsing operation on the child node object, then the next child node object is loaded, and so on.

S103. Parse the child node object according to a label text pair form to generate row record data corresponding to the child node object.

Specifically, in an embodiment, the child node object may be parsed according to a label text pair form by an iterparse() method to generate row record data corresponding to the child node object. Among them, the iterparse() method is a method in ElementTree in the Python language.

For example, there are four elements between the child object <book> and </book>, one of which is: <title>Harry Potter</title>, "Harry Potter" is the text content of the element, and "title" is The label of the element. Then the iterparse() method parses with ">" as a trigger event and "</" as another trigger event, and gets the text content "Harry Potter" of the element between the two trigger events. At the same time, the text "Harry Potter" will be parsed as "title". The label "title" and the text content of the element "Harry Potter" form a label text pair. In the same way, you can get the other three label text pairs. The four label text pairs form a tuple, and one tuple records data for one line. For example, one line of record data Record={'title': 'Harry Potter', 'author': 'J K.Rowling', 'year': '2005', 'price': '29.99'}.

In an embodiment, in order to avoid memory overflow, after parsing the child node object according to the form of the label text pair to generate the line record data corresponding to the child node object, the method further includes: storing the line record data in the The line records the data file; and releases the memory space occupied by the child node object. That is to say, after the parsing of the child node object in the memory is completed, the row record data corresponding to the child node object is stored in the row record data file, and then the memory space occupied by the child node object is released, thereby The child node object provides memory space to avoid memory shortage or memory overflow.

S104. Determine whether the child node object is the last child node object in the target XML file.

After the completion of the parsing of the current child node object in the memory, it is determined whether the child node object in the current memory is the last child node object in the target XML file.

Specifically, in an embodiment, as shown in FIG. 3, FIG. 3 is a specific schematic flowchart of the XML file parsing method shown in FIG. 1. This step S104 includes steps S1041 to S1044.

S1041: Read a character string in the target XML file that is located after the current child node object.

For example, in the foregoing code example, assuming that the child node object in the current memory is the first child node object of the root node object, the terminal reads the string after the child node object in the current memory in the target XML file as "< Book>", the start tag of the next child node object. For example, if the current child node object in memory is the fourth child node object of the root node object, the terminal reads the string after the current child node object in the target XML file as "</bookstore>", that is, the root node. The end tag of the object.

S1042: Determine whether the character string is an end tag of a root node object.

For example, it is determined whether the character string read in step S1041 is the end tag of the root node object </book store>. If the string is not the end tag </book store> of the root node object, it is determined that the child node object in the current memory is not the last child node object in the target XML file, that is, step S1043 is performed. If the string is the end tag of the root node object </book store>, it indicates that the child node object in the current memory is the last child node object in the target XML file, that is, step S1044 is performed.

S1043. If the character string is not the end tag of the root node object, determine that the current child node object is not the last child node object in the target XML file.

S1044. If the character string is an end tag of the root node object, determine that the current child node object is the last child node object in the target XML file.

It should be noted that the manner of determining whether the current child node object in the memory is the last child node object in the target XML file is not limited to the manner shown in FIG. 3, and may be other modes, and is not specifically limited herein.

In this embodiment, when it is determined that the child node object in the current memory is the last child node object in the target XML file, it indicates that the target XML file has been parsed, and the parsing process may be ended. When it is determined that the current child node object in the memory is not the last child node object in the target XML file, it indicates that the target XML file has not been parsed yet, and step S105 needs to be performed.

S105. If the child node object is not the last child node object in the target XML file, load the next child node object into the memory, and return to perform execution on the child node object according to the label text pair form. The step of generating row record data corresponding to the child node object until the row record data corresponding to all the child node objects in the target XML file is parsed.

If the current child node object is not the last child node object in the target XML file, that is, the target XML file has not been parsed, the next child node object will continue to be read into the memory, and then the process returns to steps S103 to S105. Until step S104, it is determined that the child node object in the memory is the last child node object in the target XML file, thereby completing the parsing process of the entire target XML file.

In the XML file parsing method in this embodiment, the child node object is loaded into the memory and parsed one by one, so that the memory occupied by the parsing process is small, and the memory overflow or the insufficient memory is avoided. At the same time, the method can realize parsing several or dozens of XML files in parallel when parsing the XML file, thereby greatly shortening the time taken for parsing and improving the parsing efficiency.

The embodiment of the present application further provides an XML file parsing apparatus, which is used to execute any of the foregoing XML file parsing methods. Specifically, please refer to FIG. 4. FIG. 4 is a schematic block diagram of an XML file parsing apparatus according to an embodiment of the present application. The XML file parsing apparatus 300 can be installed in a terminal such as a desktop computer, a tablet computer, a laptop computer, or the like.

As shown in FIG. 4, the XML file parsing apparatus 300 includes a character replacing unit 301, a loading unit 302, a parsing unit 303, and an object judging unit 304.

The character replacement unit 301 is configured to perform an illegal character replacement on the XML file by using a preset text compiler to generate a target XML file.

In an embodiment, in order to avoid the parsing error caused by the incompatibility of the encoding format, as shown in FIG. 5, FIG. 5 is another schematic block diagram of an XML file parsing apparatus according to an embodiment of the present application. The XML file parsing apparatus 300 further includes a format acquisition unit 305, a format determination unit 306, and a code conversion unit 307.

The format obtaining unit 305 is configured to obtain an encoding format of the XML file.

The format determining unit 306 is configured to determine whether the text font of the XML file is compatible with the encoding format.

In an embodiment, the format determining unit 306 is specifically configured to acquire a type of the text font in the XML file, and determine whether the type of the text font is compatible with the encoding format. If the format determining unit 306 determines that the text font of the XML file is compatible with the encoding format, then the encoding format conversion is not required. At this time, the format determining unit 306 sends a first signal to the character replacing unit 301, and the character replacing unit After receiving the first signal, the 301 performs an illegal character replacement on the XML file by using a preset text compiler to generate a target XML file.

The encoding conversion unit 307 is configured to: if the text font of the XML file is incompatible with the encoding format, perform encoding format conversion on the XML file by using a preset character set encoding conversion command; and convert the encoded format XML file Set to the XML file.

The transcoding unit 307 can perform encoding format conversion on the XML file in a byte stream by the piconv command.

The encoding conversion unit 307 replaces the original format XML file with the XML file after the encoding format conversion of the XML file, and then the encoding conversion unit 307 sends a third signal to the character replacement unit 301 so that the character replacement unit After receiving the third signal, the 301 performs an illegal character replacement on the XML file by using a preset text compiler to generate a target XML file.

The loading unit 302 is configured to load the child node object in the target XML file into the memory one by one according to a preset loading rule.

In an embodiment, the loading unit 302 is specifically configured to: when the start tag of the root node object in the target XML file is identified, the child node object of the next level of the root node object is used as a loading unit, and one by one The child node object in the target XML file is loaded into memory, wherein the root node object includes at least one of the child node objects.

The parsing unit 303 is configured to parse the child node object according to a label text pair form to generate row record data corresponding to the child node object.

Specifically, in an embodiment, the parsing unit 303 may parse the child node object according to the label text pair form by the iterparse() method to generate row record data corresponding to the child node object. Among them, the iterparse() method is a method in ElementTree in the Python language.

In an embodiment, in order to avoid memory overflow, as shown in FIG. 5, the XML file parsing apparatus 300 further includes a storage unit 308 and a memory release unit 309. The storage unit 308 is configured to store the line record data in a line record data file. The memory release unit 309 is configured to release the memory space occupied by the child node object.

The object determining unit 304 is configured to determine whether the child node object is the last child node object in the target XML file.

Specifically, in an embodiment, as shown in FIG. 6, FIG. 6 is a specific schematic block diagram of the XML file parsing apparatus shown in FIG. The object judging unit 304 includes a reading sub-unit 3041 and a judging sub-unit 3042. The reading subunit 3041 is configured to read a character string in the target XML file that is located after the current child node object. The determining subunit 3042 is configured to determine whether the character string is an end tag of the root node object. If the determining subunit 3042 determines that the character string is not the end tag of the root node object, it is determined that the current child node object is not the last child node object in the target XML file. If the determining subunit 3042 determines that the character string is the end tag of the root node object, it is determined that the current child node object is the last child node object in the target XML file.

It should be noted that those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the XML file parsing apparatus 300 and the unit described above can refer to the corresponding embodiment in the foregoing XML file parsing method embodiment. The process will not be repeated here.

The XML file parsing apparatus 300 in this embodiment loads the child node object into the memory one by one and parses it, so that the memory occupied by the parsing process is small, and the memory overflow or the insufficient memory is avoided. At the same time, the XML file parsing apparatus 300 can realize parsing several or dozens of XML files in parallel, thereby greatly shortening the time taken for parsing and improving the parsing efficiency.

The above XML file parsing apparatus can be implemented in the form of a computer program which can be run on a computer device as shown in FIG. Please refer to FIG. 7. FIG. 7 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 400 can be a terminal. The terminal can be an electronic device such as a tablet computer, a notebook computer, a desktop computer, or a personal digital assistant.

The computer device 400 includes a processor 402, a memory, and a network interface 405 that are coupled by a system bus 401, where the memory can include a non-volatile storage medium 403 and an internal memory 404.

The non-volatile storage medium 403 can store an operating system 4031 and a computer program 4032. The computer program 4032 includes program instructions that, when executed, cause the processor 402 to perform an XML file parsing method.

The processor 402 is used to provide computing and control capabilities to support the operation of the entire computer device 400.

The internal memory 404 provides an environment for the operation of the computer program 4032 in the non-volatile storage medium 403, which when executed by the processor 402, causes the processor 402 to perform an XML file parsing method.

The network interface 405 is used for network communication, such as sending assigned tasks and the like. It will be understood by those skilled in the art that the structure shown in FIG. 7 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device 400 to which the solution of the present application is applied, and a specific computer device. 400 may include more or fewer components than shown in the figures, or some components may be combined, or have different component arrangements.

The processor 402 is configured to run a computer program 4032 stored in the memory to implement the following functions: performing illegal character replacement on the XML file by using a preset text compiler to generate a target XML file; loading one by one according to a preset loading rule. The child node object in the target XML file is in memory; the child node object is parsed according to the label text pair form to generate row record data corresponding to the child node object; and determining whether the child node object is the The last child node object in the target XML file; if the child node object is not the last child node object in the target XML file, loading the next child node object into the memory, and returning execution to the child node The object parses the form of the tag text pair until the line record data corresponding to all the child node objects in the target XML file is parsed.

In an embodiment, before executing the illegal character replacement of the XML file by the preset text compiler to generate the target XML file, the processor 402 further executes the following procedure: acquiring an encoding format of the XML file; determining the text of the XML file Whether the font is compatible with the encoding format; if the text font of the XML file is compatible with the encoding format, performing a step of performing illegal character replacement on the XML file by the preset text compiler to generate the target XML file; The text font of the XML file is incompatible with the encoding format, and the XML file is encoded and converted by a preset character set encoding conversion command; and the XML file converted by the encoding format is set as the XML file, and executed. The step of the default text compiler performing illegal character substitution on the XML file to generate the target XML file.

In an embodiment, when the processor 402 loads the child node object in the target XML file into the memory one by one according to the preset loading rule, the processor specifically executes the following procedure: when the root node object in the target XML file is identified When the tag is started, the child node object in the target XML file is loaded into the memory one by one by using the child node object of the next level of the root node object as a loading unit, wherein the root node object includes at least One of the child node objects.

In an embodiment, when performing the determining whether the child node object is the last child node object in the target XML file, the processor 402 specifically executes the following process: reading the current target file in the target XML file. a string after the child node object; determining whether the string is an end tag of the root node object; if the string is not an end tag of the root node object, determining that the current child node object is not The last child node object in the target XML file.

In an embodiment, after performing processing on the child node object according to the form of the label text pair to generate the line record data corresponding to the child node object, the processor 402 further executes the following procedure: storing the line record data In the row record data file; and release the memory space occupied by the child node object.

In an embodiment, when the processor 402 performs the parsing of the sub-object object according to the label text pair form to generate the line record data corresponding to the sub-node object, the following program is specifically executed: the iterparse() method is used to The child node object is parsed according to the form of the tag text pair to generate row record data corresponding to the child node object.

It should be understood that in the embodiment of the present application, the processor 402 may be a central processing unit, and may also be other general purpose processors, digital signal processors, application specific integrated circuits, off-the-shelf programmable gate arrays or other programmable logic devices, and discrete gates. Or transistor logic devices, discrete hardware components, and so on. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

In another embodiment of the present application, a storage medium is provided. The storage medium can be a computer readable storage medium. The storage medium stores a computer program, wherein the computer program includes program instructions. The program instructions, when executed by the processor, cause the processor to perform an XML file parsing method in the present application. The storage medium may be a medium that can store program codes, such as a USB flash drive, a removable hard disk, a Read-Only Memory (ROM), a flash memory, a magnetic disk, or an optical disk.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. The steps in the method of the embodiment of the present application may be sequentially adjusted, merged, and deleted according to actual needs. The units in the apparatus of the embodiment of the present application may be combined, divided, and deleted according to actual needs. In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The integrated unit can be stored in a storage medium if it is implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present application may be in essence or part of the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. There are a number of instructions for causing a computer device (which may be a personal computer, terminal, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any equivalents can be easily conceived by those skilled in the art within the technical scope disclosed in the present application. Modifications or substitutions are intended to be included within the scope of the present application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

An XML file parsing method, comprising:

The illegal text substitution of the XML file by the preset text compiler to generate the target XML file;

Loading the child node object in the target XML file into the memory one by one according to a preset loading rule;

Parsing the child node object according to the label text pair form to generate row record data corresponding to the child node object;

Determining whether the child node object is the last child node object in the target XML file;

If the child node object is not the last child node object in the target XML file, loading the next child node object into the memory, and returning to perform the step of parsing the child node object according to the label text pair form Until the row record data corresponding to all the child node objects in the target XML file is parsed.
The XML file parsing method according to claim 1, wherein before the illegal character replacement of the XML file by the preset text compiler to generate the target XML file, the method further includes:

Get the encoding format of the XML file;

Determining whether the text font of the XML file is compatible with the encoding format;

If the text font of the XML file is compatible with the encoding format, performing a step of performing illegal character replacement on the XML file by using a preset text compiler to generate a target XML file;

If the text font of the XML file is incompatible with the encoding format, encoding the XML file by using a preset character set encoding conversion command;

The encoded format converted XML file is set as the XML file, and a step of performing illegal character replacement on the XML file by the preset text compiler to generate the target XML file is performed.
The method for parsing an XML file according to claim 1, wherein the loading the child node object in the target XML file into the memory one by one according to a preset loading rule comprises:

When the start tag of the root node object in the target XML file is identified, the child node object in the target XML file is loaded one by one by using the child node object of the next level of the root node object as a loading unit. In memory, wherein the root node object includes at least one of the child node objects.
The XML file parsing method according to claim 1, wherein the determining whether the child node object is the last child node object in the target XML file comprises:

Reading a character string in the target XML file that is located after the current child node object;

Determining whether the string is an end tag of a root node object;

If the character string is not the end tag of the root node object, it is determined that the current child node object is not the last child node object in the target XML file.
The XML file parsing method according to claim 1, wherein after the parsing of the sub-object object in accordance with the form of the label text pair to generate the line record data corresponding to the child node object, the method further includes:

Storing the line record data in a line record data file;

Free up the memory space occupied by the child node object.
The XML file parsing method according to claim 1, wherein the parsing the sub-node object according to the form of the tag text pair to generate the row record data corresponding to the child node object comprises: using the iterparse() method The child node object is parsed according to a label text pair form to generate row record data corresponding to the child node object.
The XML file parsing method according to claim 2, wherein the encoding format conversion of the XML file by using a preset character set encoding conversion command comprises: using a piconv command to stream the XML file in a byte stream manner Perform encoding format conversion.
An XML file parsing apparatus includes:

a character replacement unit, configured to perform an illegal character replacement on the XML file by using a preset text compiler to generate a target XML file;

a loading unit, configured to load the child node object in the target XML file into the memory one by one according to a preset loading rule;

a parsing unit, configured to parse the child node object according to a label text pair form to generate row record data corresponding to the child node object;

An object determining unit, configured to determine whether the child node object is the last child node object in the target XML file;

The loading unit is further configured to: if the child node object is not the last child node object in the target XML file, load the next one of the child node objects into the memory, so that the parsing unit is to the child The node object is parsed according to the form of the label text until the row record data corresponding to all the child node objects in the target XML file is parsed.
The XML file parsing apparatus according to claim 8, further comprising:

a format obtaining unit, configured to obtain an encoding format of the XML file;

a format determining unit, configured to determine whether a text font of the XML file is compatible with the encoding format;

a code conversion unit, configured to: if the text font of the XML file is incompatible with the encoding format, perform encoding format conversion on the XML file by using a preset character set encoding conversion command; and set the XML file after converting the encoding format For the XML file;

The character replacement unit is specifically configured to: after the encoding conversion unit sets the XML file converted by the encoding format into the XML file, perform an illegal character replacement on the XML file by using a preset text compiler to generate a target XML file;

The character replacement unit is further configured to: if the text font of the XML file is compatible with the encoding format, perform an illegal character replacement on the XML file by using a preset text compiler to generate a target XML file.
A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the computer program by: presetting a text compiler Performing illegal character replacement on the XML file to generate a target XML file; loading the child node object in the target XML file into the memory one by one according to a preset loading rule; parsing the child node object according to the form of the label text to generate the Determining the row record data corresponding to the child node object; determining whether the child node object is the last child node object in the target XML file; if the child node object is not the last child node object in the target XML file, loading Passing the next child node object to the memory, and returning to perform the step of parsing the child node object according to the label text pair form until the row record corresponding to all the child node objects in the target XML file is parsed The data is up.
The computer device according to claim 10, wherein the processor performs an illegal character replacement of the XML file by the preset text compiler to generate the target XML file, and further: obtaining an encoding format of the XML file; determining the Whether the text font of the XML file is compatible with the encoding format; if the text font of the XML file is compatible with the encoding format, performing the step of performing illegal character replacement on the XML file by the preset text compiler to generate the target XML file If the text font of the XML file is incompatible with the encoding format, encoding the XML file by using a preset character set encoding conversion command; and setting the XML file converted by the encoding format to the XML file And performing the step of illegally replacing the XML file by the default text compiler to generate the target XML file.
The computer device according to claim 10, wherein when the processor executes loading the child node object in the target XML file into the memory one by one according to a preset loading rule, the specific implementation is: when the target XML file is identified When the start tag of the root node object is the child node object of the next level of the root node object, the child node object in the target XML file is loaded into the memory one by one, wherein the root The node object includes at least one of the child node objects.
The computer device according to claim 10, wherein, when the processor performs determining whether the child node object is the last child node object in the target XML file, the specific implementation is: reading the target XML file located a character string after the current child node object; determining whether the character string is an end tag of the root node object; if the character string is not an end tag of the root node object, determining the current The child node object is not the last child node object in the target XML file.
The computer device according to claim 10, wherein after the processor performs the parsing of the child node object in the form of the label text pair to generate the line record data corresponding to the child node object, the method further implements: The row record data is stored in the row record data file; and the memory space occupied by the child node object is released.
The computer device according to claim 10, wherein the processor performs a parsing of the form of the tag text pair to generate the row record data corresponding to the child node object, and the specific implementation is: by iterparse ( The method parses the child node object according to the form of the tag text pair to generate row record data corresponding to the child node object.
A storage medium, wherein the storage medium stores a computer program, the computer program comprising program instructions that, when executed by a processor, cause the processor to execute: by a preset text compiler to an XML file Performing illegal character replacement to generate a target XML file; loading the child node object in the target XML file into the memory one by one according to a preset loading rule; parsing the child node object according to the label text pair form to generate the child node The row corresponding to the object records data; determining whether the child node object is the last child node object in the target XML file; if the child node object is not the last child node object in the target XML file, loading the next node Deriving the child node object to the memory, and returning to perform the step of parsing the child node object according to the form of the label text pair until the line record data corresponding to all the child node objects in the target XML file is parsed.
The storage medium of claim 16, wherein the program instructions, when executed by the processor, perform an illegal character replacement of the XML file by the preset text compiler to generate the target XML file, further causing the processor to execute: acquire An encoding format of the XML file; determining whether the text font of the XML file is compatible with the encoding format; if the text font of the XML file is compatible with the encoding format, performing an illegal XML file by using a preset text compiler a step of replacing a character to generate a target XML file; if the text font of the XML file is incompatible with the encoding format, encoding the XML file by a preset character set encoding conversion command; and converting the encoding format The XML file is set to the XML file, and the step of performing illegal character replacement on the XML file by the preset text compiler to generate the target XML file is performed.
The storage medium of claim 16, wherein the program instructions, when executed by the processor to load the child node objects in the target XML file one by one according to a preset loading rule, cause the processor to execute: When the start tag of the root node object in the target XML file is identified, the child node object in the target XML file is loaded into the memory one by one by using the child node object of the next level of the root node object as a loading unit. Where the root node object includes at least one of the child node objects.
The storage medium of claim 16, wherein the program instructions, when executed by the processor to determine whether the child node object is the last child node object in the target XML file, cause the processor to execute: reading a character string in the target XML file that is located after the current child node object; determining whether the character string is an end tag of the root node object; if the character string is not an end tag of the root node object And determining that the current child node object is not the last child node object in the target XML file.
The storage medium according to claim 16, wherein said program instruction, after being executed by said processor to parse said child node object in accordance with a form of a tag text pair to generate line record data corresponding to said child node object, further The processor executes: storing the row record data in a line record data file; and releasing a memory space occupied by the child node object.