Grafana: 11.4.0
-
The data_source table uses an INTEGER for the is_prunable field in Sqlite, but a BOOLEAN in Postgres. This causes the import to fail with:
pq: column "is_prunable" is of type boolean but expression is of type integer INSERT INTO "data_source" VALUES...
I assume that Postgres wants the field to be true or false instead of 1 or 0.
- The
playlist table has the fields in a different order. In Sqlite it is: uid, created_at, updated_at while in postgres it is created_at, updated_at, uid. Can column names be used in the dump/import to get around this?
Grafana: 11.4.0
The
data_sourcetable uses an INTEGER for theis_prunablefield in Sqlite, but a BOOLEAN in Postgres. This causes the import to fail with:pq: column "is_prunable" is of type boolean but expression is of type integer INSERT INTO "data_source" VALUES...
I assume that Postgres wants the field to be
trueorfalseinstead of1or0.playlisttable has the fields in a different order. In Sqlite it is:uid, created_at, updated_atwhile in postgres it iscreated_at, updated_at, uid. Can column names be used in the dump/import to get around this?