3 databases in 3 days
hga@xxxxxx
(30 Sep 2019 00:36 UTC)
|
Support for Scheme standards and implementations
Lassi Kortela
(30 Sep 2019 08:11 UTC)
|
Re: Support for Scheme standards and implementations
hga@xxxxxx
(30 Sep 2019 11:25 UTC)
|
Scheme implementations and portability
Lassi Kortela
(30 Sep 2019 13:14 UTC)
|
Re: Scheme implementations and portability
John Cowan
(30 Sep 2019 19:27 UTC)
|
Scheme implementations, portability, FFIs
Lassi Kortela
(30 Sep 2019 21:16 UTC)
|
Re: Scheme implementations, portability, FFIs
John Cowan
(30 Sep 2019 22:10 UTC)
|
JDBC
Lassi Kortela
(30 Sep 2019 13:15 UTC)
|
Re: JDBC
hga@xxxxxx
(30 Sep 2019 13:24 UTC)
|
Re: JDBC and subprocess protocol
Lassi Kortela
(30 Sep 2019 14:29 UTC)
|
Re: JDBC and subprocess protocol
hga@xxxxxx
(30 Sep 2019 15:16 UTC)
|
Re: JDBC and subprocess protocol
Lassi Kortela
(30 Sep 2019 15:47 UTC)
|
Re: JDBC and subprocess protocol
Lassi Kortela
(30 Sep 2019 15:55 UTC)
|
Re: JDBC
John Cowan
(30 Sep 2019 15:10 UTC)
|
Re: JDBC
Lassi Kortela
(30 Sep 2019 15:26 UTC)
|
Re: JDBC
Lassi Kortela
(30 Sep 2019 15:34 UTC)
|
sdbi design in detail and MariaDB CONNECT hga@xxxxxx (30 Sep 2019 16:14 UTC)
|
Re: sdbi design in detail and MariaDB CONNECT
Lassi Kortela
(30 Sep 2019 16:28 UTC)
|
Re: sdbi design in detail and MariaDB CONNECT
John Cowan
(30 Sep 2019 20:25 UTC)
|
Re: JDBC
John Cowan
(30 Sep 2019 16:44 UTC)
|
Re: JDBC
Lassi Kortela
(30 Sep 2019 20:52 UTC)
|
Re: JDBC
Alaric Snell-Pym
(01 Oct 2019 09:26 UTC)
|
Re: JDBC
hga@xxxxxx
(01 Oct 2019 09:55 UTC)
|
Re: JDBC
Alaric Snell-Pym
(01 Oct 2019 11:09 UTC)
|
sdbi supports "databases" with text query languages that return rectangular results
hga@xxxxxx
(01 Oct 2019 12:22 UTC)
|
Re: sdbi supports "databases" with text query languages that return rectangular results
John Cowan
(01 Oct 2019 16:10 UTC)
|
> From: Lassi Kortela <xxxxxx@lassi.io> > Date: Monday, September 30, 2019 10:34 AM >> To some extent this whole discussion is moot :) [ CONNECT ] is >> supported by some MariaDB client we'll end up making anyway. A JDBC >> suprocess is a matter of coding one, so it's the problem of whoever >> will code it :) > > This sounds superficially like we're arguing, but the bigger picture > here is that we have a very sound design for the DB framework. Thanks, but it's not quite to that point, there's still a lot of Sidney Harris "THEN A MIRACLE OCCURS" steps to be more explicit about ^_^. That said, my design intuition is pretty good by now. > It permits either implementation strategy easily, and we're just > arguing about whether to plug in some databases one way or another way > or do both. Exploration and individual motivation will automatically > find approach(es) that work; the point is to make sure the framework > itself can handle socket, in-process and subprocess implementations so > all avenues are open whenever someone wants to add a database. This is a very good point. To use the current (iffy) hierarchy of sdbi for this, I have, for example, running in bare direct prototype form: (sdbi connector ffi sqlite3) And: (sdbi connector net postgresql) To which Lassi is proposing to add something like: (sdbi connector subprocess-jdbc) Which would be used as: (sdbi connector subprocess-jdbc [obscure database]) Perforce, there will be a generic protocol between the connector layer and the one below it, although in John's favor I need to look at the PostgrSQL and Widenius wire protocols for ideas. The latter ... however much it'll gain us with CONNECT, as far as I know it needs a champion to be implemented any time soon. As for CONNECT (https://mariadb.com/kb/en/library/connect/), does it represent a single point of project institutional failure like I perceived SQLite3 to be? I again ask this to determine how much sdbi should be influenced by a potential mayfly. In the meanwhile I'm mining it for ideas. - Harold