sqlitebrowser / sqlitebrowser/sqlitebrowser
Foreign Key Constraint Failed When Changing Default Value
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 24.6k
- Forks
- 2.4k
- Avg merge
- 3d 49m
- Merged PRs (30d)
- 3
Description
Details for the issue
What did you do?
I attempted to change the default value for the humour field in the article table of my almanack database from "" to "n". (I also tried " ", with the same result.)
What did you expect to see?
I expected the default value to be changed from "" to "n".
What did you see instead?
An error message. See the attached screenshot.
Useful extra information
I get a similar issue to the above when trying to carry out most other changes to the field, such as toggling Not null, or changing its foreign key constraint. (Currently, there is no foreign key constraint.)
What operating system are you using?
- Linux: ( _distro: Ubuntu)
What is your DB4S version?
- Other: Latest Debian.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in DB4S using the almanack database and its article table, changing the humour default from an empty value to "n" or " ". Start by examining the reported error and the related failures when toggling Not null or changing the foreign-key setting; done means these field changes complete successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, sqlite
- Domain
- databases, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100