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

[Bug] Database error if version is greater than 1.0.0 #72

New Issue
Closed
opened 2025-03-22 03:21:55 +01:00 by joshmans · 17 comments
joshmans commented 2025-03-22 03:21:55 +01:00
Copy Link
Copy Source

Hello,

I am experiencing an issue with the database. I want to upgrade to the latest version, and the actual process is fine, but when I go to any version above 1.0.0 on docker, on unraid The Sets page throws a database error: "An error has occured: no such column: set_number."

I followed the migration procedure from pre 1.0.0 to 1.0.0 and when on 1.0.0 everything seems to work

Hello, I am experiencing an issue with the database. I want to upgrade to the latest version, and the actual process is fine, but when I go to any version above 1.0.0 on docker, on unraid The Sets page throws a database error: "An error has occured: no such column: set_number." I followed the migration procedure from pre 1.0.0 to 1.0.0 and when on 1.0.0 everything seems to work
joshmans commented 2025-03-22 21:30:05 +01:00
Author
Copy Link
Copy Source

I just realized that the Parts, Problems, and Minifigures pages also throw database errors for versions greater than 1.0.0 -

Parts: no such column: inventory.name
Problems: no such column: inventory.name
Minifigures: no such column: minifigures.fig_num

I just realized that the Parts, Problems, and Minifigures pages also throw database errors for versions greater than 1.0.0 - Parts: no such column: inventory.name Problems: no such column: inventory.name Minifigures: no such column: minifigures.fig_num
usafa43tsolo commented 2025-03-28 16:18:24 +01:00
Copy Link
Copy Source

I just installed as new within Unraid and I'm getting the same errors and issues.

Folders, app.db, and .env files were present before starting the container for the first time. All folders and files within the bricktracker folder were given read/write permissions across the board.

I pulled v1.2.2 and the database is on version #15.

  • Sets: Database error! An error has occured: no such column: set_number.
  • Parts: Database error! An error has occured: no such column: inventory.name.
  • Problems: Database error! An error has occured: no such column: inventory.name.
  • Minifigures: Database error! An error has occured: no such column: minifigures.fig_num.
  • Wishlist: Database error! An error has occured: no such column: wishlist.rowid.

I don't see any issues within the logs about access or permissions:

[2025-03-28 11:00:41 -0400] [7] [INFO] Starting gunicorn 23.0.0
[2025-03-28 11:00:41 -0400] [7] [INFO] Listening at: http://0.0.0.0:3333 (7)
[2025-03-28 11:00:41 -0400] [7] [INFO] Using worker: eventlet
[2025-03-28 11:00:41 -0400] [8] [INFO] Booting worker with pid: 8
[2025-03-28 11:00:49,835] INFO - Loading set owners list
[2025-03-28 11:00:49,837] ERROR - Database error: Your database need to be upgraded from version 0 to version 15
[2025-03-28 11:00:51,768] INFO - Loading instructions file list
[2025-03-28 11:00:51,768] INFO - Loading set purchase locations list
[2025-03-28 11:00:51,770] WARNING - A database exception occured while loading the admin page: no such table: bricktracker_metadata_purchase_locations
[2025-03-28 11:00:51,770] INFO - Loading retired sets list
[2025-03-28 11:00:51,770] INFO - Loading themes list
[2025-03-28 11:01:00,696] INFO - Loading SQL migrations list
[2025-03-28 11:01:10,538] INFO - Applying migration 1
[2025-03-28 11:01:10,591] INFO - Applying migration 2
[2025-03-28 11:01:10,632] INFO - Applying migration 3
[2025-03-28 11:01:10,644] INFO - Applying migration 4
[2025-03-28 11:01:10,656] INFO - Applying migration 5
[2025-03-28 11:01:10,668] INFO - Applying migration 6
[2025-03-28 11:01:10,681] INFO - Applying migration 7
[2025-03-28 11:01:10,696] INFO - Applying migration 8
[2025-03-28 11:01:10,708] INFO - Applying migration 9
[2025-03-28 11:01:10,722] INFO - Applying migration 10
[2025-03-28 11:01:10,737] INFO - Applying migration 11
[2025-03-28 11:01:10,750] INFO - Applying migration 12
[2025-03-28 11:01:10,763] INFO - Applying migration 13
[2025-03-28 11:01:10,775] INFO - Applying migration 14
[2025-03-28 11:01:10,787] INFO - Applying migration 15
[2025-03-28 11:01:10,799] INFO - Loading instructions file list
[2025-03-28 11:01:10,800] INFO - Loading set owners list
[2025-03-28 11:01:10,802] INFO - Loading set purchase locations list
[2025-03-28 11:01:10,803] INFO - Loading set statuses list
[2025-03-28 11:01:10,804] INFO - Loading set storages list
[2025-03-28 11:01:10,806] INFO - Loading set tags list
[2025-03-28 11:01:10,807] INFO - Loading retired sets list
[2025-03-28 11:01:10,807] INFO - Loading themes list
[2025-03-28 11:01:10,807] INFO - Loading wish owners list
[2025-03-28 11:01:23,427] INFO - The database has been downloaded
[2025-03-28 11:02:48,539] INFO - Theme list updated
[2025-03-28 11:02:48,539] INFO - Loading themes list
[2025-03-28 11:02:53,634] INFO - Loading retired sets list
[2025-03-28 11:03:10,408] ERROR - Database error: no such column: minifigures.fig_num
[2025-03-28 11:03:11,516] ERROR - Database error: no such column: inventory.name
[2025-03-28 11:03:12,665] ERROR - Database error: no such column: inventory.name
[2025-03-28 11:03:14,474] ERROR - Database error: no such column: inventory.name

