The packet counter uses a PostgreSQL sequence that doesn't get reset when the packets table is truncated, causing inaccurate counts. This migration: - Creates an event trigger that automatically resets the packet counter sequence when the packets table is truncated - Adds a manual reset function reset_packet_counter() that can be called if needed - Improves the get_packet_count() function to properly handle when the sequence is at 0 After applying this migration, the counter will automatically reset to 0 whenever TRUNCATE is used on the packets table. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| gettext | ||
| gleam | ||
| repo | ||
| static | ||