Relational Data Management and Organization Using Dlt

2. A method as in claim 1, further comprising integrating the smart contract with the database on the distributed ledger whereby the smart contract executes data definition language (DDL) operations of the distributed ledger except for DDL database operations and schema changes.

3. A method as in claim 2, further comprising implementing database related operations of the database on the distributed ledger in chaincode, the chaincode defining at least one asset of the smart contract and at least one transaction instruction for modifying the at least one asset.

4. A method as in claim 3, wherein integrating the smart contract with the database on the distributed ledger comprises the smart contract calling the chaincode.

5. A method as in claim 3, further comprising the smart contract initiating data manipulation language (DML) read operations from the chaincode.

6. A method as in claim 1, wherein the relational database management query from the smart contract comprises a structured query language (SQL) query executed by the smart contract.

7. A method as in claim 6, further comprising parsing the SQL query into an SQL operation comprising one of an SQL data manipulation language (SQL DML) write operation, an SQL DML read operation, or an SQL data definition language (SQL DDL) operation, and creating a JavaScript Object Notation (JSON) representation of the SQL operation and any relational data included in the SQL operation.

8. A method as in claim 7, further comprising determining whether a distributed ledger transaction resulting from execution of the SQL operation has progressed toward acceptance into the distributed ledger to a platform-relevant extent.

9. A method as in claim 8, further comprising adding an operation broadcast status (OPSTAT) instruction at the end of a DML Write operation to fetch a more definitive status of a corresponding transaction.

10. A method as in claim 7, wherein executing the distributed ledger transaction on the distributed ledger comprises confirming that the smart contract has authority to perform the SQL operation.

11. A method as in claim 7, wherein executing the distributed ledger transaction on the distributed ledger comprises creating an SQL operation that may be processed and stored by the distributed ledger platform as a JSON representation of the SQL operation and its result.

12. A method as in claim 7, wherein the SQL operation is an SQL DML write operation, further comprising retrieving, using the at least one processor, data from the distributed ledger to execute the SQL DML write operation, executing, using the at least one processor, the SQL DML write operation including the retrieved data, preparing, using the at least one processor, JSON representations of any new or updated records in the transaction result, and committing, using the at least one processor, the SQL DML write operation and any updated records to the distributed ledger in a form that may be processed by the database on the distributed ledger for inclusion on the distributed ledger.

13. A method as in claim 12, further comprising monitoring, using the at least one processor, the distributed ledger for progress of the SQL DML write operation toward acceptance into the distributed ledger and informing, using the at least one processor, the smart contract whether the SQL DML write operation made such progress to a platform-relevant extent.

14. A method as in claim 7, wherein the SQL operation is an SQL DML read operation, further comprising retrieving, using the at least one processor, data from the distributed ledger to execute the SQL DML read operation, executing, using the at least one processor, the SQL DML read operation including the retrieved data, preparing, using the at least one processor, a JSON representation of the transaction result, and logging, using the at least one processor, the JSON representation of the transaction result to the distributed ledger in a form that may be processed by the database on the distributed ledger for inclusion on the distributed ledger.

15. A method as in claim 14, further comprising returning, using the at least one processor, the JSON representation of the transaction result to the smart contract.

16. A method as in claim 6, wherein the smart contract executes at least a subset of SQL queries of relational database management queries of the database on the distributed ledger.

17. A method as in claim 1, further comprising the smart contract performing at least one operation including executing data manipulation language (DML) queries, creating the database on the distributed ledger, updating access rights to the database on the distributed ledger, or executing data definition language (DDL) queries.

18. A method as in claim 17, wherein creating the database on the distributed ledger comprises the smart contract executing a configuration transaction that creates data segregation of the distributed ledger and defines which peer computers will maintain a copy of the database and executing a regular transaction that writes metadata about the database, further comprising creating, using the at least one processor, code defining transaction data on the distributed ledger and transaction instructions for modifying the transaction data.