I just installed as new within Unraid and I'm getting the same errors and issues. Folders, app.db, and .env files were present before starting the container for the first time. All folders and files within the bricktracker folder were given read/write permissions across the board. I pulled v1.2.2 and the database is on version #15. - Sets: Database error! An error has occured: no such column: set_number. - Parts: Database error! An error has occured: no such column: inventory.name. - Problems: Database error! An error has occured: no such column: inventory.name. - Minifigures: Database error! An error has occured: no such column: minifigures.fig_num. - Wishlist: Database error! An error has occured: no such column: wishlist.rowid. I don't see any issues within the logs about access or permissions: [2025-03-28 11:00:41 -0400] [7] [INFO] Starting gunicorn 23.0.0 [2025-03-28 11:00:41 -0400] [7] [INFO] Listening at: http://0.0.0.0:3333 (7) [2025-03-28 11:00:41 -0400] [7] [INFO] Using worker: eventlet [2025-03-28 11:00:41 -0400] [8] [INFO] Booting worker with pid: 8 [2025-03-28 11:00:49,835] INFO - Loading set owners list [2025-03-28 11:00:49,837] ERROR - Database error: Your database need to be upgraded from version 0 to version 15 [2025-03-28 11:00:51,768] INFO - Loading instructions file list [2025-03-28 11:00:51,768] INFO - Loading set purchase locations list [2025-03-28 11:00:51,770] WARNING - A database exception occured while loading the admin page: no such table: bricktracker_metadata_purchase_locations [2025-03-28 11:00:51,770] INFO - Loading retired sets list [2025-03-28 11:00:51,770] INFO - Loading themes list [2025-03-28 11:01:00,696] INFO - Loading SQL migrations list [2025-03-28 11:01:10,538] INFO - Applying migration 1 [2025-03-28 11:01:10,591] INFO - Applying migration 2 [2025-03-28 11:01:10,632] INFO - Applying migration 3 [2025-03-28 11:01:10,644] INFO - Applying migration 4 [2025-03-28 11:01:10,656] INFO - Applying migration 5 [2025-03-28 11:01:10,668] INFO - Applying migration 6 [2025-03-28 11:01:10,681] INFO - Applying migration 7 [2025-03-28 11:01:10,696] INFO - Applying migration 8 [2025-03-28 11:01:10,708] INFO - Applying migration 9 [2025-03-28 11:01:10,722] INFO - Applying migration 10 [2025-03-28 11:01:10,737] INFO - Applying migration 11 [2025-03-28 11:01:10,750] INFO - Applying migration 12 [2025-03-28 11:01:10,763] INFO - Applying migration 13 [2025-03-28 11:01:10,775] INFO - Applying migration 14 [2025-03-28 11:01:10,787] INFO - Applying migration 15 [2025-03-28 11:01:10,799] INFO - Loading instructions file list [2025-03-28 11:01:10,800] INFO - Loading set owners list [2025-03-28 11:01:10,802] INFO - Loading set purchase locations list [2025-03-28 11:01:10,803] INFO - Loading set statuses list [2025-03-28 11:01:10,804] INFO - Loading set storages list [2025-03-28 11:01:10,806] INFO - Loading set tags list [2025-03-28 11:01:10,807] INFO - Loading retired sets list [2025-03-28 11:01:10,807] INFO - Loading themes list [2025-03-28 11:01:10,807] INFO - Loading wish owners list [2025-03-28 11:01:23,427] INFO - The database has been downloaded [2025-03-28 11:02:48,539] INFO - Theme list updated [2025-03-28 11:02:48,539] INFO - Loading themes list [2025-03-28 11:02:53,634] INFO - Loading retired sets list [2025-03-28 11:03:10,408] ERROR - Database error: no such column: minifigures.fig_num [2025-03-28 11:03:11,516] ERROR - Database error: no such column: inventory.name [2025-03-28 11:03:12,665] ERROR - Database error: no such column: inventory.name [2025-03-28 11:03:14,474] ERROR - Database error: no such column: inventory.name
joshmans commented 2025-03-28 22:12:16 +01:00
Author
Copy Link
Copy Source

