From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: guile-pg 0.13 available
Date: Mon, 23 Dec 2002 20:31:17 -0800 [thread overview]
Message-ID: <E18Qgir-0000qG-00@giblet.glug.org> (raw)
tarball in:
http://www.glug.org/alt/
NEWS below. anyone play w/ lobs to implement "stored procedures" yet?
build-from-cvs programmers, please note HACKING blurb re docs maint.
thi
_______________________________________
- version 0.13 released 2002-12-24
- `terminating' slack
The heuristic fallback when lacking `scm_terminating' has been
replaced w/ a configure.in check for `terminating' in libguile.
If neither is available, on lob flush error, guile-pg writes to
stderr unconditionally. This is safer than unconditionally
calling scm_syserror (the previous approach), which may crash
guile in some circumstances.
- New (database postgres-types) proc: oid-type-name-cache CONN [FRESH?]
Documented in the manual, which now sports full extracted
docstrings (cheesy Commentary snapshots removed, too).
[excerpt ends here]
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
reply other threads:[~2002-12-24 4:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E18Qgir-0000qG-00@giblet.glug.org \
--to=ttn@giblet.glug.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.org \
/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).