| From: | Leslie Mikesell <les(at)Mcs(dot)Net> | 
|---|---|
| To: | scrappy(at)hub(dot)org (The Hermit Hacker) | 
| Cc: | les(at)Mcs(dot)Net, pgsql-interfaces(at)postgreSQL(dot)org | 
| Subject: | Re: [QUESTIONS] ndbm emulation library? | 
| Date: | 1998-03-06 18:07:40 | 
| Message-ID: | 199803061807.MAA05889@Mercury.mcs.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-interfaces | 
> > > 	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(at)mcs(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 1998-03-06 18:40:04 | Solarix 2.x shared libraries... | 
| Previous Message | The Hermit Hacker | 1998-03-06 17:39:29 | Re: [QUESTIONS] ndbm emulation library? |