@bitkraken - do you have any input here? Still getting this issue. Not sure if its exclusive to unraid?

@bitkraken - do you have any input here? Still getting this issue. Not sure if its exclusive to unraid?
bitkraken commented 2025-03-28 22:29:20 +01:00
Copy Link
Copy Source

@joshmans well v1.2.2 us running fine for me ... BUT ... I'm not using unraid ... I'm running it inside a docker container running on ubuntu server.
(maybe you tagged me by mistake, as I was not a participant on this issue before)

have you checked, if the columns are really not there inside the app.db?

@joshmans well v1.2.2 us running fine for me ... BUT ... I'm not using unraid ... I'm running it inside a docker container running on ubuntu server. (maybe you tagged me by mistake, as I was not a participant on this issue before) have you checked, if the columns are really not there inside the app.db?
FrederikBaerentsen commented 2025-03-28 22:32:44 +01:00
Owner
Copy Link
Copy Source

@joshmans Sorry, I have no idea how Unraid works. I have tested the image and it's upgrade/migration on several new VMs using plain Docker and it works without issues. I assume this is an Unraid issue.

@joshmans Sorry, I have no idea how Unraid works. I have tested the image and it's upgrade/migration on several new VMs using plain Docker and it works without issues. I assume this is an Unraid issue.
joshmans commented 2025-03-28 22:39:23 +01:00
Author
Copy Link
Copy Source

@bitkraken yes. It was a mistake. Apologies!

@FrederikBaerentsen can you advise which columns should be present in each of the tables? I'm not well versed in SQL to be able to look at the code. But I do have a SQLLite browser I can use to look at and add the tables as needed. I'm wondering if some columns didn't get renamed in the jump from db version 0 to 6?

@bitkraken yes. It was a mistake. Apologies! @FrederikBaerentsen can you advise which columns should be present in each of the tables? I'm not well versed in SQL to be able to look at the code. But I do have a SQLLite browser I can use to look at and add the tables as needed. I'm wondering if some columns didn't get renamed in the jump from db version 0 to 6?
FrederikBaerentsen commented 2025-03-28 22:55:00 +01:00
Owner
Copy Link
Copy Source

@joshmans

This is a schema dump from my database.

CREATE TABLE IF NOT EXISTS "wishlist_old" (
        set_num TEXT,
        name TEXT,
        year INTEGER,
        theme_id INTEGER,
        num_parts INTEGER,
        set_img_url TEXT,
        set_url TEXT,
        last_modified_dt TEXT
    );
