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": { ... } Here's the description of each attribute: Attribute Description type Type of the processor. producer Settings that affect how the data is extracted. See the full table of supported settings in . the

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": { ... } Here's the description of each attribute: Attribute Description type Type of the processor. producer Settings that affect how the data is extracted. See the full table of supported settings in . the

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": { ... } Here's the description of each attribute: Attribute Description type Type of the processor. producer Settings that affect how the data is extracted. See the full table of supported settings in . the

consists of JSON text, which looks like this: { "type": , "producer": { <producer settings> }, "consumer": { }, "processor": "type": "csv", "producer": { ... }, "consumer": { ... }, "processor": { ... } } Here's the description of each attribute: Attribute Description type Type of the processor. producer Settings that affect read per segment during data extraction. See extractType Integer 100000 Any Export Command Producer Settings DBeaver User Guide 22.1. Page 133 of 403. fetchSize Fetch size Number of rows to fetch

consists of JSON text, which looks like this: { "type": , "producer": { <producer settings> }, "consumer": { }, "processor": "type": "csv", "producer": { ... }, "consumer": { ... }, "processor": { ... } } Here's the description of each attribute: Attribute Description type Type of the processor. producer Settings that affect read per segment during data extraction. See extractType Integer 100000 Any Export Command Producer Settings DBeaver User Guide 22.2. Page 137 of 423. fetchSize Fetch size Number of rows to fetch

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": { ... } DBeaver User Guide 23.2. Page 215 of 700. Attribute Description type Type of the processor. producer Settings that affect how the data is extracted. See the full table of supported settings in

you close it. SQL Console DBeaver User Guide 23.3. Page 242 of 859. Overview Usage Settings Producer Settings Consumer Settings Processor Settings CSV DbUnit HTML JSON Markdown.table SQL Source 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 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": { ... }

Client side scripting DBeaver Lite User Guide 24.1. Page 654 of 1008. 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": { ... }

@set Client side scripting DBeaver User Guide 24.0. Page 664 of 1099. Overview Usage Settings Producer Settings Consumer Settings Processor Settings CSV DbUnit HTML JSON Markdown.table SQL Source 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": { ... }