Skip to content
New issue

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

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

Already on GitHub? # to your account

Deleting patches that are part of a Synth Bank throws error instead of explanation why they can't be deleted #386

Closed
christofmuc opened this issue Jan 14, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@christofmuc
Copy link
Owner

Trying to delete a whole imported bank I get the following error:

error DATABASE ERROR in deletePatches via filter: SQL Exception FOREIGN KEY constraint failed


Deleting patches also doesn't seem to work and I get the following error:

warning Could not delete patch Synthwave 2.3 from database as it is referred to be at least one bank definition. Removed it from user lists and set it to hidden instead

Originally posted by @RadekPilich in #378

@christofmuc christofmuc changed the title Trying to delete a whole imported bank throws SQL error Deleting patches that are part of a Synth Bank throws error instead of explanation why they can't be deleted Jan 18, 2025
@christofmuc christofmuc added the bug Something isn't working label Jan 18, 2025
@RadekPilich
Copy link

RadekPilich commented Feb 2, 2025

@christofmuc Feel free to close this one. I now understand how to delete synth banks, imports, patches. Some tooltip guide or help page would be helpful to grasp this. Although it's probably easier / more effective if I or someone else made a handful of short videos to show the main workflows and functions.

@christofmuc
Copy link
Owner Author

Yea, thanks! I keep this open because there should be a dialog box popping up and not a SQL Exception error, the software can be a bit more friendly...

The video idea is good, I am just incredibly slow at that, which is why I never got around to do it,

christofmuc added a commit that referenced this issue Feb 23, 2025
@christofmuc christofmuc added the Ready for release Will be part of the next release label Feb 23, 2025
@christofmuc
Copy link
Owner Author

Reworked delete logic so it hides patches that are part of the bank instead of trying to delete them, which wouldn't work.

@christofmuc christofmuc removed the Ready for release Will be part of the next release label Feb 23, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants