public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Celia McInnis <mcinnisc@omnisig.com>
To: "David Robinson (AU)" <David.Robinson@citrix.com.au>
Cc: "'sourcenav@sources.redhat.com'" <sourcenav@sources.redhat.com>
Subject: Re: reading databases from perl?
Date: Mon, 09 Jul 2001 20:09:00 -0000	[thread overview]
Message-ID: <3B4A7316.B15C1575@omnisig.com> (raw)
In-Reply-To: <A364502829E6D3119BF400508B2D831F0197E15A@sydexch01.citrix.com.au>

Thanks. I was using the C db API - but found this inconvenient
(multi-platform). I am now using a system call from perl to dbdump. This
is at least a little better. Please keep me posted if you build a perl
module to read the db. (I probably should be using the tcl db api, but I
find tcl very cumbersome next to perl...).

Celia McInnis

"David Robinson (AU)" wrote:

> Hello Celia
>
> I have been reading the SN database externally, but not
> with perl. I previously did some hacking using dbdump,
> which is distributed with SN. At present I am trying to
> build a PHP extension module to read the database.
>
> Apparently you can also access the database using tcl;
> SN is mostly written in TCL.
>
> The database format is berkeley DB 1.85 (a very old format)
> which can be found at http://www.sleepycat.com/ .
>
> Perhaps you could build the static database library, link
> it into a shared library, then access it using perl.
>
> Regards
> David Robinson
>
> -----Original Message-----
> From: Celia McInnis [ mailto:mcinnisc@omnisig.com ]
> Sent: Sunday, 8 July 2001 14:28
> To: Source Navigator
> Subject: reading databases from perl?
>
> Can anyone tell me how I can read the source-navigator databases from
> perl?
>
> Thanks,
> Celia McInnis

  reply	other threads:[~2001-07-09 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09 15:44 David Robinson (AU)
2001-07-09 20:09 ` Celia McInnis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-07 21:23 Celia McInnis

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B4A7316.B15C1575@omnisig.com \
    --to=mcinnisc@omnisig.com \
    --cc=David.Robinson@citrix.com.au \
    --cc=sourcenav@sources.redhat.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).