CREATE TABLE IF NOT EXISTS "sets_old" (
        set_num TEXT,
        name TEXT,
        year INTEGER,
        theme_id INTEGER,
        num_parts INTEGER,
        set_img_url TEXT,
        set_url TEXT,
        last_modified_dt TEXT,
        mini_col BOOLEAN,
        set_check BOOLEAN,
        set_col BOOLEAN,
        u_id TEXT
    );
CREATE TABLE IF NOT EXISTS "inventory_old" (
        set_num TEXT,
        id INTEGER,
        part_num TEXT,
        name TEXT,
        part_img_url TEXT,
        part_img_url_id TEXT,
        color_id INTEGER,
        color_name TEXT,
        quantity INTEGER,
        is_spare BOOLEAN,
        element_id INTEGER,
        u_id TEXT
    );
CREATE TABLE IF NOT EXISTS "minifigures_old" (
        fig_num TEXT,
        set_num TEXT,
        name TEXT,
        quantity INTEGER,
        set_img_url TEXT,
        u_id TEXT
    );
CREATE TABLE IF NOT EXISTS "missing_old" (
        set_num TEXT,
        id INTEGER,
        part_num TEXT,
        part_img_url_id TEXT,
        color_id INTEGER,
        quantity INTEGER,
        element_id INTEGER,
        u_id TEXT
    );
