nextcloud / nextcloud/documentation
Document BIGINT declaration in migrations
Open
Nobody has claimed this yet.
1. to develop
enhancement
manual: developer
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
With https://github.com/nextcloud/mail/pull/6436 we saw that the column size is not the same for all DB types and might need special care between MariaDB and SQLite. This would be great to have documented in the database section.
Contributor guide
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
Start in the documentation's database section and review nextcloud/mail#6436 for the MariaDB and SQLite BIGINT behavior that prompted this issue. Document how BIGINT declarations differ between those database types and what migration authors need to handle; done means the database guidance covers the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb, sqlite
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100