OverviewFilesCommitsIssuesDocsReleasesPeers

opencog-atomspace-storage commits / 56073b3

Remove stale, unpatched commits.
The fix was made maybe a month ago approx. The comments were never cleaned up
56073b350a94c1d5569cd65cfab1b07ebc4d3a73
by Linas Vepstas <linasvepstas@gmail.com> · 2026-01-18T04:05:08.000Z

Changed files (1) +0 -18

opencog/persist/api/opencog/persist.scm +0 -18
……@@ -222,15 +222,6 @@
222222 `fetch-value` to get only one Value.
223223 `store-atom` to store all Values.
224224"
225 ; Need to use cog-set-value! here, instead of cog-set-value! in order
226 ; to get correct behavior for working with frames. This is due to
227 ; an unpatched bug: calling cog-set-value! in some frame where
228 ; the storage node is only in a lower frame causes a COW of that
229 ; StorageNode into that frame. But the COW is a copy, and that
230 ; copy isn't actually open. So cog-set-value! just bypasses the COW
231 ; and everything works. I'm not sure what the best long-term fix
232 ; for this is. At any rate, XXX FIXME.
233 ;
234225 ; For backwards compat, throw a C++ exception if not open.
235226 (if STORAGE
236227 (cog-set-value! STORAGE (*-fetch-atom-*)
……@@ -403,15 +394,6 @@
403394 `store-value` to store just one Value.
404395 `fetch-atom` to fetch all Values on an Atom.
405396"
406 ; Need to use cog-set-value! here, instead of cog-set-value! in order
407 ; to get correct behavior for working with frames. This is due to
408 ; an unpatched bug: calling cog-set-value! in some frame where
409 ; the storage node is only in a lower frame causes a COW of that
410 ; StorageNode into that frame. But the COW is a copy, and that
411 ; copy isn't actually open. So cog-set-value! just bypasses the COW
412 ; and everything works. I'm not sure what the best long-term fix
413 ; for this is. At any rate, XXX FIXME.
414 ;
415397 ; For backwards compat, throw a C++ exception if not open.
416398 (if STORAGE
417399 (cog-set-value! STORAGE (*-store-atom-*) ATOM)