vikunja/vikunja
Archived
8
54
Fork 94
Code Issues 101 Pull Requests 31 Packages Releases 37 Activity

Make sure all int64 db fields are using bigint when actually storing the data #741

Merged
konrad merged 5 commits from feature/bigint-for-int-fields into master 2020-12-18 16:51:23 +00:00
Conversation 0 Commits 5 Files Changed 22 +279 -71
konrad commented 2020-12-18 15:56:45 +00:00
Owner
Copy Link

Description

This PR is mostly a massive migration to convert all existing records from int(11) to bigint.

# Description This PR is mostly a massive migration to convert all existing records from `int(11)` to `bigint`.
konrad added 4 commits 2020-12-18 15:56:46 +00:00
Fix migration query for postgres
Some checks reported errors
continuous-integration/drone/pr Build was killed
Details
bf97c0023c
konrad added 1 commit 2020-12-18 16:09:48 +00:00
Fix lint
All checks were successful
continuous-integration/drone/pr Build is passing
Details
87cb6cc424
konrad merged commit b0d4902406 into master 2020-12-18 16:51:23 +00:00
konrad deleted branch feature/bigint-for-int-fields 2020-12-18 16:51:28 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
dependencies
duplicate
This issue or pull request already exists
help wanted
Need some help
invalid
Something is wrong
kind/bug
Something is not working
kind/feature
New feature
moved-to-github
needs reproduction
question
More information is needed
security
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
dpschen frederick konrad renovate shilch
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vikunja/vikunja#741
No description provided.
Delete Branch "feature/bigint-for-int-fields"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?