Budibase / budibase

Low code platform for building business apps and workflows in minutes. Supports PostgreSQL, MySQL, MariaDB, MSSQL, MongoDB, Rest API, Docker, K8s, and more 🚀
https://budibase.com
Other
22.59k stars 1.56k forks source link

Exporting JSON with schema uses wrong file extension, and JSON columns display as null #13069

Open melohagan opened 8 months ago

melohagan commented 8 months ago

Checklist

Hosting

Describe the bug When exporting "JSON with Schema" the file extension is .jsonWithSchema instead of .json I was also exporting a table that had a JSON column, and re-importing, it showed as null instead of 'json'.

To Reproduce Steps to reproduce the behavior:

  1. Create a Budibase internal DB with a JSON array column. Add some row data.
  2. Export with JSON schema
  3. See that the file extension is not .json
  4. Correct the file extension, then create new table -> import JSON
  5. See that the JSON column is type null, when it should say 'JSON'. The import still works.

Expected behavior If I export a table as JSON with schema, the file extension should be .json. If I import a table as JSON, JSON type columns should be imported successfully.

Screenshots Screenshot 2024-02-19 at 16 10 57

Screenshot 2024-02-19 at 16 11 16

Screenshot 2024-02-19 at 16 10 38

Data export export.json

linear[bot] commented 8 months ago

BUDI-8024 Exporting JSON with schema uses wrong file extension, and JSON columns display as null