sco.storage
Methods and entrypoints for sco.storage.
sco_storage_v1
Section titled “sco_storage_v1”Source: sco_storage.h, implementation, layout pin.
One database, transaction and cursor namespace per plugin, not per thread. Any thread can use the plugin’s transaction/cursor, but concurrent calls serialize. Keys are 1–255 bytes; values 0–1 MiB; at most 64 open cursors per plugin. The host may allocate copies, statements and cursors; callers never receive SQLite memory. Database quota and statement budgets are host-configured, not fixed by the method table. A budget failure is FAILED, not an API cancellation callback. For SQL restrictions and persistence settings see storage.
Contract records
Section titled “Contract records”- sco_storage_v1.begin
- sco_storage_v1.close
- sco_storage_v1.column
- sco_storage_v1.column_count
- sco_storage_v1.column_name
- sco_storage_v1.commit
- sco_storage_v1.del
- sco_storage_v1.exec
- sco_storage_v1.get
- sco_storage_v1.last_error
- sco_storage_v1.next_key
- sco_storage_v1.put
- sco_storage_v1.query
- sco_storage_v1.rollback
- sco_storage_v1.step