Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Saving changes to database initialization script deletes the other initialization scripts #3273

Open
1 of 2 tasks
NikolasPpd opened this issue Aug 31, 2024 · 1 comment
Assignees
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged. 🚧 Next Issues and PRs planned for the next release.

Comments

@NikolasPpd
Copy link

Description

I can add multiple initialization scripts to the database just fine. If I then click save in any of those scripts, any changes made to that particular script will be saved, but all the other scripts disappear.

This problem happens in a PostgreSQL database resource. Haven't tested it with other databases but if they also support initialization scripts then they might share the same issue.

Expected behavior: Clicking save should save changes made to a script without deleting the others.

Minimal Reproduction (if possible, example repository)

  1. Add multiple initialization scripts to your database
    image

  2. Click one of the save buttons next to the scripts (it's not necessary to make any changes)

  3. Page refreshes, says the changes were saved successfully and now all the scripts are gone except the one you saved
    image

Exception or Error

No response

Version

v4.0.0-beta.323

Cloud?

  • Yes
  • No
@peaklabs-dev peaklabs-dev added the 🐛 Bug Reported issues that need to be reproduced by the team. label Aug 31, 2024
@peaklabs-dev peaklabs-dev added the 🐞 Confirmed Bug Verified issues that have been reproduced by the team. label Oct 16, 2024
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Oct 16, 2024
@peaklabs-dev peaklabs-dev self-assigned this Oct 18, 2024
@peaklabs-dev peaklabs-dev added 🚧 Next Issues and PRs planned for the next release. ✅ Done Issues that are fixed and a PR is ready to be merged. and removed ✅ Done Issues that are fixed and a PR is ready to be merged. labels Oct 18, 2024
@peaklabs-dev
Copy link
Member

A fix for this issue has been implemented and will be available in an upcoming release. Thank you for your patience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged. 🚧 Next Issues and PRs planned for the next release.
Projects
None yet
Development

No branches or pull requests

2 participants