core-lightning/doc/lightning-deldatastore.7.md

lightning-deldatastore -- Command for removing (plugin) data
============================================================

SYNOPSIS
--------

**deldatastore** *key* [*generation*]

DESCRIPTION
-----------

The **deldatastore** RPC command allows plugins to delete data it has
stored in the Core Lightning database.

The command fails if the *key* isn't present, or if *generation*
is specified and the generation of the data does not exactly match.

RETURN VALUE
------------

[comment]: # (GENERATE-FROM-SCHEMA-START)
On success, an object is returned, containing:
- **key** (array of strings):
  - Part of the key added to the datastore
- **generation** (u64, optional): The number of times this has been updated
- **hex** (hex, optional): The hex data which has removed from the datastore
- **string** (string, optional): The data as a string, if it's valid utf-8

[comment]: # (GENERATE-FROM-SCHEMA-END)

The following error codes may occur:
- 1200: the key does not exist
- 1201: the key does exist, but the generation is wrong
- -32602: invalid parameters

AUTHOR
------

Rusty Russell <<rusty@rustcorp.com.au>> is mainly responsible.

SEE ALSO
--------

lightning-listdatastore(7), lightning-datastore(7)

RESOURCES
---------

Main web site: <https://github.com/ElementsProject/lightning>

[comment]: # ( SHA256STAMP:83a7e89ed44c6dbf744d1327337e29393f9095628bd95fffe59ec5014ee0a483)
datastore: docs, schemas, and a test. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:50:12 +02:00			`lightning-deldatastore -- Command for removing (plugin) data`
			`============================================================`

			`SYNOPSIS`
			`--------`

Remove useless \ 2022-01-26 18:18:49 +01:00			`deldatastore key [generation]`
datastore: docs, schemas, and a test. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:50:12 +02:00
			`DESCRIPTION`
			`-----------`

			`The deldatastore RPC command allows plugins to delete data it has`
doc: update c-lightning to Core Lightning almost everywhere. Mostly comments and docs: some places are actually paths, which I have avoided changing. We may migrate them slowly, particularly when they're user-visible. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2022-04-06 07:09:48 +02:00			`stored in the Core Lightning database.`
datastore: docs, schemas, and a test. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:50:12 +02:00
datastore: add generation, simple atomicity. We add a generation counter, and allow update or del conditional on a given generation. Formalizes error codes, too, since we have more now. Suggested-by: @shesek Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:51:04 +02:00			`The command fails if the key isn't present, or if generation`
			`is specified and the generation of the data does not exactly match.`
datastore: docs, schemas, and a test. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:50:12 +02:00
			`RETURN VALUE`
			`------------`

			`[comment]: # (GENERATE-FROM-SCHEMA-START)`
			`On success, an object is returned, containing:`
datastore: turn keys into arrays After some discussion with @shesek, and my own usage, we agreed that a more comprehensive interface, which explicitly supports grouping, is desirable. Thus keys are now arrays, with the semantic that a key is either a parent or has a value, never both. For convenience in the JSON schema, we always return them as arrays, though we accept simple strings as arguments. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:51:34 +02:00			`- key (array of strings):`
			`- Part of the key added to the datastore`
			`- generation (u64, optional): The number of times this has been updated`
			`- hex (hex, optional): The hex data which has removed from the datastore`
datastore: allow strings. It's common, and the simplest case. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:50:13 +02:00			`- string (string, optional): The data as a string, if it's valid utf-8`
doc: fix GH/readthedocs rendering of manual pages. They render the comment as if it's in the list. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-09-03 12:07:59 +02:00
datastore: docs, schemas, and a test. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:50:12 +02:00			`[comment]: # (GENERATE-FROM-SCHEMA-END)`

			`The following error codes may occur:`
datastore: add generation, simple atomicity. We add a generation counter, and allow update or del conditional on a given generation. Formalizes error codes, too, since we have more now. Suggested-by: @shesek Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:51:04 +02:00			`- 1200: the key does not exist`
			`- 1201: the key does exist, but the generation is wrong`
			`- -32602: invalid parameters`
datastore: docs, schemas, and a test. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-08-25 04:50:12 +02:00
			`AUTHOR`
			`------`

			`Rusty Russell <<rusty@rustcorp.com.au>> is mainly responsible.`

			`SEE ALSO`
			`--------`

			`lightning-listdatastore(7), lightning-datastore(7)`

			`RESOURCES`
			`---------`

			`Main web site: <https://github.com/ElementsProject/lightning>`

make-schema: don't include tools/fromschema.py in SHASUMS We were including the entire list of prerequisites when generating a shastamp, which for schemas includes the `tools/fromschema.py` doc. This meant all of our shasums were updating anytime this tool file changed. Instead, we just include the first prerequisite. See: https://www.gnu.org/software/make/manual/html_node/Automatic-Variables.html#Automatic-Variables 2022-07-13 17:45:39 +02:00			`[comment]: # ( SHA256STAMP:83a7e89ed44c6dbf744d1327337e29393f9095628bd95fffe59ec5014ee0a483)`