From: Neil Jerram <neil@ossau.uklinux.net>
To: linasvepstas@gmail.com
Cc: Andy Wingo <wingo@pobox.com>, guile-user <guile-user@gnu.org>
Subject: Re: new sqlite binding
Date: Sun, 28 Nov 2010 11:51:58 +0000 [thread overview]
Message-ID: <87r5e51u4n.fsf@ossau.uklinux.net> (raw)
In-Reply-To: AANLkTimYg_ERqhvfbc9MAqwpMsn0r-uihdyx2vGwPE2B@mail.gmail.com
Linas Vepstas <linasvepstas@gmail.com> writes:
> Hi,
>
> On 25 November 2010 08:12, Andy Wingo <wingo@pobox.com> wrote:
>>
>> I just hacked up a new binding to sqlite. It works with sqlite3 and
>> Guile 1.9/2.0. Check it out at:
>>
>> http://gitorious.org/guile-sqlite3
>
> I'd like to horn in on Andy's glory by advertising guile-dbi
>
> http://home.gna.org/guile-dbi/
>
> which provides a consistent set of bindings to three different
> systems: Postgres, MySQL and SQLite3
>
> Like Andy, I solicit patches/fixes/extensions.
At the moment, I assume guile-dbi involves building C glue code?
I like the backend-independence of the DBI interface, and I also like
Scheme code that I can just drop in and use without needing to compile
any C.
So, personally, I'd generally favour merging these two bindings, and
evolving the other DBD implementations to use the new FFI. Although
probably also keeping the existing glue code implementation, as an
alternative to support older Guiles.
Regards,
Neil
next prev parent reply other threads:[~2010-11-28 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 14:12 new sqlite binding Andy Wingo
2010-11-27 6:20 ` Linas Vepstas
2010-11-28 11:51 ` Neil Jerram [this message]
2010-11-28 16:08 ` Linas Vepstas
2010-11-29 21:11 ` Andy Wingo
2010-11-29 20:50 ` Andy Wingo
2010-12-03 18:35 ` Neil Jerram
2010-12-07 4:46 ` Linas Vepstas
2010-12-07 9:50 ` Neil Jerram
2010-11-29 20:43 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5e51u4n.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@gnu.org \
--cc=linasvepstas@gmail.com \
--cc=wingo@pobox.com \
/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).