<request type="DELETE_LEDGER_HISTORY" desc="Delete Ledger Update History">
<parameters>
<parameter name="APPLICATION" value="SAMPLE1"/> (1)
<parameter name="LEDGER_EDITION" value="PUBLIC"/> (2)
</parameters>
<contents> (3)
</contents>
</request>Deleting Ledger Update History
This manual is in pilot operation.
|
Overview
Ledger data in the fusion_place database is managed by generation. Each time the ledger data is updated, a new generation is added. As the number of generations increases, the database file size also grows.
This function aggregates ledger line data by generation in the specified edition into the latest generation and deletes the older generations. While this does not immediately reduce the database file size, running the "Sweeping Garbage" process afterward will free up space within the database and make it reusable.
Only users with Designer or Administrator privileges can execute this request.
How to Write a Request
Below is an example request for "Deleting Ledger Update History":
| 1 | "Application" parameter |
| 2 | "Ledger Edition" parameter |
| 3 | Request Content |
Parameters
Specify the target application and the target ledger edition.
| Parameter | Required | Key | Description |
|---|---|---|---|
APPLICATION |
Yes |
None |
Specify the label of the target application. |
LEDGER_EDITION |
Yes |
None |
Specify the "ledger edition key" of the target ledger edition. Reserved ledger keys are as follows: PUBLIC : Public Edition |
Response Content
Below is an example response for "Deleting Ledger Update History":
<response type="DELETE_LEDGER_HISTORY" desc="Delete Ledger Update History">
<returned-contents> (1)
</returned-contents>
<result>
<code>SUCCESSFUL</code> (2)
<started-at time-zone="Asia/Tokyo">2015/02/28 09:50:04.227</started-at>
<ended-at time-zone="Asia/Tokyo">2015/02/28 09:50:07.827</ended-at>
<messages>
... (3)
</messages>
</result>
</response>| 1 | Returned Content |
| 2 | Processing Result Code |
| 3 | Message |