CREATE TABLE IF NOT EXISTS "rebrickable_sets" (
    "set" TEXT NOT NULL,
    "number" INTEGER NOT NULL,
    "version" INTEGER NOT NULL,
    "name" TEXT NOT NULL,
    "year" INTEGER NOT NULL,
    "theme_id" INTEGER NOT NULL,
    "number_of_parts" INTEGER NOT NULL,
    "image" TEXT,
    "url" TEXT,
    "last_modified" TEXT,
    PRIMARY KEY("set")
);
CREATE TABLE IF NOT EXISTS "bricktracker_metadata_statuses" (
    "id" TEXT NOT NULL,
    "name" TEXT NOT NULL,
    "displayed_on_grid" BOOLEAN NOT NULL DEFAULT 0,
    PRIMARY KEY("id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_wishes" (
    "set" TEXT NOT NULL,
    "name" TEXT NOT NULL,
    "year" INTEGER NOT NULL,
    "theme_id" INTEGER NOT NULL,
    "number_of_parts" INTEGER NOT NULL,
    "image" TEXT,
    "url" TEXT,
    PRIMARY KEY("set")
);
CREATE TABLE IF NOT EXISTS "bricktracker_metadata_storages" (
    "id" TEXT NOT NULL,
    "name" TEXT NOT NULL,
    PRIMARY KEY("id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_metadata_purchase_locations" (
    "id" TEXT NOT NULL,
    "name" TEXT NOT NULL,
    PRIMARY KEY("id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_sets" (
    "id" TEXT NOT NULL,
    "set" TEXT NOT NULL,
    "description" TEXT,
    "storage" TEXT, -- Storage bin location
    "purchase_date" REAL, -- Purchase data
    "purchase_location" TEXT, -- Purchase location
    "purchase_price" REAL, -- Purchase price
    PRIMARY KEY("id"),
    FOREIGN KEY("set") REFERENCES "rebrickable_sets"("set"),
    FOREIGN KEY("storage") REFERENCES "bricktracker_metadata_storages"("id"),
    FOREIGN KEY("purchase_location") REFERENCES "bricktracker_metadata_purchase_locations"("id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_set_statuses" (
    "id" TEXT NOT NULL,
    "status_minifigures_collected" BOOLEAN NOT NULL DEFAULT 0, "status_set_checked" BOOLEAN NOT NULL DEFAULT 0, "status_set_collected" BOOLEAN NOT NULL DEFAULT 0,
    PRIMARY KEY("id"),
    FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id")
);
CREATE TABLE IF NOT EXISTS "rebrickable_minifigures" (
    "figure" TEXT NOT NULL,
    "number" INTEGER NOT NULL,
    "name" TEXT NOT NULL,
    "image" TEXT, "number_of_parts" INTEGER NOT NULL DEFAULT 0,
    PRIMARY KEY("figure")
);
CREATE TABLE IF NOT EXISTS "bricktracker_minifigures" (
    "id" TEXT NOT NULL,
    "figure" TEXT NOT NULL,
    "quantity" INTEGER NOT NULL,
    PRIMARY KEY("id", "figure"),
    FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id"),
    FOREIGN KEY("figure") REFERENCES "rebrickable_minifigures"("figure")
);
CREATE TABLE IF NOT EXISTS "rebrickable_parts" (
    "part" TEXT NOT NULL,
    "color_id" INTEGER NOT NULL,
    "color_name" TEXT NOT NULL,
    "color_rgb" TEXT, -- can be NULL because it was not saved before
    "color_transparent" BOOLEAN, -- can be NULL because it was not saved before
    "name" TEXT NOT NULL,
    "category" INTEGER, -- can be NULL because it was not saved before
    "image" TEXT,
    "image_id" TEXT,
    "url" TEXT, -- can be NULL because it was not saved before
    "print" INTEGER, -- can be NULL, was not saved before
    PRIMARY KEY("part", "color_id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_parts" (
    "id" TEXT NOT NULL,
    "figure" TEXT,
    "part" TEXT NOT NULL,
    "color" INTEGER NOT NULL,
    "spare" BOOLEAN NOT NULL,
    "quantity" INTEGER NOT NULL,
    "element" INTEGER,
    "rebrickable_inventory" INTEGER NOT NULL,
    "missing" INTEGER NOT NULL DEFAULT 0,
    "damaged" INTEGER NOT NULL DEFAULT 0,
    PRIMARY KEY("id", "figure", "part", "color", "spare"),
    FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id"),
    FOREIGN KEY("figure") REFERENCES "rebrickable_minifigures"("figure"),
    FOREIGN KEY("part", "color") REFERENCES "rebrickable_parts"("part", "color_id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_metadata_owners" (
    "id" TEXT NOT NULL,
    "name" TEXT NOT NULL,
    PRIMARY KEY("id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_set_owners" (
    "id" TEXT NOT NULL, 
    PRIMARY KEY("id"),
    FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_wish_owners" (
    "set" TEXT NOT NULL, 
    PRIMARY KEY("set"),
    FOREIGN KEY("set") REFERENCES "bricktracker_wishes"("set")
);
CREATE TABLE IF NOT EXISTS "bricktracker_metadata_tags" (
    "id" TEXT NOT NULL,
    "name" TEXT NOT NULL,
    PRIMARY KEY("id")
);
CREATE TABLE IF NOT EXISTS "bricktracker_set_tags" (
    "id" TEXT NOT NULL, 
    PRIMARY KEY("id"),
    FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id")
);
@joshmans This is a schema dump from my database. ```` CREATE TABLE IF NOT EXISTS "wishlist_old" ( set_num TEXT, name TEXT, year INTEGER, theme_id INTEGER, num_parts INTEGER, set_img_url TEXT, set_url TEXT, last_modified_dt TEXT ); CREATE TABLE IF NOT EXISTS "sets_old" ( set_num TEXT, name TEXT, year INTEGER, theme_id INTEGER, num_parts INTEGER, set_img_url TEXT, set_url TEXT, last_modified_dt TEXT, mini_col BOOLEAN, set_check BOOLEAN, set_col BOOLEAN, u_id TEXT ); CREATE TABLE IF NOT EXISTS "inventory_old" ( set_num TEXT, id INTEGER, part_num TEXT, name TEXT, part_img_url TEXT, part_img_url_id TEXT, color_id INTEGER, color_name TEXT, quantity INTEGER, is_spare BOOLEAN, element_id INTEGER, u_id TEXT ); CREATE TABLE IF NOT EXISTS "minifigures_old" ( fig_num TEXT, set_num TEXT, name TEXT, quantity INTEGER, set_img_url TEXT, u_id TEXT ); CREATE TABLE IF NOT EXISTS "missing_old" ( set_num TEXT, id INTEGER, part_num TEXT, part_img_url_id TEXT, color_id INTEGER, quantity INTEGER, element_id INTEGER, u_id TEXT ); CREATE TABLE IF NOT EXISTS "rebrickable_sets" ( "set" TEXT NOT NULL, "number" INTEGER NOT NULL, "version" INTEGER NOT NULL, "name" TEXT NOT NULL, "year" INTEGER NOT NULL, "theme_id" INTEGER NOT NULL, "number_of_parts" INTEGER NOT NULL, "image" TEXT, "url" TEXT, "last_modified" TEXT, PRIMARY KEY("set") ); CREATE TABLE IF NOT EXISTS "bricktracker_metadata_statuses" ( "id" TEXT NOT NULL, "name" TEXT NOT NULL, "displayed_on_grid" BOOLEAN NOT NULL DEFAULT 0, PRIMARY KEY("id") ); CREATE TABLE IF NOT EXISTS "bricktracker_wishes" ( "set" TEXT NOT NULL, "name" TEXT NOT NULL, "year" INTEGER NOT NULL, "theme_id" INTEGER NOT NULL, "number_of_parts" INTEGER NOT NULL, "image" TEXT, "url" TEXT, PRIMARY KEY("set") ); CREATE TABLE IF NOT EXISTS "bricktracker_metadata_storages" ( "id" TEXT NOT NULL, "name" TEXT NOT NULL, PRIMARY KEY("id") ); CREATE TABLE IF NOT EXISTS "bricktracker_metadata_purchase_locations" ( "id" TEXT NOT NULL, "name" TEXT NOT NULL, PRIMARY KEY("id") ); CREATE TABLE IF NOT EXISTS "bricktracker_sets" ( "id" TEXT NOT NULL, "set" TEXT NOT NULL, "description" TEXT, "storage" TEXT, -- Storage bin location "purchase_date" REAL, -- Purchase data "purchase_location" TEXT, -- Purchase location "purchase_price" REAL, -- Purchase price PRIMARY KEY("id"), FOREIGN KEY("set") REFERENCES "rebrickable_sets"("set"), FOREIGN KEY("storage") REFERENCES "bricktracker_metadata_storages"("id"), FOREIGN KEY("purchase_location") REFERENCES "bricktracker_metadata_purchase_locations"("id") ); CREATE TABLE IF NOT EXISTS "bricktracker_set_statuses" ( "id" TEXT NOT NULL, "status_minifigures_collected" BOOLEAN NOT NULL DEFAULT 0, "status_set_checked" BOOLEAN NOT NULL DEFAULT 0, "status_set_collected" BOOLEAN NOT NULL DEFAULT 0, PRIMARY KEY("id"), FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id") ); CREATE TABLE IF NOT EXISTS "rebrickable_minifigures" ( "figure" TEXT NOT NULL, "number" INTEGER NOT NULL, "name" TEXT NOT NULL, "image" TEXT, "number_of_parts" INTEGER NOT NULL DEFAULT 0, PRIMARY KEY("figure") ); CREATE TABLE IF NOT EXISTS "bricktracker_minifigures" ( "id" TEXT NOT NULL, "figure" TEXT NOT NULL, "quantity" INTEGER NOT NULL, PRIMARY KEY("id", "figure"), FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id"), FOREIGN KEY("figure") REFERENCES "rebrickable_minifigures"("figure") ); CREATE TABLE IF NOT EXISTS "rebrickable_parts" ( "part" TEXT NOT NULL, "color_id" INTEGER NOT NULL, "color_name" TEXT NOT NULL, "color_rgb" TEXT, -- can be NULL because it was not saved before "color_transparent" BOOLEAN, -- can be NULL because it was not saved before "name" TEXT NOT NULL, "category" INTEGER, -- can be NULL because it was not saved before "image" TEXT, "image_id" TEXT, "url" TEXT, -- can be NULL because it was not saved before "print" INTEGER, -- can be NULL, was not saved before PRIMARY KEY("part", "color_id") ); CREATE TABLE IF NOT EXISTS "bricktracker_parts" ( "id" TEXT NOT NULL, "figure" TEXT, "part" TEXT NOT NULL, "color" INTEGER NOT NULL, "spare" BOOLEAN NOT NULL, "quantity" INTEGER NOT NULL, "element" INTEGER, "rebrickable_inventory" INTEGER NOT NULL, "missing" INTEGER NOT NULL DEFAULT 0, "damaged" INTEGER NOT NULL DEFAULT 0, PRIMARY KEY("id", "figure", "part", "color", "spare"), FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id"), FOREIGN KEY("figure") REFERENCES "rebrickable_minifigures"("figure"), FOREIGN KEY("part", "color") REFERENCES "rebrickable_parts"("part", "color_id") ); CREATE TABLE IF NOT EXISTS "bricktracker_metadata_owners" ( "id" TEXT NOT NULL, "name" TEXT NOT NULL, PRIMARY KEY("id") ); CREATE TABLE IF NOT EXISTS "bricktracker_set_owners" ( "id" TEXT NOT NULL, PRIMARY KEY("id"), FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id") ); CREATE TABLE IF NOT EXISTS "bricktracker_wish_owners" ( "set" TEXT NOT NULL, PRIMARY KEY("set"), FOREIGN KEY("set") REFERENCES "bricktracker_wishes"("set") ); CREATE TABLE IF NOT EXISTS "bricktracker_metadata_tags" ( "id" TEXT NOT NULL, "name" TEXT NOT NULL, PRIMARY KEY("id") ); CREATE TABLE IF NOT EXISTS "bricktracker_set_tags" ( "id" TEXT NOT NULL, PRIMARY KEY("id"), FOREIGN KEY("id") REFERENCES "bricktracker_sets"("id") ); ````
joshmans commented 2025-03-28 23:10:32 +01:00
Author
Copy Link
Copy Source

@FrederikBaerentsen your schema doesn't appear to have any "set_number" column, so I'm struggling to understand how the application would even be looking for it

@FrederikBaerentsen your schema doesn't appear to have any "set_number" column, so I'm struggling to understand how the application would even be looking for it
FrederikBaerentsen commented 2025-03-28 23:16:30 +01:00
Owner
Copy Link
Copy Source

rebrickable_sets uses number and version as set_number.

I would suggest you try and deploy using Docker Compose as it’s the only supported method.

rebrickable_sets uses number and version as set_number. I would suggest you try and deploy using Docker Compose as it’s the only supported method.
joshmans commented 2025-03-28 23:18:49 +01:00
Author
Copy Link
Copy Source

so your concatenate those two columns into a virtual column or something? I'll see if I can get compose working. unraid and compose is always a pain lol

so your concatenate those two columns into a virtual column or something? I'll see if I can get compose working. unraid and compose is always a pain lol
joshmans commented 2025-03-28 23:46:38 +01:00
Author
Copy Link
Copy Source

@usafa43tsolo @FrederikBaerentsen I figured it out.

The unraid CommunityApplications template for BrickTracker sets the default sorting environment variables (in the 'show more settings') area. I simply removed the variables so they would be set to their defaults and all is working as expected now.

@usafa43tsolo @FrederikBaerentsen I figured it out. The unraid CommunityApplications template for BrickTracker sets the default sorting environment variables (in the 'show more settings') area. I simply removed the variables so they would be set to their defaults and all is working as expected now.
👀 2
usafa43tsolo commented 2025-03-29 00:45:32 +01:00
Copy Link
Copy Source

@joshmans I had a feeling it was Unraid-specific for one reason or another. Thanks for sorting that out!

@FrederikBaerentsen We really appreciate all your work to maintain BrickTracker! I love it!

@joshmans I had a feeling it was Unraid-specific for one reason or another. Thanks for sorting that out! @FrederikBaerentsen We really appreciate all your work to maintain BrickTracker! I love it!
Watever commented 2025-05-20 02:45:09 +02:00
Copy Link
Copy Source

@usafa43tsolo @FrederikBaerentsen I figured it out.

The unraid CommunityApplications template for BrickTracker sets the default sorting environment variables (in the 'show more settings') area. I simply removed the variables so they would be set to their defaults and all is working as expected now.

Have you removed all the "additionnal setting" or only the ones related to the sorting of the database ?

Do you think we could modify the Unraid template ?
I had the same issue and took a while to understand.

> @usafa43tsolo @FrederikBaerentsen I figured it out. > > The unraid CommunityApplications template for BrickTracker sets the default sorting environment variables (in the 'show more settings') area. I simply removed the variables so they would be set to their defaults and all is working as expected now. Have you removed all the "additionnal setting" or only the ones related to the sorting of the database ? Do you think we could modify the Unraid template ? I had the same issue and took a while to understand.
unsubtle commented 2025-05-23 18:38:32 +02:00
Copy Link
Copy Source

Hello, maintainer of the Unraid template here (grtgbln on Unraid, nwithan8 on GitHub). I was pinged over on my repo about some out-of-date changes to this template that I just finished updating.

If I may make a suggestion, I'm sure you're aware of the comically large number of environmental variables for this project, each of which must be explicitly added to the Unraid template whenever the container is updated, which seems to be quite often (I have enrolled this app in my new monitoring system that should alert me if Docker-related things change with this app moving forward). Might I recommend, however, moving all these variables instead to a single configuration file that can be mounted into the Docker container? Would also make it easier, I imagine, for users to debug their configuration settings rather than having to parse through 100 environmental variables.

I personally went through this with my own application, starting with environmental variables, until a certain point where it because too cumbersome and pivoted to a config file.

Hello, maintainer of the [Unraid template](https://github.com/nwithan8/unraid_templates/blob/main/templates/brick_tracker.xml) here (grtgbln on Unraid, nwithan8 on GitHub). I was pinged over on my repo about some out-of-date changes to this template that I just finished updating. If I may make a suggestion, I'm sure you're aware of the comically large number of environmental variables for this project, each of which must be explicitly added to the Unraid template whenever the container is updated, which seems to be quite often (I have enrolled this app in my new monitoring system that should alert me if Docker-related things change with this app moving forward). Might I recommend, however, moving all these variables instead to a single configuration file that can be mounted into the Docker container? Would also make it easier, I imagine, for users to debug their configuration settings rather than having to parse through 100 environmental variables. I personally went through this with my own application, starting with environmental variables, until a certain point where it because too cumbersome and pivoted to a config file.
FrederikBaerentsen added the
Status
Need More Info
Unraid labels 2025-09-14 11:41:34 +02:00
FrederikBaerentsen changed title from Database error if version is greater than 1.0.0 to [Bug] Database error if version is greater than 1.0.0 2025-09-22 08:52:02 +02:00
FrederikBaerentsen added the Kind/Bug label 2025-09-22 08:53:18 +02:00
bckthms commented 2025-11-15 20:49:03 +01:00
Copy Link
Copy Source

Hi @unsubtle
It seems that Frederik followed your idea to put variables in an external .env file since several months
Can you take a look and update the Unraid template if needed please ?

Hi @unsubtle It seems that Frederik followed your idea to put variables in an external .env file since several months Can you take a look and update the Unraid template if needed please ?
unsubtle commented 2025-11-17 00:54:56 +01:00
Copy Link
Copy Source

Hi @unsubtle
It seems that Frederik followed your idea to put variables in an external .env file since several months
Can you take a look and update the Unraid template if needed please ?

Thanks for letting me know, but I believe you're confusing the .env file, which is just used for Docker Compose purposes, versus an internal config file which is what I was suggesting. I don't see any changes on this app in the past two months, so the Unraid template should be current.

> Hi @unsubtle > It seems that Frederik followed your idea to put variables in an external .env file since several months > Can you take a look and update the Unraid template if needed please ? Thanks for letting me know, but I believe you're confusing the .env file, which is just used for Docker Compose purposes, versus an internal config file which is what I was suggesting. I don't see any changes on this app in the past two months, so the Unraid template should be current.
👍 1
FrederikBaerentsen commented 2025-12-18 15:03:57 +01:00
Owner
Copy Link
Copy Source

It's been some time since there was any activity on this issue. I'm going to close this one due to inactivity.

If this is still relevant, feel free to reopen it.

It's been some time since there was any activity on this issue. I'm going to close this one due to inactivity. If this is still relevant, feel free to reopen it.
Sign in to join this conversation.
No Branch/Tag Specified
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
Status
Need More Info
 Unraid
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
FrederikBaerentsen
No Assignees
7 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#72
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?