mirror of
https://github.com/corda/corda.git
synced 2025-01-29 15:43:55 +00:00
Moves vault API information into the API section.
This commit is contained in:
parent
791af7db53
commit
575acd2983
@ -6,8 +6,9 @@ This section describes the APIs that are available for the development of CorDap
|
||||
* :doc:`api-states`
|
||||
* :doc:`api-persistence`
|
||||
* :doc:`api-contracts`
|
||||
* :doc:`api-vault`
|
||||
* :doc:`api-transactions`
|
||||
* :doc:`api-flows`
|
||||
* :doc:`api-core-types`
|
||||
|
||||
Before reading this page, you should be familiar with the key concepts of Corda: :doc:`key-concepts`.
|
||||
Before reading this page, you should be familiar with the :doc:`key concepts of Corda <key-concepts>`.
|
@ -1,5 +1,5 @@
|
||||
Vault Query
|
||||
===========
|
||||
API: Vault
|
||||
==========
|
||||
|
||||
Corda has been architected from the ground up to encourage usage of industry standard, proven query frameworks and libraries for accessing RDBMS backed transactional stores (including the Vault).
|
||||
|
@ -46,7 +46,7 @@ Note the following:
|
||||
* the vault performs fungible state spending (and in future, fungible state optimisation management including merging, splitting and re-issuance)
|
||||
* vault extensions represent additional custom plugin code a developer may write to query specific custom contract state attributes.
|
||||
* customer "Off Ledger" (private store) represents internal organisational data that may be joined with the vault data to perform additional reporting or processing
|
||||
* a :doc:`vault-query` API is exposed to developers using standard Corda RPC and CorDapp plugin mechanisms
|
||||
* a :doc:`vault query API <api-vault>` is exposed to developers using standard Corda RPC and CorDapp plugin mechanisms
|
||||
* a vault update API is internally used by transaction recording flows.
|
||||
* the vault database schemas are directly accessible via JDBC for customer joins and queries
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user