From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Joshua Branson via General Guile related discussions
<guile-user@gnu.org>
Cc: guile-sources@gnu.org, Joshua Branson <jbranso@dismail.de>
Subject: Re: Guile-PG 0.49 available
Date: Sun, 27 Dec 2020 21:26:38 -0500 [thread overview]
Message-ID: <87h7o6oech.fsf@gnuvola.org> (raw)
In-Reply-To: <rsba14$t5f$3@ciao.gmane.io> (Joshua Branson via General Guile related discussions's message of "Sun, 27 Dec 2020 19:48:30 -0500")
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
() Joshua Branson via General Guile related discussions <guile-user@gnu.org>
() Sun, 27 Dec 2020 19:48:30 -0500
May I ask how this differs from guile-squee? Is it "faster"?
Can't say -- i've never used guile-squee, personally. However,
a brief scan of the guile-squee homepage tells me that Guile-PG
is "more", in the sense of offering not only libpq wrapping, but
also other modules related to working w/ PostgreSQL, as well as
documentation:
http://www.nongnu.org/guile-pg/doc/index.html
OTOH, for many people "less is more". :-D
I suppose i should look into guile-squee some more, especially
if/how it handles lobj (large objects) and ports for Guile 2.2
and onward. Any hints on that topic most welcome!
--
Thien-Thi Nguyen -----------------------------------------------
(defun responsep (query) ; (2020) Software Libero
(pcase (context query) ; = Dissenso Etico
(`(technical ,ml) (correctp ml))
...)) 748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 219 bytes --]
prev parent reply other threads:[~2020-12-28 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 5:57 Guile-PG 0.49 available Thien-Thi Nguyen
2020-12-28 0:48 ` Joshua Branson via General Guile related discussions
2020-12-28 2:26 ` Thien-Thi Nguyen [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
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=87h7o6oech.fsf@gnuvola.org \
--to=ttn@gnuvola.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
--cc=jbranso@dismail.de \
/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).