NL2011478C2 - Method and device for providing a first database request message in a first syntax. - Google Patents
Method and device for providing a first database request message in a first syntax. Download PDFInfo
- Publication number
- NL2011478C2 NL2011478C2 NL2011478A NL2011478A NL2011478C2 NL 2011478 C2 NL2011478 C2 NL 2011478C2 NL 2011478 A NL2011478 A NL 2011478A NL 2011478 A NL2011478 A NL 2011478A NL 2011478 C2 NL2011478 C2 NL 2011478C2
- Authority
- NL
- Netherlands
- Prior art keywords
- data
- database
- instruction
- syntax
- request message
- Prior art date
Links
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/245—Query processing
- G06F16/2452—Query translation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F16/972—Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Description
METHOD AND DEVICE FOR PROVIDING A FIRST DATABASE REQUEST MESSAGE IN A FIRST SYNTAX
TECHNICAL FIELD
The various aspects relate to generation and porting of instructions for processing requests related to data in multiple databases, which databases have different requirements on the format of the instructions.
BACKGROUND
Electronic database systems are in use for tens of years. In these years, the way database systems work and have been set up have evolved. The evolution has affected the way data is structured and the way operations to databases are instructed. However, databases already in use for longer periods have not all evolved yet and work still on legacy software. Because of the size of certain databases, like databases held by municipalities for registering data on their citizens, database transition is preferably executed in a step-by-step process. During such process, the legacy database needs to remain accessible and a new database using new software should be addressable as well. The legacy database and the new database may require, at least for certain cases, instructions to be issued in different formats and with different data, whereas they may be required to be instructed from one system that may not be aware whether the instruction is to a legacy database or to a new database.
SUMMARY
It is preferred to provide instructions for database operations that can be efficiently and conveniently be translated to instruction to either the new database or the legacy database. A first aspect provides a method of providing a first database request message in a first syntax. The method comprises receiving a database process instruction, generating a first instruction data field in the first syntax based on the database process instruction, the first plurality of instruction data fields forming a first data structure being compliant with first system requirements, determining input control data related to the database process instruction, the input control data being compatible with second system requirements of a second system, generating at least one first input control data field comprising the input control data, the input control data field being in the first syntax and generating the first database request message comprising the first instruction data field and the input control data field.
By providing a message comprising the instructions directly in a format in accordance with the first system requirements and comprising control data in accordance with the second requirements, the message comprises data in accordance with the first system requirements and the second system requirements. Hence, the message can be, to an extent required, conveniently be amended to further messages fully compliant with the first system requirements or the second system requirements. This allows one single instruction message to be generated for addressing a database, without further knowledge of system requirements of a specific database the instruction message will later on be relayed to.
More practical, the first system requirements may relate to a new database system and the second system requirements may relate to a legacy database system. In such scenario, the first instruction data field in the first syntax based on the database process instruction, the first plurality of instruction data fields forming the first data structure may be split from the first database request message and sent to the new system - a rather simple operation. For the second system, the legacy system, a more complex operation like a translation may be required. This makes the method well suitable for future use, as the burden to adapt instructions to requirements for the new system is the lowest.
An embodiment of the first aspect further comprises porting the first database request message to a second database request message. The comprises translating data comprised by the first instruction data field from the first syntax to a second syntax required by the second system requirements, translating data comprised by the first input control data field from the first syntax to the second syntax; and generating a second database request message comprising the translated data comprised by the first instruction data field and the translated data comprised by the first input control data field, the second database request message being compliant with second system requirements of the second system.
This embodiment yields a database request message that is compliant with the second system requirements and may hence be used for sending instructions to the second system. A second aspect relates to a computer programme product for loading in a computer and causing the computer, when executed by the computer, to execute the method according to the first aspect. A third aspect relates to a device for providing a first database request message in a first syntax, the device comprising an input module arranged to receive a database process instruction and a processing unit. The processing unit is arranged to generate a first instruction data field in the first syntax based on the database process instruction, the first plurality of instruction data fields forming a first data structure being compliant with first system requirements, determine input control data related to the database process instruction, the input control data being compatible with second system requirements of a second system, generate at least one first input control data field comprising the input control data, the input control data field being in the first syntax; and generate the first database request message comprising the first instruction data field and the input control data field. The device further comprises an output unit for providing the first database request message to another device. A fourth aspect relates to a method for porting a first database request message provided in a first syntax to a second database request message in a second syntax, the first database message. The first database message comprises at least a first instruction data field forming a first data structure being compliant with first system requirements and at least a first input control data field comprising input control data. The porting comprises translating data comprised by the first instruction data field from the first syntax to a second syntax required by second system requirements, translating data comprised by first input control data field from the first syntax to the second syntax; and generating a second database request message comprising the translated data comprised by the first instruction data field and the translated data comprised by the first input control data field, the second database request message being compliant with second system requirements of the second system. A fifth aspect relates to a computer programme product for loading in a computer and causing the computer, when executed by the computer, to execute the method according to the fourth aspect. A sixth aspect relates to a porting device for porting a first database request message provided in a first syntax to a second database request message in a second syntax, the first database message comprising at least one first instruction data field forming a first data structure being compliant with first system requirements; and at least one first input control data field comprising input control data. The device comprises an input unit arranged to receive the first database request message and a processing unit. The processing unit is arranged to translate data comprised by the first instruction data field from the first syntax to a second syntax required by the second system requirements; translate data comprised by a first input control data field from the first syntax to the second syntax; and generate a second database request message comprising the translated data comprised by the first instruction data field and the translated data comprised by the first input control data field, the second database request message being compliant with second system requirements of the second system. The porting device further comprises an output unit for providing the second database request message to a further device.
BRIEF DESCRIPTION OF THE DRAWINGS
The various aspects and embodiments thereof will now be discussed in further details in conjunction with Figures. In the Figures,
Figure 1: shows a networked data processing system;
Figure 2: shows a first flowchart;
Figure 3: shows a second flowchart;
Figure 4: shows a third flowchart; and
Figure 5: shows a fourth flowchart.
DETAILED DESCRIPTION
Figure 1 shows a networked data processing system 100. The networked data processing system 100 comprises a first private cloud network 102 and a second private cloud network 104.
The first private cloud network 102 comprises an instruction processing server 110 and a first service bus 130. The second private cloud network 104 comprises a second service bus 140 and a first database server 160.
The networked data processing system 100 further comprises a set of user terminals 108 connected to the instruction processing server 110 over a public wide area network 106 and a second database server 180 connected to the second service bus 140.
The second database server 180 may be connected to the second service bus 140 over the public wide area network 106, either transparently or via a virtual private network, or via another type of network. The second database server 180 comprises a communication module 182 for communicating with the second service bus 140. The second database server also comprises a processing unit 184 for processing data received from the second service bus 140 and executing instructions that may be comprised by data received. Such instructions may be database queries to be processed on a database stored by a storage module 186 comprised by the second database server 180. The processing unit 184 is also arranged to receive results from queries and have them send to the second service bus via the communication module 182.
The networked data processing system 100 is arranged to enable users of the user terminals 108 to manage data related to the users that is stored in the first database server 160 and the second database server 180. The managing of the data comprises issuing instructions for queries for data stored in the first database server 160 and for updating data stored in the first database server 160. The managing of data is handled by means of instruction messages that are relayed to the first database server 160 via the instruction processing server 110, the first service bus 130 and the second service bus 140.
In one particular embodiment, the instruction processing server 110 and the first service bus 130 are managed by a first party, the second service bus 140 and the first database server 160 are being handled by a second party and the second database server 180 by a third party. The instruction processing server 110, the first service bus 130 and the second service bus 140 are primarily arranged for relaying instruction messages to the second database server 180 in a first syntax. These instructions for the second database server 180 have a first data structure type. Hence, messages sent from the second service bus 130 to the second database server 180 are in the first syntax and have the first data structure type. Transmission paths carrying this data type are in Figure 1 indicated by a capital letter C as reference sign.
The instruction processing server 110 and the first service bus 130 are also required to relay instruction messages to the first database server 160 which requires instructions being provided in a second syntax and a second data structure type. Hence, messages sent from the second service bus 130 to the first database server 160 are in the second syntax and have the second data structure type. Transmission paths carrying this data type are in Figure 1 indicated by a capital letter B as reference sign.
The first data structure type in the first syntax required for messages with instructions to be executed by the second database server 180 is not directly compatible with a second data structure type in the second syntax required for messages for the first database server 160. Therefore, the instruction processing server 110 is arranged for providing messages in a third data structure type that can be conveniently transformed to a message with the first data structure type in the first syntax and to a message with the second data structure type in the second syntax.
Generation of messages with the third data structure type and transformation thereof to messages with the first data structure type in the first syntax and to messages with the second data structure type in the second syntax will be discussed below in conjunction with Figure 1, Figure 2 showing a first flowchart 200, Figure 3 showing a second flowchart 300, Figure 4 showing a third flowchart and Figure 5 showing a fourth flowchart.
Users of the user terminals 108 are provided with an interface on the screens of the user terminals 108 to enable the users to issue instructions for managing data related to them. The terminal 108 may be personal computers, tablet computers, smart phones, other, or a combination thereof. The instructions relate in one embodiment to querying data or to updating of data. Updating of data may for example relate to a change of an address of the user. The user interface is provided by the instruction processing server 110 and is preferably provided as a so-called web interface by means of a PHP (Hypertext Preprocessor) script, html (hypertext mark-up language), other means of a combination thereof.
Data entered by the users is sent to the instruction processing server 110 in a proprietary format via the public wide area network 106 and received by a public network transceiver module 112. The public network transceiver module 112 is connected to an instruction processing unit 120 for processing of data in the proprietary format and transforming the data to one or more instruction messages in the third data structure type. The third data structure type is preferably provided in the first syntax. The process of transforming the data to one or more instruction messages in the third data structure type will be discussed in further detail in conjunction with Figure 1 and Figure 2. Figure 2 shows the first flowchart 200 with items of which a summary is provided in the table below:
No. 202 Start process; receive instruction 204 Determine instruction type 206 Query or update instruction? 212 Generate query instruction data 214 Generate control data for query instruction 216 Generate compound query message 222 Generate update instruction 224 Generate control data for update instruction 226 Generate compound update message 232 Send compound instruction message 234 End process
The process starts at a terminator 202, by receiving a user instruction from the user terminal 108. Subsequently, in step 204, a determination sub-module 122 of the instruction processing unit 120 determines what type the received user instruction is. As discussed before, the user instruction may relate to a query request or an update request.
After the determination, the process branches in a decision 206 to step 212 if the user instruction relates to a query instruction. In step 212, an instruction data generation sub-module 124 generates query instruction data in the first syntax, which in this embodiment is XML (Extensible Markup Language). The query instruction data is preferably provided in the first data structure type. The query instruction data may comprise a mask for types of items to be searched and/or search terms for a query to be executed. The search terms may be specified as related to a specific category, like surname or address.
After step 212, the process continues to step 214, in which a control data generation sub-module 126 generates query control data for the query instruction message. The control data is provided in the first syntax as well. Query control data may comprise a communication identifier, an organisation identifier, a function code, other or a combination thereof.
Subsequently, in step 216, an instruction message sub-module 128 generates the query instruction message with the third data structure type. This is done by inserting the query control data generated in step 214 in the query instruction data generated in step 212, thus creating a compound query instruction message. This means in this embodiment that the third data structure type is generated by adding control data to the query instruction data provided in the first data structure type.
The compound query instruction message is subsequently sent to the first service bus 130 via the first service bus transceiver module 118 in step 232, upon which the process ends in a terminator 234.
After the determination, the process branches in a decision 206 to step 222 if the user instruction relates to an update instruction. In step 222, the instruction data generation sub-module 124 generates update instruction data in the first syntax, which in this embodiment is XML (Extensible Markup Language). The update instruction data is preferably provided in the first data structure type. The update instruction data may comprise an identifier to an item or person to which the update request relates and one or more characteristics of the user or item for which update is instructed.
After step 222, the process continues to step 224, in which a control data generation sub-module 126 generates update control data for the update instruction message. The control data is provided in the first syntax as well. Control data may comprise a communication identifier, an organisation identifier, a function code, other or a combination thereof.
Subsequently, in step 226, an instruction message sub-module 128 generates the update instruction message with the third data structure type. This is done by inserting the update control data generated in step 224 in the update instruction data generated in step 222, thus creating a compound update instruction message. This means in this embodiment that the third data structure type is generated by adding control data to the instruction data provided in the first data structure type.
The compound update instruction message is subsequently sent to the first service bus 130 via the first service bus transceiver module 118 in step 232. Hence, messages sent from the instruction processing server 110 to the first service bus 130 are in the first syntax and have the third data structure type. Transmission paths carrying this data type are in Figure 1 indicated by a capital letter A as reference sign. After the sending step, the process ends in a terminator 234.
Hence, the compound query instruction message and the compound update instruction message are generated in similar ways and use the same syntax. However, as different items are required for the query instruction data and for the update instruction data, two branches may be provided in the process of generating the compound instruction messages.
The instruction processing server 110 comprises a memory module 116 arranged for storing computer code causing the instruction processing unit 120 to execute the process as outlined above. Such computer code may create various sub-modules as programmed parts of the instruction processing unit 120.
The compound instruction messages, query instruction messages as well as well as update instruction messages, are received by the first service bus 130 by means of an instruction server transceiver 132 and subsequently provided to the second service bus 140 via a first cloud transceiver 138. Intermediate processing by the first service bus processing unit 134 and storage in the first service bus storage module 136 may be performed, but is not required. Such processing may be encryption as the compound instruction messages may be sent to the second service bus 140 over a public network and data security may be required in such scenario. Furthermore, the first service bus 130 may provide further security features like acting as a firewall for protection of the instruction processing server 110.
The second service bus 140 may provide similar and reciprocal functionality, i.e. decryption of data and acting as a firewall for protection of the first database server 160. And the second service bus 140 is arranged for translation of the compound instruction messages for processing by the first database server 160 and the second database server 180. The first transformation will be discussed first in conjunction with Figure 1 and Figure 3 depicting a second flowchart 300. Items of the second flowchart 3 are depicted below.
No. 302 Start process; receive compound instruction message 304 Determine instruction type of compound instruction message 306 Query or update instruction? 312 Translate query instruction data to second syntax 314 Translate query control data to second syntax 316 Generate query instruction message for first database server 322 Translate update instruction data to second syntax 324 Translate update control data to second syntax 326 Generate update instruction message for first database server 332 Send translated message 334 End process
In a terminator 302, the compound message is received by the second service bus 140 by means of a second cloud transceiver 142. In step 304, the instruction type of the compound instruction message is determined. For the embodiments discussed here, such instruction type may be a query type or an update type. The data structure types for both types of compound instruction messages are the same, but the actual data structures of both types of compound message are different.
Also the output of the process depicted by the second flowchart 300 is different depending on the type of the compound instruction message. The output of the process is a translated instruction message. The translated instruction message has the second data structure type and is provided in the syntax for query and update instructions, as discussed before, but a translated query instruction message has a different data structure than a translated update instruction message.
After the determination, the process branches in a decision 306 to step 312 if the compound instruction message relates to a query instruction. In step 312, an instruction data translation sub-unit 152 of a second service bus processing unit 150 translates query instruction data of the compound instruction message in the first syntax to the second syntax. In step 314, a control data translation sub-unit 154 of the second service bus processing unit 150 translates query control data of the compound instruction message in the first syntax to the second syntax. As the second data structure type requires both instruction data and control data, the compound instruction message may also be translated in one go. The second syntax is in the embodiments discussed here a COBOL copymember syntax.
Subsequently, in step 316, the translated query instruction message is formed by a translated messages generation sub-unit 156 of the second service bus processing unit 150, in the second syntax. As the second data structure type requires both instruction data and control data, the compound instruction message may also be translated in one go, directly creating the translated query instruction message.
The translated query instruction message thus created is provided to the first database server 160 via a translated instruction transceiver 148 in step 332.
After the determination, the process branches in a decision 306 to step 322 if the compound instruction message relates to an update instruction. In step 322, an instruction data translation sub-unit 152 of a second service bus processing unit 150 translates update instruction data of the compound instruction message in the first syntax to the second syntax. In step 324, a control data translation sub-unit 154 of the second service bus processing unit 150 translates update control data of the compound instruction message in the first syntax to the second syntax. As the second data structure type requires both instruction data and control data, the compound instruction message may also be translated in one go.
Subsequently, in step 326, the translated update instruction message is formed by a translated messages generation sub-unit 156 of the second service bus processing unit 150, in the second syntax. As the second data structure type requires both instruction data and control data, the compound instruction message may also be translated in one go, directly creating the translated update instruction message.
The translated update instruction message thus created is provided to the first database server 160 via a translated instruction transceiver 148 in step 332 and the process ends in a terminator 334.
In the database server 160, the translated instruction message is received by the first database transceiver 162. If the translated instruction message relates to a query instruction, the query instruction is executed by a query processing unit 164 on data stored by the database storage module 168. If the translated instruction message relates to an update instruction, the update instruction is executed by an update processing unit 166 on data stored by the database storage module 168. Alternatively, query instructions and update instructions are handled by one and the same processing unit.
The second service bus 140 comprises a memory module 146 arranged for storing computer code causing the second service bus processing unit 150 to execute the process as outlined above. Such computer code may create various sub-modules as programmed parts of the second service bus processing unit 150.
The execution of the instructions yields responses comprising data. The database server 160, using COBOL copymembers as second data structure types, yields, in response to processing instruction messages, response messages having the same data structure as the instruction messages. This means the instruction messages comprise fields for result data and the response messages comprise fields for instruction data. But the fields for result data of the instruction messages do not comprise relevant data and the fields for instruction data of the response messages do not comprise relevant data. Alternatively or additionally, data in the fields for result data of the instruction messages and data in the fields for instruction data of the response messages is not processed in any particular way.
The database storage module 168 is also arranged for storing computer code causing the query processing unit 164 and the update processing unit 166 to execute the process as outlined above. Alternatively or additionally, the first database transceiver 162 may be programmed for executing certain parts of the process.
The response messages of the first database server 160, of the second data structure type and in the second syntax, are handed back to the second service bus 140 via the first database transceiver 162 and the translated instruction transceiver 148 to the second service bus processing unit 150. The response messages in the second data structure type and in the second syntax are subsequently translated to the third data structure type in the first syntax. This will be discussed in further detail in conjunction with Figure 1 and Figure 4, the latter depicting a third flowchart 400. Items of the third flowchart 4 are depicted below.
No. 402 Start process; receive output message 404 Determine instruction type of the output message 406 Query or update response? 412 Translate query result data to first syntax 414 Translate query output control data to first syntax 416 Generate compound query response message in third data structure type 422 Translate update output data to first syntax 424 Translate update control data to first syntax 426 Generate compound update response message in third data structure type 432 Send translated message 434 End process
The process starts in a terminator 402 by receiving an output message from the first database server 160. As discussed, the data structure of the output message is the same as the data structure of the instruction message the output message is a response to.
Subsequently, in step 404, the type of instruction related to the output message relates to is determined. This option is advantageous as it helps determining the structure of a message the output message in the second syntax is translated to. This may make the translation process more efficient.
After the determination, the process branches in a decision 406 to step 412 if the output message relates to a query instruction. In step 412, query result data resulting out of the query instruction applied to the database is translated from the second syntax to the first syntax and from the second data structure type to the first data structure type. Subsequently, in step 414, query output control data resulting out of the query instruction applied to the database is translated from the second syntax to the first syntax. The query output control data is preferably the same as the query control data in the compound query instruction message.
For these translations, the instruction data translation sub-unit 152 and the control data translation sub-unit 154 of the second service bus processing unit 150 may be used.
In step 416, a compound query response message in third data structure type is generated by inserting the query output control data in the first syntax to the translated query result data provided in the first syntax and the first data structure type. For this operation, the translated messages generation sub-unit 156 may be used. Alternatively, query response messages with the second data structure type are translated directly to the third data structure type, executing three steps in one operation.
After the determination, the process branches in a decision 406 to step 422 if the output message relates to an update instruction. In step 422, update result data resulting out of the update instruction applied to the database is translated from the second syntax to the first syntax and from the second data structure type to the first data structure type. Subsequently, in step 424, update output control data out of the update instruction applied to the database is translated from the second syntax to the first syntax. For these translations, the instruction data translation sub-unit 152 and the control data translation sub-unit 154 of the second service bus processing unit 150 may be used.
In step 426, a compound update response message in third data structure type is generated by inserting the update output control data in the first syntax to the translated update result data provided in the first syntax and the first data structure type. For this operation, the translated messages generation sub-unit 156 may be used. Alternatively, update response messages with the second data structure type are translated directly to the third data structure type, executing three steps in one operation.
The compound response message thus generated is subsequently sent to the first service bus 130 in step 432, upon which the process executed by the second service bus 140 ends in a terminator 434. In a subsequent process, the data in the compound response message may be further relayed to users of the user terminals 108 via the various intermediate modules.
The second service bus 140 comprises a memory module 146 arranged for storing computer code causing the second service bus processing unit 150 to execute the process as outlined above. Such computer code may create various sub-modules as programmed parts of the second service bus processing unit 150.
As discussed above, the first data structure type in the first syntax required for messages for the second database server 180 is not directly compatible with the second data structure type in the second syntax required for messages for the first database server 160. Therefore, the instruction processing server 110 is arranged for provide messages in a third data structure type that can be conveniently transformed to a message with the first data structure type in the first syntax and to a message with the second data structure type in the second syntax. This transformation process will be discussed in conjunction with a fourth flowchart 500 provided by Figure 5. Items of the fourth flowchart 500 are depicted below.
No. 502 Start process; receive compound instruction message 504 Determine destination database server 506 First or second database server? 512 Proceed to first flowchart 200 522 Remove control data 524 Send instruction message to second database server 180 526 End
The process starts in a terminator 502 with the second service bus processing unit 150 receiving a compound instruction message from the first instruction bus 130. The compound instruction message is provided in the third data structure type and the first syntax. In step 504, a destination for the compound instruction message is determined. The destination for the compound instruction message is either the first database server 160 or the second database server 180. Each of these database servers requires a different data structure type of messages to be processed.
After determination, the process branches in a decision 502 to connector 512 if the destination of an instruction in the compound instruction message is the first database server 160. The connector 512 redirects the process to the first flowchart 200 for further processing of the compound instruction message in accordance with the flowchart.
If the destination of an instruction in the compound instruction message is the second database server 180, the process branches in the decision 502 to step 522. In step 322, the control data is removed from the compound instruction message. In this way the compound instruction message provided in the third data structure type is transformed to an instruction message in the first data structure type. As discussed above, this first data structure type is required by the second database server 180 for receiving instructions to be executed.
After data structure type transformation, the instruction message is sent to the second database server 180 in step 524 and the process ends in terminator 526.
Expressions such as "comprise", "include", "incorporate", "contain", "is" and "have" are to be construed in a non-exclusive manner when interpreting the description and its associated claims, namely construed to allow for other items or components which are not explicitly defined also to be present. Reference to the singular is also to be construed in be a reference to the plural and vice versa.
In the description above, it will be understood that when an element such as layer, region or substrate is referred to as being "on", "onto" or "connected to" another element, the element is either directly on or connected to the other element, or intervening elements may also be present.
Furthermore, the invention may also be embodied with less components than provided in the embodiments described here, wherein one component carries out multiple functions. Just as well may the invention be embodied using more elements than depicted in the Figures, wherein functions carried out by one component in the embodiment provided are distributed over multiple components. A person skilled in the art will readily appreciate that various parameters disclosed in the description may be modified and that various embodiments disclosed and/or claimed may be combined without departing from the scope of the invention.
It is stipulated that the reference signs in the claims do not limit the scope of the claims, but are merely inserted to enhance the legibility of the claims.
Claims (16)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
NL2011478A NL2011478C2 (en) | 2013-09-20 | 2013-09-20 | Method and device for providing a first database request message in a first syntax. |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
NL2011478A NL2011478C2 (en) | 2013-09-20 | 2013-09-20 | Method and device for providing a first database request message in a first syntax. |
NL2011478 | 2013-09-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
NL2011478C2 true NL2011478C2 (en) | 2015-03-23 |
Family
ID=50001209
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
NL2011478A NL2011478C2 (en) | 2013-09-20 | 2013-09-20 | Method and device for providing a first database request message in a first syntax. |
Country Status (1)
Country | Link |
---|---|
NL (1) | NL2011478C2 (en) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030061205A1 (en) * | 2001-09-27 | 2003-03-27 | Cleghorn Monica Rose | System and method for processing database queries |
US20050262157A1 (en) * | 2004-05-19 | 2005-11-24 | Vanyo Tadd E | Interface cool ice OLEDB consumer interface |
US20060004726A1 (en) * | 2004-06-16 | 2006-01-05 | Michael Blank | System for processing a data request and related methods |
-
2013
- 2013-09-20 NL NL2011478A patent/NL2011478C2/en not_active IP Right Cessation
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030061205A1 (en) * | 2001-09-27 | 2003-03-27 | Cleghorn Monica Rose | System and method for processing database queries |
US20050262157A1 (en) * | 2004-05-19 | 2005-11-24 | Vanyo Tadd E | Interface cool ice OLEDB consumer interface |
US20060004726A1 (en) * | 2004-06-16 | 2006-01-05 | Michael Blank | System for processing a data request and related methods |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110535831B (en) | Kubernetes and network domain-based cluster security management method and device and storage medium | |
CN108279932B (en) | Method and device for dynamically configuring user interface of mobile terminal | |
CN102497454B (en) | Method for realizing gray publication of application in application service platform system | |
CN107809383B (en) | MVC-based path mapping method and device | |
CN106406844B (en) | Method and device for realizing public number menu of communication interaction platform | |
US8966446B1 (en) | Systems and methods of live experimentation on content provided by a web site | |
US20090177778A1 (en) | Session Affinity Cache and Manager | |
CN106202547B (en) | Site management method and device and website system | |
CN110830374B (en) | Method and device for gray level release based on SDK | |
CN104583945B (en) | A kind of application upgrade method, apparatus | |
CN112217656B (en) | Method and device for synchronizing configuration information of network equipment in SD-WAN (secure digital-to-Wide area network) system | |
CN111580820A (en) | Applet generation method and device | |
CN106663013A (en) | Dynamic pacing for service upgrades | |
CN110324169A (en) | A kind of method and apparatus of interface management | |
CN103729189B (en) | Broadcasting method for converting protocol based on LUA, system, terminal | |
CN102314469A (en) | Method for implementing cross-domain request callback | |
CN107800781A (en) | A kind of configuration data processing method and device | |
CN103973682A (en) | Method and device for having access to webpage | |
CN106357521A (en) | Data sharing method and device | |
CN101512523A (en) | System and method for dynamic context-sensitive integration of content into a web portal application | |
CN109936605A (en) | A kind of method and apparatus of loading interface data | |
CN110941779A (en) | Page loading method and device, storage medium and electronic equipment | |
CN107992350B (en) | Method and device for generating configuration overview page | |
CN103957234A (en) | Method for sending download files in browser and browser device | |
CN109284452A (en) | The online methods of exhibiting of electronic protocol, device, electronic equipment, storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
MM | Lapsed because of non-payment of the annual fee |
Effective date: 20201001 |