yttcom.net
Backend / Tools / DB Viewer
yttcom.net
Domains / DB Viewer
v2.0 · 07.11.26
◇ 40-sys.db
systems/40-server/data/
records.db inbox.db transfers.db knowledge.db jurisdiction.db
40-sys decisions Row #97
Tables
decisions
189
domain
0
events
10
gov_archive
0
gov_archive_fts
0
gov_archive_fts_config
1
gov_archive_fts_data
2
gov_archive_fts_docsize
0
gov_archive_fts_idx
0
items
3
sessions
82
sqlite_sequence
5
transfers_log
0
decisions — Row #97
40-sys.db · systems/40-server/data/
id
97
system
date
08/20/26
subject
CLOSE.php session_recorded false-fail -- root cause found and fixed (confirmed cross-system, K380)
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
97
detail
Confirmed real (not isolated to my since-guess): Admin 00 independently hit the identical false-fail last night, documented as K380. Root cause: the sys_db sessions INSERT in CLOSE.php stored $since RAW (whatever human format arrived, e.g. 08/18/26 5:02pm PT), while close_verify's own SELECT (called immediately after, same request) compared opened_at against normalize_since_pt($since) -- a normalized Y-m-d H:i:s format. SQLite does plain string comparison, no date coercion (same class of bug the file's own K-VERIFY-01 comment already warned about) -- 08/18/26... sorts before 2026-08-18... as a string, so opened_at >= since_norm was false on literally every close. Fixed by normalizing $since before storing it, so stored and queried values use the same format.
▼ Show timestamps
created_at
2026-08-20 19:16:41
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