1
Fork 0
Commit Graph

14 Commits

Author SHA1 Message Date
viktorstrate fc515aa375
Cleanup gorm model attributes + add indexes 2021-01-19 17:31:37 +01:00
viktorstrate a1a14286d6
Properly clean up when a user <-> album relation is deleted 2021-01-06 17:28:06 +01:00
viktorstrate d78cef300a
Finish add/remove root paths 2020-12-31 00:37:11 +01:00
viktorstrate aeb05bca49
get initial scanner up and running 2020-12-22 01:14:43 +01:00
viktorstrate 31da5e1c07
Replace database, initial setup now works 2020-11-28 21:49:33 +01:00
viktorstrate e42ac2436b
Replace database, resolve all build-time errors 2020-11-28 21:29:31 +01:00
viktorstrate 177ae91500 Replace database, mostly video 2020-11-25 23:06:47 +01:00
viktorstrate 3c23f82330 Replace database, mostly album related 2020-11-23 19:59:01 +01:00
stz184 f88fa33e5f InnoDB has a maximum index length of 767 bytes for tables that use COMPACT or REDUNDANT row format, so for utf8mb3 or utf8mb4 columns, you can index a maximum of 255 or 191 characters, respectively.
That's why I created a new column storing a MD5 hash of the path and made it unique. The MD5 hash has only 32 characters and can be generated natively in MySQL and MariaDB. It helps us to avoid maximum key length and in the same time enforce unique photo and album paths.

- Added path_hash column to photo and album tables
- Added down migration file for 005_utf8_migration (just for consistency)
- Added PathHash field to Album and Photo struct
- album_scanner.go and photo_scanner.goo perform checks by MD5 hash now
2020-06-24 11:43:20 +03:00
viktorstrate fc4639a293 Add album path resolver 2020-03-07 16:19:27 +01:00
viktorstrate 2af47b2381 Properly close sql rows 2020-02-28 20:57:46 +01:00
viktorstrate a3a4dda286 Work on share tokens 2020-02-09 21:25:33 +01:00
viktorstrate e6593ee7f3 Working on integrating backend with ui 2020-02-09 15:26:59 +01:00
viktorstrate c2a5b5d2f3 Add album resolver 2020-02-05 16:14:21 +01:00