yttcom.net
Backend / Tools / DB Viewer
yttcom.net
Domains / DB Viewer
v2.0 · 07.11.26
◇ 10-sys.db
systems/10-master/data/
records.db inbox.db transfers.db knowledge.db jurisdiction.db
10-sys decisions Row #181
Tables
decisions
198
domain
8
events
0
gov_archive
0
gov_archive_fts
0
gov_archive_fts_config
1
gov_archive_fts_data
4
gov_archive_fts_docsize
0
gov_archive_fts_idx
2
items
18
sessions
99
sqlite_sequence
5
transfers_log
0
decisions — Row #181
10-sys.db · systems/10-master/data/
id
181
system
date
08/25/26
subject
Fixed fix-log.html Could-not-find-original-line-to-update bug (v3.4)
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
181
detail
USR369 sent a screenshot showing a real live failure: editing an existing FIX-LOG entry ('Overseeing builder maintenance on HTML sheets.') and clicking Update Entry returned 'Could not find original line to update.' Confirmed the entry (dated 08/25/26 12:04, no #N id -- predates the concurrent v3.3 auto-number feature) genuinely still existed in the live file, unchanged. Root cause: doUpdate()/toggleStatus() both searched for a copy of the line captured whenever the page/list was last rendered (_rawLines[idx]) inside a freshly re-fetched file -- any drift between the two makes the exact-string search fail closed. Fixed both functions to re-parse the FRESHLY fetched content at submit time and locate the real row inside that same fresh text -- by persisted #N id when present, or by matching date+system+task+name for older entries without an id -- so the search string is always guaranteed to come from the same text being searched. v3.1->v3.4 bump.
▼ Show timestamps
created_at
2026-08-25 12:27:49
Backend Domains Panel DB Viewer Transfers
Backend Tools DB Viewer DB Admin Server Map File Editor Backend Tools DB Viewer DB Admin Server Map File Editor