Unexpected token when export data

[RedBlob]

Hello,

Using the "Export data" function, an error message appears referring to the JSON at position 1

In position 1 seems to be the primary key of the PostgreSQL table, which, however, has been working correctly for months without any problems ( it is an integer variable that is correctly operational ).

What could be the problem ?

Thank You for help

[melohagan]

Hey @RedBlob

Could you please share the schema of your SQL table (the table CREATE script).

[RedBlob]

Hi @melohagan

This is the SQL for primary Key sequence :

CREATE SEQUENCE IF NOT EXISTS public.id_flux_seq
INCREMENT 1
START 1
MINVALUE 1
MAXVALUE 9223372036854775807
CACHE 1;

ALTER SEQUENCE public.id_flux_seq
OWNER TO postgres;

GRANT ALL ON SEQUENCE public.id_flux_seq TO redblob;

And this is the SQL for table :

CREATE TABLE IF NOT EXISTS public.rfid_flux
(
id_flux bigint NOT NULL DEFAULT nextval('id_flux_seq'::regclass),
codice text COLLATE pg_catalog."default" NOT NULL DEFAULT 'x'::text,
nome text COLLATE pg_catalog."default" NOT NULL DEFAULT 'x'::text,
indirizzo text COLLATE pg_catalog."default" NOT NULL DEFAULT 'x'::text,
flag_sync_db boolean DEFAULT false,
flag_sync_loc boolean DEFAULT false,
CONSTRAINT local_flux_pkey PRIMARY KEY (id_flux)
)

TABLESPACE pg_default;

ALTER TABLE IF EXISTS public.rfid_flux
OWNER to postgres;

GRANT UPDATE, INSERT, SELECT ON TABLE public.rfid_flux TO redblob ;

Thank You for help.

[RedBlob]

Hello @melohagan ,
Have you suggestion for this problem ?
We must start the testing on production and the export function is an important feature for our users.
Thank You.
Best Regards

[melohagan]

Hey @RedBlob I believe this is a bug, and I currently have a PR out: #10721