fix(plexmatch): 修复 PostgreSQL 历史记录查询 - #370
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #365 中的 PostgreSQL 报错可以由 PlexMatch v2 的历史补全查询稳定复现:
tmdbid.is_not(0)会生成非法的IS NOT 0。普通入库事件不经过该查询,问题仅在启用“补全 .plexmatch 文件”后触发。本 PR 将数值筛选改为
IS NOT NULL AND != 0,在 PostgreSQL 与 SQLite 下保持一致语义,并发布 PlexMatch v21.3。历史 v1 插件与版本保持不变。同时修正 Release workflow 的同名插件目录选择与版本线基准:
package.json只打包plugins/,package.v2.json只打包plugins.v2/,避免 v2 变更重建历史 v1 资产。验证:
Fixes #365