From 9098f888fc0bae9ce9634bd5c0ae9f9f1738da23 Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Thu, 5 Mar 2026 00:08:09 +0000 Subject: [PATCH] naked SQL - online edit of handbook/troggle/trogspeculate.html --- handbook/troggle/trogspeculate.html | 1 + 1 file changed, 1 insertion(+) diff --git a/handbook/troggle/trogspeculate.html b/handbook/troggle/trogspeculate.html index 30fa2e14d..f45413cbd 100644 --- a/handbook/troggle/trogspeculate.html +++ b/handbook/troggle/trogspeculate.html @@ -131,6 +131,7 @@ could mean that we could gain. But we could move to a read-only system where the only writing happens on data-import. Then we could use python 'pickle()' or 'json()' read-only data structures, but we would need to create all our own indexing and cross-referencing code (which is a much bigger job* than you might think - in fact, it is impossible in a standard wsgi/asgi architecture where there is no shared memory between users and each session is independent). +

[However, in 2026 an AI can cope with this. This has not gone unnoticed: Raw+DC: The ORM pattern of 2026?.]

There would be more lower-level code, but the different segments of the system could be in caving-sensible modules not django-meaningful modules. And we would not have all the extra