From: "Arthur A. Gleckler" <xxxxxx@speechcode.com>
Date: Wednesday, October 02, 2019 4:10 PM

On Wed, Oct 2, 2019 at 10:52 AM <xxxxxx@ancell-ent.com> wrote:
 
The blessed transaction log could be put on GitHub, it only adds records to the end.  For more formal and general backup, it would be easy to set up a minimum size 500GB 108 US$/year rsync.net account with the keys to the kingdom being spread out to e.g. Arthur and whomever else makes sense.  Very easy to use, ssh, scp, and rsync of course, can even host git repositories, albeit without any frills.  There's also a FreeBSD ZFS snapshot facility that by default does the last 7 days. 

I'm afraid that I don't understand.  Based on the subject line, it sounds like this would be for storing a registry of data types supported by the proposed serialization mechanism.  Do we really need more than a simple text file, or perhaps a Git repo, for that?

I've been trying to keep up with the discussion on this list, but I'm worried that I've missed something.  If so, I apologize.

This is for my multi-dimensional database of types for the Scheme Database Interface (sdbi).  It needs to keep track of the various relevant data types specific R6RS and R7RS Scheme implementation support that can be "directly" stored in a database, the types supported by the databases we support in more than a generic fashion, and then capture information about converting both ways. 

"More than a generic fashion" is for when you're not doing a greenfields project, or the automagic conversion does not satisfy your requirements.  And I'm thinking the database may including code stored as text, for example in situations where "normal" conversions won't work because of a "quirk" in either a Scheme implementation or database.

Basically, I want as much of the conversion code to be auto-generated as possible from one master source.

And when John brought up the issue of properly backing up such a database, well, one Git repo is not enough, nor is it ideal for a raw database.  I thought I'd offer to facilitate and fund a reliable place to backup all sorts of smallish Scheme standards, I'm ... really hard core about backups, e.g. a few hours ago I finished this months' full backup to LTO tapes.  You were CC'ed because you at minimum would also have full access to this account, to avoid things like a repeat of the R6RS process data loss, and would likely have other useful things to backup to a rsync.net minimum 500GB size account.

- Harold