jim 64a914c14d fix: tolerate ~5s timestamp drift in UpdateNoteReplyText
The API returns reply timestamps that are ~1s ahead of what -collect
originally stored, so an exact TimeStamp match in the UPDATE was
hitting zero rows for every note - the API call worked, the reply
text came back, but nothing landed in the DB. Match within +-5s
instead. Also return rowsAffected from UpdateNoteReplyText and
report it separately from notes-seen in the summary so misses are
visible.
2026-05-07 14:10:37 -05:00
2025-11-24 11:58:55 -06:00
.
2026-03-26 00:35:24 -05:00
2026-05-06 16:51:56 -05:00
.
2026-03-26 00:35:24 -05:00
.
2026-03-26 00:35:24 -05:00
.
2026-03-26 00:35:24 -05:00
.
2026-03-26 00:35:24 -05:00
.
2026-03-26 00:35:24 -05:00
2024-10-30 09:14:53 -05:00
2026-05-06 14:50:30 -05:00
S
Description
No description provided
136 MiB
Languages
C# 98.1%
PLpgSQL 1.9%