You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched budibase discussions and github issues to check if my issue already exists
Hosting
Self
Method: CLI
Budibase Version: 3.2.29
App Version: 3.2.29
Describe the bug
When adding an external data source such as MS SQL or PSQL unexpected errors occur.
MS SQL - When adding the data source, selecting no tables or clicking skip crashes the builder. Page needs to be refreshed. When deleting the data source, the builder returns the error "Error deleting datasource"
Postgres - When deleting the data source, the builder returns the error "Error deleting datasource"
To Reproduce
Steps to reproduce the behaviour:
Add a new data source - MS SQL or Postgres (have only experimented with these two so far, others may also be affected)
Select no tables, or skip fetching tables
delete (or attempt to delete) the data source
Expected behaviour
A clear and concise description of what you expected to happen.
Checklist
Hosting
Describe the bug
When adding an external data source such as MS SQL or PSQL unexpected errors occur.
MS SQL - When adding the data source, selecting no tables or clicking skip crashes the builder. Page needs to be refreshed. When deleting the data source, the builder returns the error "Error deleting datasource"
Postgres - When deleting the data source, the builder returns the error "Error deleting datasource"
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
A clear and concise description of what you expected to happen.
Screenshots
MS SQL Jam - https://jam.dev/c/c5793404-3029-491d-9778-4cd11783121d
Postgres Jam - https://jam.dev/c/ba13b774-1677-44f4-88ab-f4e8858ad034
App Export
If possible - please attach an export of your budibase application for debugging/reproduction purposes.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: