Passing only okvs object and a prefix will make it much more difficult to switch backend.
I don't see how. That should be part of the purpose of the "home" argument to "okvs" procedure (or perhaps another argument "backend"), like the way that ODBC connection strings work.
If one store symbols in the nstore they should be able to query them. It is useful to differentiate symbols from variables.
The context always separates them: a symbol on one side is a key, on the other side it's data. I see no possibility of ever confusing them.
I disagree. It will force to think about the order in which variables appear in nstore-select and nstore-select-where.
Fair point. In that case, return an alist (which is a good way to represent a tuple with named attributes in Scheme generally).
John Cowan
http://vrici.lojban.org/~cowan xxxxxx@ccil.orgHumpty Dump Dublin squeaks through his norse
Humpty Dump Dublin hath a horrible vorse
But for all his kinks English / And his irismanx brogues
Humpty Dump Dublin's grandada of all rogues. --Cousin James