Every boolean field should have a default value in database #1110

Closed
opened 2025-11-02 03:49:00 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @daviian on GitHub (Sep 30, 2017).

Description

At the moment there are many boolean fields in the database, which do not have a default value.
This leads at least in my tests to different behaviour with different databases in use.

Therefore I suggest to add default values to all boolean fields as it was already briefly discussed in #2354.
This proposal should replace #2354.

Originally created by @daviian on GitHub (Sep 30, 2017). ## Description At the moment there are many boolean fields in the database, which do not have a default value. This leads at least in my tests to different behaviour with different databases in use. Therefore I suggest to add default values to all boolean fields as it was already briefly discussed in #2354. This proposal should replace #2354.
GiteaMirror added the type/enhancementissue/stale labels 2025-11-02 03:49:00 -06:00
Author
Owner

@stale[bot] commented on GitHub (Feb 12, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 12, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (Feb 26, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 26, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1110