CN107273386B - XML Schema constraint file generation method and device for database - Google Patents
XML Schema constraint file generation method and device for database Download PDFInfo
- Publication number
- CN107273386B CN107273386B CN201610218128.4A CN201610218128A CN107273386B CN 107273386 B CN107273386 B CN 107273386B CN 201610218128 A CN201610218128 A CN 201610218128A CN 107273386 B CN107273386 B CN 107273386B
- Authority
- CN
- China
- Prior art keywords
- node
- attribute
- instance
- generating
- mark
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
- G06F16/84—Mapping; Conversion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention provides a method and a device for generating an XML Schema constraint file of a database, wherein the method comprises the following steps: determining a node data model, the node data model comprising: node name, node level, node number limit, node data type, whether null is allowed or not and node sequence; determining a node instance according to the node data model, the node instance comprising: a first node and a first node attribute, a second node and a second node attribute, and a third node attribute; and generating an XML Schema constraint file according to the node instance. By implementing the method, the user can quickly and accurately generate the Schema constraint file, and errors such as node repetition and the like caused by manually editing the Schema file are avoided.
Description
Technical Field
The invention relates to the technical field of databases, in particular to a method and a device for generating an XML Schema constraint file of a database.
Background
Extensible Markup Language (XML) databases are increasingly applied to various scenarios, such as Factory Automation software platform (FA) systems. The XML database stores and queries data in XML format files. Because of the text properties of XML documents, which are easily edited by human error, such as by deleting letters by mistake, creating nodes repeatedly, etc., it becomes necessary to restrict the validity of the XML documents.
At present, a method for constraining the validity of an XML file is to establish a corresponding XML Schema constraint file, and perform specification constraint on nodes and attributes thereof in the XML file in the Schema file, but because the number of XML files usually related to one XML database is very large, it is very time-consuming and inefficient for a user to edit the Schema file one by one.
Disclosure of Invention
In order to solve the problems of low efficiency and easy error in manual editing of Schema files by users in the prior art, embodiments of the present invention provide a method and an apparatus for generating an XML Schema constraint file of an XML database.
In order to solve the above problem, an embodiment of the present invention discloses a method for generating an XML Schema constraint file of a database, including:
determining a node data model, wherein the node data model comprises at least one of the following information: node name, node level, node number limit, node data type, whether null is allowed or not and node sequence;
determining a node instance according to the node data model, the node instance comprising: a first node and a first node attribute, a second node and a second node attribute, and a third node attribute; wherein the first node is a root node; the second node is a child node of the first node; the third node is a child node of the second node;
and generating an XML Schema constraint file according to the node instance.
In an optional embodiment of the invention, the determining the node instance according to the node data model includes:
acquiring node attribute data input by a user;
and generating a corresponding node instance by using the node attribute data and the node data model.
Optionally, the node instance includes: a first node, at least one second node and at least three third nodes.
Optionally, the generating an XML Schema constraint file according to the node instance includes:
generating a corresponding first node mark and a first node attribute mark according to the first node and the first node attribute;
sequentially generating corresponding second node marks and second node attribute marks according to the second nodes and the second node attributes until all the second nodes are processed;
determining third nodes and third node attributes corresponding to the second nodes and generating corresponding third node marks and third node attribute marks;
and generating an XML Schema constraint file according to the generated first node mark and the first node attribute mark, the generated second node mark and the generated second node attribute mark, and the generated third node mark and the generated third node attribute mark.
The embodiment of the invention also discloses a device for generating the XML Schema constraint file of the database, which comprises the following steps: a data model determination module, a node instance determination module, and a constraint file generation module, wherein,
a data model determination module for determining a node data model, the node data model comprising at least one of the following information: node name, node level, node number limit, node data type, whether null is allowed or not and node sequence;
a node instance determining module, configured to determine a node instance according to the node data model, where the node instance includes: a first node and a first node attribute, a second node and a second node attribute, and a third node attribute; wherein the first node is a root node; the second node is a child node of the first node; the third node is a child node of the second node;
and the constraint file generation module is used for generating an XML Schema constraint file according to the node instance.
Optionally, the node instance determining module includes:
the node attribute determining subunit is used for acquiring node attribute data input by a user;
and the node instance generating subunit is used for generating the corresponding node instance by using the node attribute data and the node data model.
Optionally, the node instance includes: a first node, at least one second node and at least three third nodes.
Alternatively to this, the first and second parts may,
the constraint file generation module is further used for generating a corresponding first node mark and a first node attribute mark according to the first node and the first node attribute; sequentially generating corresponding second node marks and second node attribute marks according to the second nodes and the second node attributes until all the second nodes are processed; determining third nodes and third node attributes corresponding to the second nodes and generating corresponding third node marks and third node attribute marks; and generating an XML Schema constraint file according to the generated first node mark and the first node attribute mark, the generated second node mark and the generated second node attribute mark, and the generated third node mark and the generated third node attribute mark.
The embodiment of the invention at least comprises the following advantages:
by implementing the method provided by the embodiment of the invention, the node data model is preset according to actual service requirements, the node instance is determined, and then the XML Schema file is generated according to the node instance, wherein the Schema file comprises a complete first node mark and a first node attribute mark, a complete second node mark and a complete second node attribute mark, and a complete third node mark and a complete third node attribute mark.
Drawings
Fig. 1 is a flowchart illustrating steps of a method for generating an XML Schema constraint file of a database according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating steps of a method for generating an XML Schema constraint file of a database according to a second embodiment of the present invention;
fig. 3 is a block diagram of a structure of an XML Schema constraint file generating device for a database according to an embodiment of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.
Referring to fig. 1, a flowchart illustrating steps of an embodiment of a method for generating an XML Schema constraint file of a database according to the present invention is shown, which may specifically include the following steps:
specifically, the node data model includes at least one of the following information: node name, node level, node number limit, node data type and node order.
It should be noted that, in implementing the present invention, the node data model can be defined in various ways, and for the convenience of understanding of those skilled in the art, an example of the node data model is given below by taking an object-oriented language as an example, and the node data model includes defined node properties and methods:
specifically, the node instance includes: a first node and a first node attribute, a second node and a second node attribute, and a third node attribute.
The first node is a root node, the second node is a child node of the first node, and the third node is a child node of the second node; the number of the first nodes is usually one, and the number of the second nodes and the third nodes can be determined according to actual needs. In an optional embodiment of the invention, the node instance comprises at least one second node and at least three third nodes.
And 103, generating an XML Schema constraint file according to the node instance.
Because the node and the corresponding node attributes, such as the node name, the node level, the node type and the like, are determined by the node instance, the XML Schema file can be generated according to the node instance.
In an optional embodiment of the present invention, the generating an XML constraint Schema file according to the node instance may specifically include the following sub-steps:
substep 1, generating a corresponding first node mark and a first node attribute mark according to the first node and the first node attribute;
step 2, generating corresponding second node marks and second node attribute marks in sequence according to the second nodes and the second node attributes until all the second nodes are processed;
substep 3, determining third nodes and third node attributes corresponding to the second nodes and generating corresponding third node marks and third node attribute marks;
and a substep 4, generating an XML Schema constraint file according to the generated first node mark and the first node attribute mark, the generated second node mark and the second node attribute mark, and the generated third node mark and the third node attribute mark.
The first node, the second node and the third node are arranged in a tree structure in the XML file, namely the first node is a root node, the second node is a child node of the first node, and the third node is a child node of the second node.
In specific implementation, a person skilled in the art may determine a specific implementation of the above steps according to different programming languages used, and the above steps are implemented by setting a Schmea file generation method GenerateSchema (), which may be implemented by:
suppose that the parameter xmlNodeInfo represents the node instance to be generated, and the parameter xmlSchemaFile represents the output XML Schemaconstraint file
Substep A, obtaining the information of a root node (a first node) of xmlNodeInfo;
substep B, obtaining all the second node information of xmlNodeInfo, and executing the following steps B1 to B3 for each second node:
sub-step B1, obtaining information of all third nodes corresponding to the current second node, and executing the following steps B11 to B12 for each of the third nodes:
sub-step B11, analyzing the attribute information of the current third node, wherein the attribute information comprises the attributes of node name, data type, quantity limitation, whether the third node is allowed to be empty, etc.;
substep B12, determining a third node flag and a third node attribute flag according to the analysis result;
specifically, the output file is set according to the format of the Schema constraint file, which is exemplified as follows:
sub-step B2, parsing the attribute information of the current second node, the attribute information including the node name, the number limit, whether it is allowed to be empty, etc.
Substep B3, determining the current second node label and the second node attribute label according to the analysis result;
specifically, this step further sets the second node information in the xml schema file based on the output result of sub-step B1.
A substep C of parsing the attribute information of the root node (first node), the attribute information including a node name, and determining a root node flag and a root node attribute flag according to the parsing result;
specifically, this step further sets the first node information in the xml schema file based on the output result of substep B3
And a substep D, outputting an XML Schema constraint file.
To sum up, in the method provided in the embodiment of the present invention, a node instance is determined according to a preset node data model and an actual service requirement, and then an XML Schema file is generated according to the node instance, where the Schema file includes a complete first node tag and a first node attribute tag, a second node tag and a second node attribute tag, and a third node tag and a third node attribute tag, and the XML Schema file can be used to perform constraint verification on the XML file, thereby avoiding problems of node duplication, attribute errors, and the like of the XML file caused by user misoperation and editing.
Referring to fig. 2, fig. 2 is a flowchart of a step of an application embodiment of a method for generating an XML Schema constraint file of a database according to an embodiment of the present invention, where it is assumed that constraints of a current XML file are as follows:
the root node is "Hosts";
the secondary node is 'Host', and the number of the secondary nodes is unlimited;
in each secondary node, three tertiary nodes are provided, namely 'HostID', 'Name' and 'ModeID';
the method comprises the following steps:
in an example of the pop-up window of the present invention, the user may add/delete the second node and the corresponding third node, and for each node, the user may directly set the attribute data of each node, including the node name, the node value type, whether the node is allowed to be empty, and the like, and after the setting is completed, the user may click the 'ok' button to obtain the node attribute data input by the user in the window.
It should be noted that, the above-mentioned obtaining of the node attribute data input by the user through the pop-up window is only a preferred mode of the present invention, and in a specific implementation, a person skilled in the art may also select another mode to obtain the node attribute data, which is not limited by the present invention, for example, through a web page, a touch operation, and the like.
and step 204, writing the third node information one by using a loop statement.
Specifically, each third node label (i.e., "HostID", "Name", and "ModeID") and corresponding node attribute label are included, including: node name, number limit, data type, whether allowed to be empty, etc.
and step 206, writing the second node information one by using a loop statement.
Specifically, each second node label (i.e., "Host") and corresponding attribute label are included, including: node name, number limit, data type, whether allowed to be empty, etc.
a first node label (i.e., root node Hosts ") and a first node attribute label are written.
In summary, in the above embodiment, the pop-up window is used to obtain the node attribute data input by the user, so that the user can set the node and the attribute of the XML data file in a what-you-see-is-what-you-get manner, which can further reduce the time required for generating the node instance and improve the efficiency of generating the Schema file.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.
Referring to fig. 3, a block diagram of a structure of an embodiment of an XML Schema constraint file generating device for a database according to the present invention is shown, which may specifically include the following modules: a data model determination module 310, a node instance determination module 320, and a constraint file generation module 330, wherein,
a data model determination module 310 for determining a node data model, the node data model comprising: node name, node level, node number limit, node data type, whether null is allowed or not and node sequence;
a node instance determining module 320, configured to determine a node instance according to the node data model, where the node instance includes: a first node and a first node attribute, a second node and a second node attribute, and a third node attribute; wherein the first node is a root node; the second node is a child node of the first node; the third node is a child node of the second node;
and the constraint file generating module 330 is configured to generate an XML Schema constraint file according to the node instance.
Optionally, the node instance determining module 320 includes:
the node attribute determining subunit is used for acquiring node attribute data input by a user;
and the node instance generating subunit is used for generating the corresponding node instance by using the node attribute data and the node data model.
Optionally, the node instance includes: a first node, at least one second node and at least three third nodes.
In an optional embodiment of the present invention, the constraint file generating module is further configured to generate a corresponding first node flag and a corresponding first node attribute flag according to the first node and the first node attribute; sequentially generating corresponding second node marks and second node attribute marks according to the second nodes and the second node attributes until all the second nodes are processed; determining third nodes and third node attributes corresponding to the second nodes and generating corresponding third node marks and third node attribute marks; and generating an XML Schema constraint file according to the generated first node mark and the first node attribute mark, the generated second node mark and the generated second node attribute mark, and the generated third node mark and the generated third node attribute mark.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The method and the device for generating the XML Schema constraint file of the database provided by the invention are introduced in detail, a specific example is applied in the text to explain the principle and the implementation mode of the invention, and the description of the embodiment is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (6)
1. A method for generating an XML Schema constraint file of a database is characterized by comprising the following steps:
determining a node data model, wherein the node data model comprises at least one of the following information: node name, node level, node number limit, node data type, whether null is allowed or not and node sequence;
determining a node instance according to the node data model, the node instance comprising: a first node and a first node attribute, a second node and a second node attribute, and a third node attribute; wherein the first node is a root node; the second node is a child node of the first node; the third node is a child node of the second node;
generating an XML Schema constraint file according to the node instance;
wherein the determining a node instance according to the node data model comprises:
acquiring node attribute data input by a user;
and generating a corresponding node instance by using the node attribute data and the node data model.
2. The method of claim 1, wherein the node instance comprises: a first node, at least one second node and at least three third nodes.
3. The method according to claim 1, wherein the generating an XML Schema constraint file according to the node instance comprises:
generating a corresponding first node mark and a first node attribute mark according to the first node and the first node attribute;
sequentially generating corresponding second node marks and second node attribute marks according to the second nodes and the second node attributes until all the second nodes are processed;
determining third nodes and third node attributes corresponding to the second nodes and generating corresponding third node marks and third node attribute marks;
and generating an XML Schema constraint file according to the generated first node mark and the first node attribute mark, the generated second node mark and the generated second node attribute mark, and the generated third node mark and the generated third node attribute mark.
4. An apparatus for generating an XML Schema constraint file of a database, comprising: a data model determination module, a node instance determination module, and a constraint file generation module, wherein,
a data model determination module for determining a node data model, the node data model comprising at least one of the following information: node name, node level, node number limit, node data type, whether null is allowed or not and node sequence;
a node instance determining module, configured to determine a node instance according to the node data model, where the node instance includes: a first node and a first node attribute, a second node and a second node attribute, and a third node attribute; wherein the first node is a root node; the second node is a child node of the first node; the third node is a child node of the second node;
a constraint file generation module, configured to generate an XML Schema constraint file according to the node instance;
the node instance determination module includes:
the node attribute determining subunit is used for acquiring node attribute data input by a user;
and the node instance generating subunit is used for generating the corresponding node instance by using the node attribute data and the node data model.
5. The apparatus of claim 4, wherein the node instance comprises: a first node, at least one second node and at least three third nodes.
6. The apparatus of claim 4,
the constraint file generation module is further used for generating a corresponding first node mark and a first node attribute mark according to the first node and the first node attribute; sequentially generating corresponding second node marks and second node attribute marks according to the second nodes and the second node attributes until all the second nodes are processed; determining third nodes and third node attributes corresponding to the second nodes and generating corresponding third node marks and third node attribute marks; and generating an XML Schema constraint file according to the generated first node mark and the first node attribute mark, the generated second node mark and the generated second node attribute mark, and the generated third node mark and the generated third node attribute mark.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610218128.4A CN107273386B (en) | 2016-04-08 | 2016-04-08 | XML Schema constraint file generation method and device for database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610218128.4A CN107273386B (en) | 2016-04-08 | 2016-04-08 | XML Schema constraint file generation method and device for database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107273386A CN107273386A (en) | 2017-10-20 |
| CN107273386B true CN107273386B (en) | 2020-04-28 |
Family
ID=60052939
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610218128.4A Active CN107273386B (en) | 2016-04-08 | 2016-04-08 | XML Schema constraint file generation method and device for database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107273386B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8055611B1 (en) * | 2008-03-31 | 2011-11-08 | Sonoa Networks India (PVT) Ltd. | Simplified XPath evaluation in XML document validation |
| CN104809111A (en) * | 2014-01-23 | 2015-07-29 | 北京北方微电子基地设备工艺研究中心有限责任公司 | Method, device and system for verifying validation of automatic system database file |
| CN106202149A (en) * | 2016-06-22 | 2016-12-07 | 南京南瑞继保电气有限公司 | A kind of IEC61850 model file conversion method |
-
2016
- 2016-04-08 CN CN201610218128.4A patent/CN107273386B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8055611B1 (en) * | 2008-03-31 | 2011-11-08 | Sonoa Networks India (PVT) Ltd. | Simplified XPath evaluation in XML document validation |
| CN104809111A (en) * | 2014-01-23 | 2015-07-29 | 北京北方微电子基地设备工艺研究中心有限责任公司 | Method, device and system for verifying validation of automatic system database file |
| CN106202149A (en) * | 2016-06-22 | 2016-12-07 | 南京南瑞继保电气有限公司 | A kind of IEC61850 model file conversion method |
Non-Patent Citations (2)
| Title |
|---|
| 基于SID XML Schema的资源命名管理系统设计与实现;张欢;《中国优秀硕士学位论文全文数据库 信息科技辑》;20110915;I138-455 * |
| 张欢.基于SID XML Schema的资源命名管理系统设计与实现.《中国优秀硕士学位论文全文数据库 信息科技辑》.2011, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107273386A (en) | 2017-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8176412B2 (en) | Generating formatted documents | |
| CN108762743B (en) | Data table operation code generation method and device | |
| CN107741935B (en) | Data importing method and data importing device | |
| US20130124969A1 (en) | Xml editor within a wysiwyg application | |
| CN112463135A (en) | Code generation method, code generator, electronic device, and storage medium | |
| CN110362792B (en) | Method and device for converting RN file into applet file and conversion equipment | |
| CN103136100A (en) | Method and system for Android test | |
| CN112231197A (en) | Page testing method and device and storage medium | |
| CN107273386B (en) | XML Schema constraint file generation method and device for database | |
| CN111078529A (en) | Client write-in module testing method and device and electronic equipment | |
| CN112114794B (en) | Automatic generation method and device of website application program and computer storage medium | |
| US9916315B2 (en) | Computer implemented system and method for comparing at least two visual programming language files | |
| CN110928540A (en) | Page generation method and device | |
| CN115033436A (en) | Page testing method and device, electronic equipment and storage medium | |
| JP2019028723A (en) | Design confirmation device and design confirmation method | |
| CN112307404A (en) | Document website setting method, device, equipment and medium based on source file | |
| CN114296726A (en) | Code generation method and device, computer equipment and storage medium | |
| CN109460236B (en) | Program version construction and checking method and system | |
| CN111507079A (en) | Multi-language document generation method, system and equipment | |
| Osis et al. | Using Use Cases for Domain Modeling. | |
| JP2012150740A (en) | Program generating device and method | |
| US11036932B2 (en) | Technology platform having integrated content creation features | |
| CN110162307B (en) | Method and device for converting JSON file into DLL file | |
| CN114282501A (en) | Method and device for creating table in document, electronic equipment and storage medium | |
| CN117215536A (en) | Interface code creation method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |