From: Leslie Mikesell <les@Mcs.Net>
To: scrappy@hub.org
Cc: les@Mcs.Net
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [QUESTIONS] ndbm emulation library?
Date: Fri, 6 Mar 1998 12:07:40 -0600 (CST)
Message-ID: <199803061807.MAA05889@Mercury.mcs.net> (raw)
In-Reply-To: <Pine.NEB.3.95.980306123817.26524Q-100000@hub.org>
> > > I'm confused, but...why would you want to do this vs using the
> > > standard libpq interface?
> >
> > I've already got apps using ndbm (and getting occasional file
> > corruption). I'd like to fix this and get the benefits of
> > multi-host access and the ability to write new code to access
> > the same data in all the ways possible with pgsql. If we had
> > a wrapper around libpq with ndbm emulation it would be as simple
> > as re-linking my old apps and migrating the data.
>
> So you basically want to "hide" the SQL commands behind ndbm
> compatible function calls? Have you looked into what is involved? Do you
> want to work on an 'interfaces/ndbm' library? *raised eyebrows*
I was hoping someone had already done it. Other than generalizing
the dbm_open() routine it seems pretty straightforward and it
would take the same amount of work to convert a single app to
use sql directly.
Les Mikesell
les@mcs.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: les@Mcs.Net, scrappy@hub.org
Subject: Re: [QUESTIONS] ndbm emulation library?
In-Reply-To: <199803061807.MAA05889@Mercury.mcs.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox