public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Serhei Makarov <me@serhei.io>
Cc: Keith Seitz <keiths@redhat.com>, Bunsen <bunsen@sourceware.org>
Subject: Re: bunsen (re)design discussion #0: list of topics, review of terminology
Date: Fri, 8 Apr 2022 22:26:10 -0400	[thread overview]
Message-ID: <20220409022610.GG23295@redhat.com> (raw)
In-Reply-To: <ffc939d0-ae6e-4d5f-b88b-bbfad21b9811@www.fastmail.com>

Hi -

> > That should be straightforward with the new git/sqlite scheme too.
> > One can freeze a git repo for fixed testing, or one can edit one
> > under testsuite control.  And one can easily query the resulting
> > datasets for expected values.  Should be no problem at all for at
> > least the analysis side of the house.
>
> Sure, indeed sticking a frozen sample db into the testsuite might
> be essential if we end up designing a schema that is an API,
> then end up evolving the schema in a way that requires migrations,
> then an existing copy of the db will be an important data source
> to test against.

(I was not talking about including a frozen version of the sqlite
database, only of the git testlog repo ... but whatever, all is
possible.)


> [...]
> In any case, after digesting Frank's sample code for sqlite migration,
> I have a clearer idea of what pieces to adopt in a way that keeps
> continuity with the existing functionality.
> I'll do my own quick-experiment-in-a-separate branch to clarify
> what I want from the structure.

Looking forward to it!


- FChE


      reply	other threads:[~2022-04-09  2:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 18:59 Serhei Makarov
2022-03-07 19:03 ` Serhei Makarov
2022-04-07 16:57   ` Keith Seitz
2022-04-08 23:13     ` Serhei Makarov
2022-04-09  1:56       ` Frank Ch. Eigler
2022-04-09  2:22         ` Serhei Makarov
2022-04-09  2:26           ` Frank Ch. Eigler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220409022610.GG23295@redhat.com \
    --to=fche@redhat.com \
    --cc=bunsen@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=me@serhei.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).