16 commits

Author	SHA1	Message	Date
G30	c0d09a5de9	fix: list publicly shared read-only notes in the Read Only view (#27637)	2026-08-17 01:40:56 -06:00
Timothy Jaeryang Baek	20647bd2d5	chore: format	2026-07-27 00:12:47 -04:00
Timothy Jaeryang Baek	1f0dc90abe	refac	2026-07-26 18:06:03 -04:00
Classic298	699d512e2f	perf: drop redundant session.refresh calls after commit across the model layer (#27381) ... Both session factories run with expire_on_commit=False, so ORM objects keep their attribute values after commit. Every session.refresh issued right after a commit therefore re-SELECTed a row whose values the session already held, including full chat JSON blobs and user settings, purely to overwrite identical data. Fifty such calls existed across the model layer, covering nearly every write path in the app (chat inserts, title updates, pin/archive toggles, user role and settings updates, tool, prompt, function, model, file, tag, feedback, memory, automation and grant writes). All fifty are removed. The only refreshes with an actual job were the two update-then-reload paths in tools and skills, where a Core UPDATE statement bypasses the identity map; those now use session.get(..., populate_existing=True), which guarantees a fresh row in one SELECT whether or not the row was already present in the session (the previous code issued get plus refresh, two SELECTs, on the default configuration). Benchmark (real SQLite DB, per write): | write path | before | after | | --- | --- | --- | | chat title update, ~600 KB chat blob | 2.08 ms | 1.24 ms | | user role update, small row | 1.21 ms | 0.68 ms | On Postgres each removed refresh is additionally a network round trip. The chat-blob case also skips re-parsing the entire JSON document per write. Functionally verified against a fresh database: user insert, role and settings updates, chat insert (including the server-default meta column, which is always provided client-side), title update and pin toggle, tool insert and the Core-update reload path, tag insert and the prompt insert flow that pins version_id after history creation all return correct values and persist correctly.	2026-07-23 18:08:00 -05:00
Timothy Jaeryang Baek	6d0295588e	refac: modernize type annotations (PEP 604 / PEP 585)	2026-05-12 17:10:15 +09:00
Timothy Jaeryang Baek	25898116ea	chore: format	2026-04-12 18:12:59 -05:00
Timothy Jaeryang Baek	27169124f2	refac: async db	2026-04-12 14:22:11 -05:00
Timothy Jaeryang Baek	945275faae	refac	2026-03-22 06:58:58 -05:00
Timothy Jaeryang Baek	de3317e26b	refac	2026-03-17 17:58:01 -05:00
Timothy Jaeryang Baek	345f3e3559	refac	2026-02-25 15:15:59 -06:00
Timothy Jaeryang Baek	3d99de6771	enh: access grant level perms	2026-02-23 15:49:05 -06:00
Timothy Jaeryang Baek	8c485b260f	refac	2026-02-19 16:53:21 -06:00
Timothy Jaeryang Baek	3dd44c4f19	refac	2026-02-18 15:23:50 -06:00
Timothy Jaeryang Baek	589c4e64c1	refac	2026-02-13 13:56:29 -06:00
Timothy Jaeryang Baek	f376d4f378	chore: format	2026-02-11 16:24:11 -06:00
Timothy Jaeryang Baek	42763cbbd8	enh: access grants table	2026-02-08 21:21:25 -06:00