Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: ovsqlite (Bo Lindbergh)
2. Re: ovsqlite (Bo Lindbergh)
3. Re: ovsqlite (Russ Allbery)
----------------------------------------------------------------------
Message: 1
Date: Sat, 19 Dec 2020 00:05:51 +0100
From: Bo Lindbergh <[email protected]>
To: [email protected]
Subject: Re: ovsqlite
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Quoth Julien ?LIE <[email protected]>:
>
> There's an issue with the second patch when SQLite is not installed
> (HAVE_SQLITE3 unset).
> The build fails because buffer_t is an unknown type in
> ovsqlite/ovsqlite-private.c (not defined in the ovsqlite/ovsqlite-private.h
> header when HAVE_SQLITE3 is unset).
Oops! All the actual code in ovsqlite-private.c should of course have
#ifdef HAVE_SQLITE3 / #endif around it.
/Bo Lindbergh
------------------------------
Message: 2
Date: Sat, 19 Dec 2020 04:39:19 +0100
From: Bo Lindbergh <[email protected]>
To: [email protected]
Subject: Re: ovsqlite
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Quoth Russ Allbery <[email protected]>:
>
> It feels like a great way to do overview that will be easier to maintain.
What parts of the current overview code are hard to maintain?
/Bo Lindbergh
------------------------------
Message: 3
Date: Fri, 18 Dec 2020 19:56:00 -0800
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: ovsqlite
Message-ID: <[email protected]>
Content-Type: text/plain
Bo Lindbergh <[email protected]> writes:
> Quoth Russ Allbery <[email protected]>:
>> It feels like a great way to do overview that will be easier to maintain.
> What parts of the current overview code are hard to maintain?
ovdb has historically required some porting to new versions of BerkelyDB,
although as the development pace of BerkeleyDB has stalled, it's come up
less. buffindexed is a neat idea, but it's had a fair number of bug
reports and I'm not 100% convinced that it's reliable against various
relatively rare problems.
I think tradindexed is relatively solid (of course, I would, since I wrote
the current incarnation of it), but it's also kind of slow and it's
conceptually wrong to roll one's own database when actual database engines
exist.
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 126, Issue 11
********************************************
