[GH-ISSUE #195] Creating a new pool corrupts data in backend #125

New issue

Closed

opened 2026-02-27 19:16:57 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 19:16:57 +03:00

Owner

Originally created by @EddieTheCubeHead on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/195

C:...\Stagnum\server\src\api\pool\dependencies.py:242: SAWarning: New instance <PlaybackSession at 0x212a383a6f0> with identity key (<class 'database.entities.PlaybackSession'>, ('username',), None) conflicts with persistent instance <PlaybackSession at 0x212a33a2db0> (This warning originated from the Session 'autoflush' process, which was invoked automatically in response to a user-initiated operation.)
return session.scalar(select(Pool).where(

Originally created by @EddieTheCubeHead on GitHub (Apr 6, 2024). Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/195 C:\...\Stagnum\server\src\api\pool\dependencies.py:242: SAWarning: New instance <PlaybackSession at 0x212a383a6f0> with identity key (<class 'database.entities.PlaybackSession'>, ('username',), None) conflicts with persistent instance <PlaybackSession at 0x212a33a2db0> (This warning originated from the Session 'autoflush' process, which was invoked automatically in response to a user-initiated operation.) return session.scalar(select(Pool).where(