[Bug]: Updated to 2.6.16 (docker-hub) broke my data

[jappyjan]

Binner version

v2.6.16

Operating System

Ubuntu Server x64

Describe the bug and the steps to reproduce it

I created a backup of my data using the admin panel,
then i deleted my old docker instance (wanted to re-organize volumes etc)
and then i created a new docker instance with fresh volumes (no data).
then i signed in as default admin (pw: admin) and restored my backup using the admin panel.

now im greeted with

API Error
Microsoft.Data.Sqlite.SqliteException
Error
An exception occurred of type Microsoft.Data.Sqlite.SqliteException
SQLite Error 1: 'no such column: p.BaseProductNumber'.

in the frontend, sometimes with:

API Error
Status: 500 - No message was specified.

this happens on this request:

curl 'https://<hidden>/api/part/list?orderBy=DateCreatedUtc&direction=Descending&results=10' \
  -H 'accept: */*' \
  -H 'accept-language: de-DE,de;q=0.5' \
  -H 'authorization: Bearer <hidden>' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -b 'refreshToken=<HIDDEN>' \
  -H 'pragma: no-cache' \
  -H 'priority: u=1, i' \
  -H 'referer: https://<hidden>/inventory/add' \
  -H 'sec-ch-ua: "Brave";v="137", "Chromium";v="137", "Not/A)Brand";v="24"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "macOS"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-origin' \
  -H 'sec-gpc: 1' \
  -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36'

Here is the backup file:
binner-backup-2025-6-14.bak.zip

Would you like to attach your appsetings.json configuration?

not sure how to extract it from my docker volumes...

Screenshots or Videos (Optional, but they help!)

No response

Are you able to contribute a PR? (No is ok!)

None

[replaysMike]

Hi @jappyjan - sorry this happened to you! Do you remember what version you were upgrading from? I'll definitely investigate what went wrong. I'm not sure yet if this was a docker configuration problem or an actual bug.

[jappyjan]

I sadly don't remember the version I was on sorry :/