Marcello Costagliola 74bdbb0764 Keep the room_id index and date the migration in UTC ...

The composite index doesn't serve everything the room_id one did. In
SQLite that index is (room_id, rowid), so it also reads a room's messages
in id order, and it is the narrower one to count a room with. Keeping both,
as memberships already does, leaves those lookups as they were.

The migration was named after local time, two hours ahead of the UTC
timestamp Rails generates; it now carries a UTC one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NuTtwJKhb77Dv7EQqv2C3C

2026-10-05 01:39:36 +02:00

..

migrate

Keep the room_id index and date the migration in UTC

2026-10-05 01:39:36 +02:00

schema.rb

Keep the room_id index and date the migration in UTC

2026-10-05 01:39:36 +02:00