用户管理页面，当用户超过一页的数量的时候，往下拉刷新之后，下一页的第一条数据会跟上一页的最后一条数据重复

[HanBBQovo]

[github-actions]

Thank you for reporting this issue.

Analysis:

I've traced the bug to the cursor-based pagination implementation in src/repository/user.ts (lines 168-173). The issue is related to timestamp precision loss during the pagination cursor round-trip.

Root cause:

The cursor pagination uses a composite key comparison:

// src/repository/user.ts:171-172
sql`(${users.createdAt}, ${users.id}) > (${cursorDate.toISOString()}::timestamptz, ${cursor.id})`

The problem occurs because:

1. PostgreSQL stores timestamps with microsecond precision (e.g., 2024-01-15 10:30:45.123456+00)
2. When building the next cursor (line 215), the timestamp is converted to JavaScript Date which only has millisecond precision
3. The ISO string conversion (toISOString()) loses microseconds (e.g., becomes 2024-01-15T10:30:45.123Z)
4. On the next page request, this truncated timestamp is used in the comparison
5. Since the truncated timestamp (10:30:45.123) is actually less than the original (10:30:45.123456), the same record passes the > comparison and gets included in the next page

Affected code:

• src/repository/user.ts:168-173 - Cursor comparison condition
• src/repository/user.ts:213-216 - Cursor construction from last record

Potential fix directions:

1. Use >= comparison and explicitly exclude the cursor ID: WHERE (created_at > cursor_time) OR (created_at = cursor_time AND id > cursor_id)
2. Alternatively, fetch the raw timestamp string from PostgreSQL instead of converting through JavaScript Date

---

Automated response from Claude AI