The Immich API and database should store `null` instead of empty strings. Columns where this is happening: - [ ] `album.description` (#30123) - [ ] `asset_exif.description` (#30069) - [ ] `person.name` (#29702) - [ ] `person.thumbnailPath` (#30070) - [ ] `session.deviceType` (#30048) - [ ] `session.deviceOS` (#30048) - [x] `user.password` (#30223) - [ ] `user.profileImagePath` (#30141) - [ ] `user.oauthId` (#30157) - [ ] `user.name` (#30106)
The Immich API and database should store
nullinstead of empty strings.Columns where this is happening:
album.description(feat: store null instead of empty string for album.description #30123)asset_exif.description(fix(server): store null instead of empty string for asset_exif description #30069)person.name(fix(server): store null instead of empty string for person name #29702)person.thumbnailPath(fix(server): store null instead of empty string for person thumbnailPath #30070)session.deviceType(fix(server): store null instead of empty string for session deviceType and deviceOS #30048)session.deviceOS(fix(server): store null instead of empty string for session deviceType and deviceOS #30048)user.password(fix(server): store null instead of empty string for user password #30223)user.profileImagePath(fix(server): store null instead of empty string for user profileImagePath #30141)user.oauthId(fix(server): store null instead of empty string for user oauthId #30157)user.name(fix(server): store null instead of empty string for user name #30106)for everyone working on PRs for this issue, some hints :)
nulland''actually mean the same for that column''to null in the request schema to not break clients sending''+ add TODO comments to drop this in v4HistoryBuilderinfo on request fields indicating that clients must sendnullinstead of''in an upcoming major version''instead ofnullon the API surface to not break clients + add TODO comments to returnnullin v4HistoryBuilderinfo on response fields indicating that clients will sendnullinstead of''in an upcoming major version