Repository navigation
release: PostgreSQL Database Provider 3.0.4 - #10
Merged
Merged
Conversation
added 3 commits
October 17, 2026 15:25
- Nueva migracion que normaliza DateCreated no finito o minimo en BaseItems. - Normalizacion de los centinelas DateTime y DateTimeOffset antes de escribir en PostgreSQL. - Busqueda de titulos con ILIKE en Name, OriginalTitle y SortName. - SortName incluido en la busqueda rapida y en su indice GIN trigram. - Pruebas de normalizacion de fechas y de reescritura de busquedas.
- La cache de consultas bufferiza las columnas de fecha como UTC y el lector restaura DateTimeKind: el cliente Android recibia la fecha sin zona horaria, la sustituia por su valor minimo y fallaba al convertirla. - Las filas duplicadas se resuelven con ON CONFLICT ... DO UPDATE sobre la clave primaria en lugar de DO NOTHING, que informa 0 filas afectadas y EF Core interpreta como DbUpdateConcurrencyException. - El proveedor fija QuerySplittingBehavior en SingleQuery, igual que el proveedor SQLite de Jellyfin, y deja de llenar el log con MultipleCollectionIncludeWarning. - Pruebas de regresion de los tres casos y ajuste de las pruebas de reescritura SQL.
El prefetch es best effort y comparte un unico slot en todo el proceso, asi que puede descartarse cuando el runner esta cargado o coincide con otra prueba. La prueba repite el escenario en lugar de depender de un unico intento.
BORNIOS
force-pushed
the
release/3.0.4
branch
from
October 17, 2026 22:43
3d5e7e9 to
c22c9ab
Compare
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.
Español
PostgreSQL Database Provider 3.0.4
DateTimeKind.Utcal bufferizar, el cliente recibía la fecha sin zona horaria y la sustituía por su valor mínimo. Las columnas de fecha se bufferizan como UTC y el lector restaura elKindcomo segunda barrera.DateCreatedno finito o mínimo ya guardado enBaseItems, junto con la normalización de los centinelasDateTimeyDateTimeOffsetantes de escribir.ILIKEsobreName,OriginalTitleySortName, con índice trigram sobreSortName).ON CONFLICT ... DO UPDATEsobre la clave primaria, que conserva la fila guardada y cuenta como una fila afectada, en lugar deDO NOTHING, que EF Core interpretaba como conflicto de concurrencia.QuerySplittingBehaviorenSingleQuery, igual que el proveedor SQLite de Jellyfin, y deja de llenar el log conMultipleCollectionIncludeWarning.Validación
English
PostgreSQL Database Provider 3.0.4
DateTimeKind.Utcwhile buffering, so the client received dates without a time zone and replaced them with its minimum value. Date columns are buffered as UTC and the reader restores theKindas a second safeguard.DateCreatedvalues already stored inBaseItems, plus normalization ofDateTimeandDateTimeOffsetsentinels before writing.ILIKEoverName,OriginalTitle, andSortName, with a trigram index onSortName).ON CONFLICT ... DO UPDATEon the primary key, which keeps the stored row and counts as one affected row, instead ofDO NOTHING, which EF Core reported as a concurrency conflict.QuerySplittingBehaviortoSingleQuery, matching Jellyfin's SQLite provider, and stops flooding the log withMultipleCollectionIncludeWarning.Validation