Toutsu/GmRelayBot
1
1
Fork 0
Code Issues 18 Pull Requests 1 Actions Packages Projects Releases 85 Wiki Activity

fix(db): make legacy telegram_* columns nullable for Discord multi-platform #103

Closed
Toutsu wants to merge 0 commits from fix/discord-nullable-telegram-columns into main
pull from: fix/discord-nullable-telegram-columns
merge into: Toutsu:main
Conversation 0 Commits - Files Changed -
Toutsu commented 2026-05-26 12:52:50 +03:00
Owner
Copy Link
Copy Source

Summary

Discord /newsession fails with PostgreSQL NOT NULL constraint violation on legacy telegram_* columns. This PR adds migration V023 to drop those constraints, allowing Discord (and future platforms) to create records without Telegram identifiers.

Changes

  • src/GmRelay.Bot/Migrations/V023__game_groups_telegram_chat_id_nullable.sql — ALTER TABLE dropping NOT NULL on:
    • game_groups.telegram_chat_id
    • game_groups.gm_telegram_id
    • players.telegram_id
  • Version synchronized to 3.0.10 across:
    • Directory.Build.props
    • compose.yaml
    • .gitea/workflows/deploy.yml
    • NavMenu.razor
    • DiscordProjectStructureTests.cs

Test plan

  • DiscordProjectStructureTests pass (8/8)
  • CI passes (format, build, tests, Trivy)
  • Deploy succeeds
  • Release published

Related

  • Fixes production error: null value in column "telegram_chat_id" violates not-null constraint
  • Follow-up to PR #102 (v3.0.9)
## Summary Discord `/newsession` fails with PostgreSQL `NOT NULL` constraint violation on legacy `telegram_*` columns. This PR adds migration V023 to drop those constraints, allowing Discord (and future platforms) to create records without Telegram identifiers. ## Changes - `src/GmRelay.Bot/Migrations/V023__game_groups_telegram_chat_id_nullable.sql` — ALTER TABLE dropping `NOT NULL` on: - `game_groups.telegram_chat_id` - `game_groups.gm_telegram_id` - `players.telegram_id` - Version synchronized to `3.0.10` across: - `Directory.Build.props` - `compose.yaml` - `.gitea/workflows/deploy.yml` - `NavMenu.razor` - `DiscordProjectStructureTests.cs` ## Test plan - [x] `DiscordProjectStructureTests` pass (8/8) - [ ] CI passes (format, build, tests, Trivy) - [ ] Deploy succeeds - [ ] Release published ## Related - Fixes production error: `null value in column "telegram_chat_id" violates not-null constraint` - Follow-up to PR #102 (v3.0.9)
Toutsu added 1 commit 2026-05-26 12:52:51 +03:00
fix(db): make legacy telegram_* columns nullable for Discord multi-platform
PR Checks / test-and-build (pull_request) Successful in 18m38s
Details
c955e1572f 
V023 migration drops NOT NULL constraints on:
- game_groups.telegram_chat_id
- game_groups.gm_telegram_id
- players.telegram_id

This allows Discord (and future platforms) to create players and
game_groups without legacy Telegram identifiers.

Bump version → 3.0.10

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Toutsu closed this pull request 2026-05-26 16:06:29 +03:00
Some checks are pending
PR Checks / test-and-build (pull_request) Successful in 18m38s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
area:bot
Telegram bot and worker logic
 area:data
Database schema, migrations and persistence model
 area:discord
Discord bot service and Discord adapter
 area:infra
Infrastructure, runtime and deployment
 area:miniapp
Telegram Mini App dashboard
 area:platform
Platform-neutral abstractions and adapter boundaries
 area:shared
Shared domain and rendering contracts
 area:web
Blazor web dashboard
 in-progress
В работе (issue взят агентом)
 next-up
Recommended immediate backlog
 pending-approval
Ждёт согласования плана решения
 platform:discord
Discord-specific behavior or adapter work
 platform:multi
Cross-platform or platform-neutral work
 platform:telegram
Telegram-specific behavior or adapter work
 priority:p0
Critical priority
 priority:p0
Блокирующий приоритет: задача должна быть выполнена до признания решения production-ready
 priority:p1
High priority
 priority:p2
Medium priority
 priority:p3
Lower priority
 security
Security-sensitive work
 type:bug
Bug fix or corrective work
 type:chore
Maintenance and supporting work
 type:feature
New product functionality
 type:refactor
Structural change without direct feature growth
 type:test
Testing and coverage work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Toutsu
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Toutsu/GmRelayBot#103
Delete Branch "fix/discord-nullable-telegram-columns"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?