No, I meant "(r)dbms" to replace "tech-stack".  It's not the stack that matters, it's what you get to at the end of it.  In any case, to most people "stack" includes things like the front end, which are out of scope here.

On Tue, Oct 1, 2019 at 4:06 PM <xxxxxx@ancell-ent.com> wrote:
From: John Cowan <xxxxxx@ccil.org>
Date: Tuesday, October 01, 2019 2:31 PM

On Tue, Oct 1, 2019 at 12:42 PM <xxxxxx@ancell-ent.com> wrote:


It is John's Simple SQL API with "sql-" replaced with "sdbi-", and the following changes:

New opaque data type, tech-stack, and that's not a good name for the stack of e.g. "subprocess jdbc db2", suggestions including replacing "stack" are solicited.

I like "rdbms", where "r" stands for "rectangular", or in the alternative just "dbms".

To replace what?  sdbi?  In any case, "rdbms" would be deliberately confusing, and "dbms" might as well be "db" to save typing.  If it's for the whole API, it should be "db" as a more general term than "dbms", there's more to sdbi than the database.  Although I suppose you could say the whole tech stack is a database management system of its own.

sdbi -> dbi would be fine if you want to shorten the former.  You're already typing Scheme code, so that's assumed.

What I'd really like is a better name for "stack" / "tech-stack", which encompasses everything needed to get to the database as well as it.

Everything following, which starts with (sdbi-read result-set) -> list, is unchanged except for the"sql-" -> "sdbi-" swap.

I think that the blob API should be generalized to reading arrays and multisets somehow.  In both cases the idea is that the content of a cell (row-column pair) may be too large to just return all at once. 

Noted for when we get serious about that part of the API.

- Harold