From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 8E5A33858C51 for ; Sat, 9 Apr 2022 02:26:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8E5A33858C51 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-245-yn7t-HXLPsaVPffJkOFtfg-1; Fri, 08 Apr 2022 22:26:22 -0400 X-MC-Unique: yn7t-HXLPsaVPffJkOFtfg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A7100185A794; Sat, 9 Apr 2022 02:26:21 +0000 (UTC) Received: from redhat.com (unknown [10.2.16.64]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 67097111F3D9; Sat, 9 Apr 2022 02:26:11 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1nd0ni-0001Ze-Ij; Fri, 08 Apr 2022 22:26:10 -0400 Date: Fri, 8 Apr 2022 22:26:10 -0400 From: "Frank Ch. Eigler" To: Serhei Makarov Cc: Keith Seitz , Bunsen Subject: Re: bunsen (re)design discussion #0: list of topics, review of terminology Message-ID: <20220409022610.GG23295@redhat.com> References: <58451c27-bd3b-4305-b894-3862dfe76808@www.fastmail.com> <699471ef-d43a-4d36-8ae9-5b2f657271a0@www.fastmail.com> <1dda2480-ebb8-489a-8151-09c7e75764e1@redhat.com> <20220409015645.GF23295@redhat.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: bunsen@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bunsen mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2022 02:26:24 -0000 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