Client side scripting DBeaver Lite User Guide 24.2.ea. Page 655 of 1010. Overview Usage Settings Producer Settings Consumer Settings Processor Settings CSV processor DbUnit processor HTML processor consists of JSON text, which looks like this: { "type": , "producer": { <producer settings> }, "consumer": { }, "processor": "type": "csv", "producer": { ... }, "consumer": { ... }, "processor": { ... } } The command itself doesn't do anything. It must be followed by any other query: @export { "type": "csv", "producer": { ... }

side scripting DBeaver Ultimate User Guide 24.2.ea. Page 704 of 1171. Overview Usage Settings Producer Settings Consumer Settings Processor Settings CSV processor DbUnit processor HTML processor consists of JSON text, which looks like this: { "type": , "producer": { <producer settings> }, "consumer": { }, "processor": "type": "csv", "producer": { ... }, "consumer": { ... }, "processor": { ... } } The command itself doesn't do anything. It must be followed by any other query: @export { "type": "csv", "producer": { ... }

Client side scripting DBeaver User Guide 24.2.ea. Page 704 of 1171. Overview Usage Settings Producer Settings Consumer Settings Processor Settings CSV processor DbUnit processor HTML processor consists of JSON text, which looks like this: { "type": , "producer": { <producer settings> }, "consumer": { }, "processor": "type": "csv", "producer": { ... }, "consumer": { ... }, "processor": { ... } } The command itself doesn't do anything. It must be followed by any other query: @export { "type": "csv", "producer": { ... }