Email list hosting service & mailing list manager


New draft (#3) of SRFI 168: Generic Tuple Store Database Arthur A. Gleckler 02 Jun 2019 17:51 UTC

I've just published draft #3 of SRFI 168.  It was submitted by
Amirouche Boubekki, author of the SRFI.

  <https://srfi.schemers.org/srfi-168/>

Here is Amirouche's summary of the changes in this draft:

  - okvs must manage the transaction

  - nstore-everything was removed and replaced by okvs-debug

  - nstore takes a prefix parameter that must be a list, to allow
  to use the same okvs to store multiple abstractions.

  - tuple items are passed as list instead of rest parameters

  - Actually, allow pagination but without support for reverse?
  because the order in which bindings are returned is not
  predictable (except if you forced a particular index). That is
  nstore-from only support offset and limit.

  - nstore-from and nstore-where are not decorated with
  okvs-transactional because it would give the false impression
  that it is useable as-is in the REPL. Unlike the other
  procedures in this specification, this two procedure return
  generator which "valid" as long as the transaction is
  running. Once the transaction is commited or rollbacked, it is
  not anymore possible to retrieve the results.

  - Update sample code

Here's the diff:

  <https://github.com/scheme-requests-for-implementation/srfi-168/compare/133b338e4e8c0c65499c9709d7189d9a066cfba6..d103ffc795f81259e30a5d798c65f6046ee1070b>

Regards,

SRFI Editor