Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SqliteError: no such table: tag_parents #45

Closed
sbstratos79 opened this issue Aug 17, 2024 · 3 comments
Closed

SqliteError: no such table: tag_parents #45

sbstratos79 opened this issue Aug 17, 2024 · 3 comments

Comments

@sbstratos79
Copy link

I am using the latest docker image i.e. 1.11.0
Hydrus version is 586.

Rebuilding database throws this error:

Rebuilding Database!

Posts                           [####################] Done in 1.20s
Urls                            [####################] Done in 1.75s
Notes                           [####################] Done in 15ms
Tags                            [####################] Done in 459ms
Mappings                        [####################] Done in 1.75s
Mappings                        [####################] Done in 4.61s
Mappings                        [####################] Done in 18ms
SqliteError: no such table: tag_parents
    at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
    at i.total (/build/server/helpers/dbImport/import.ts:24:64)
    at i.<anonymous> (/build/server/helpers/dbImport/import.ts:49:24)
    at Generator.next (<anonymous>)
    at /app/server.js:229:1303
    at new Promise (<anonymous>)
    at a (/app/server.js:229:1048)
    at i.start (/app/server.js:229:1993)
    at Object.<anonymous> (/build/server/helpers/dbImport/index.ts:73:83)
    at Generator.next (<anonymous>) {
  code: 'SQLITE_ERROR'
}
@bartybobbins
Copy link

This is possibly the side effect of an overhaul of tag parents in Hydrus v586.

overhauled the tag parents/siblings storage tables from the old two-table combined format to dynamic sub-tables separated by both service_id and status. this makes parent and sibling storage a little more spammy but also significantly smaller and more simple, and it ensures search code is always working on clean, efficient, and fast indices, which means no more crazy search variability no matter how we work with these things. as a side benefit, I relaxed the logic so the siblings storage is now capable of storing more 'conflicting' pairs, no longer enforcing an old overly optimistic 1->n rule

@Lxtharia
Copy link

Tried with hydrus v585 in a docker container and it throws the same error

(I would've tried to try another version lower, but pulling 1GB docker images takes too long right now)

funmaker added a commit that referenced this issue Aug 23, 2024
- Added rating.service config that can accept either id number or string name of the rating service
- Deprecated rating.serviceName in favor of rating.service
- Fixed error while importing tags with multiple independent preferred siblings
- Fixed deprecated config options overriding properly named options on conflict
@funmaker
Copy link
Owner

Fixed in v1.12.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants