FrederikBaerentsen/BrickTracker
8
20
Fork 12
Code Issues 16 Pull Requests Actions Packages Projects 1 Releases 10 Wiki Activity

Post 1.4.0 Upgrade - Database Error #158

New Issue
Closed
opened 2026-05-05 02:50:00 +02:00 by jeremywillans · 2 comments
jeremywillans commented 2026-05-05 02:50:00 +02:00
Copy Link
Copy Source

Hi Frederik!

I just upgraded to 1.4.0 and it appeared to go smoothly. I added a new set and that was successful however now trying to open majorty of pages is yielding this error

Database error!
An error has occured: no such column: bricktracker_parts.spare.

Logs only show the same message
ERROR:bricktracker.views.error:Database error: no such column: bricktracker_parts.spare

Hi Frederik! I just upgraded to 1.4.0 and it appeared to go smoothly. I added a new set and that was successful however now trying to open majorty of pages is yielding this error Database error! An error has occured: no such column: bricktracker_parts.spare. Logs only show the same message ERROR:bricktracker.views.error:Database error: no such column: bricktracker_parts.spare
FrederikBaerentsen commented 2026-05-05 08:21:18 +02:00
Owner
Copy Link
Copy Source

Hi @jeremywillans

It sounds like you need to update your BK_PARTS_DEFAULT_ORDER

See Breaking Changes in the release notes: https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker/releases/tag/v1.4.0

If that does not fix it, let me know!

Hi @jeremywillans It sounds like you need to update your `BK_PARTS_DEFAULT_ORDER` See `Breaking Changes` in the release notes: https://gitea.baerentsen.space/FrederikBaerentsen/BrickTracker/releases/tag/v1.4.0 If that does not fix it, let me know!
FrederikBaerentsen added reference release/1.4.1 2026-05-05 08:21:22 +02:00
FrederikBaerentsen added the Kind/Bug label 2026-05-05 08:21:28 +02:00
jeremywillans commented 2026-05-05 08:28:18 +02:00
Author
Copy Link
Copy Source

@FrederikBaerentsen,

Thanks, I didn't set this initially so assumed it would update. Manually changing in admin to align with the default has fixed the issue.

Cheers!

@FrederikBaerentsen, Thanks, I didn't set this initially so assumed it would update. Manually changing in admin to align with the default has fixed the issue. Cheers!
Sign in to join this conversation.
release/1.4.1
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
 Out of Scope
Request is out of scope
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Unraid
Unsupported/Can't help
No Label Kind/Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
FrederikBaerentsen
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#158
Delete Branch "%!s()"

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?