20. A system as in claim 19, wherein the smart contract executes data definition language (DDL) operations of the distributed ledger except for DDL database operations and schema changes.

21. A system as in claim 20, wherein database related operations of the database are implemented on the distributed ledger in chaincode, the chaincode defining at least one asset of the smart contract and at least one transaction instruction for modifying the at least one asset.

22. A system as in claim 21, wherein the smart contract calls the chaincode for execution.

23. A system as in claim 22, wherein the smart contract executes at least a subset of SQL queries of relational database management queries of the database on the distributed ledger.

24. A system as in claim 21, wherein the smart contract initiates data manipulation language (DML) read operations from the chaincode.

25. A system as in claim 19, wherein the relational database management query from the smart contract comprises a structured query language (SQL) query executed by the smart contract.

26. A system as in claim 25, the at least one processor further executing instructions to perform operations comprising parsing the SQL query into an SQL operation comprising one of an SQL data manipulation language (SQL DML) write operation, an SQL DML read operation, or an SQL data definition language (SQL DDL) operation, and creating a JavaScript Object Notation (JSON) representation of the SQL operation and any relational data included in the SQL operation.

27. A system as in claim 26, the at least one processor further executing instructions to perform operations comprising determining whether a distributed ledger transaction resulting from execution of the SQL operation has progressed toward acceptance into the distributed ledger to a platform-relevant extent.

28. A system as in claim 27, the at least one processor further executing instructions to perform operations comprising adding an operation broadcast status (OPSTAT) instruction at the end of a DML Write operation to fetch a more definitive status of a corresponding transaction.

29. A system as in claim 26, wherein executing the distributed ledger transaction on the database on the distributed ledger comprises executing instructions to confirm that the smart contract has authority to perform the SQL operation.

30. A system as in claim 26, wherein executing the distributed ledger transaction on the database on the distributed ledger comprises executing instructions to create an SQL operation that may be processed and stored by the distributed ledger platform as a JSON representation of the SQL operation and its result.

31. A system as in claim 26, wherein the SQL operation is an SQL DML write operation, the at least one processor further executing instructions to perform operations comprising retrieving data from the distributed ledger to execute the SQL DML write operation, executing the SQL DML write operation including the retrieved data, preparing JSON representations of any new or updated records in the transaction result, and committing the SQL DML write operation and any updated records to the distributed ledger in a form that may be processed by the database on the distributed ledger for inclusion on the distributed ledger.

32. A system as in claim 31, the at least one processor further executing instructions to perform operations comprising monitoring the distributed ledger for progress of the SQL DML write operation toward acceptance into the distributed ledger and informing the smart contract whether the SQL DML write operation made such progress to a platform-relevant extent.

33. A system as in claim 26, wherein the SQL operation is an SQL DML read operation, the at least one processor further executing instructions to perform operations comprising retrieving data from the distributed ledger to execute the SQL DML read operation, executing the SQL DML read operation including the retrieved data, preparing a JSON representation of the transaction result, and logging the JSON representation of the transaction result to the distributed ledger in a form that may be processed by the database on the distributed ledger for inclusion on the distributed ledger.

34. A system as in claim 33, the at least one processor further executing instructions to perform operations comprising returning the JSON representation of the transaction result to the smart contract.

35. A system as in claim 19, wherein the smart contract performs at least one operation including executing data manipulation language (DML) queries, creating the database on the distributed ledger, updating access rights to the database on the distributed ledger, or executing data definition language (DDL) queries.

36. A system as in claim 35, wherein the smart contract creates the database on the distributed ledger by executing a configuration transaction that creates data segregation of the distributed ledger and defines which peer computers will maintain a copy of the database and executing a regular transaction that writes metadata about the database, the at least one processor further executing instructions to perform operations comprising creating code defining transaction data on the distributed ledger and transaction instructions for modifying the transaction data.