Re: Simplified (a-la [G|N]DBM) DB access

From: Dan Sugalski <dan(at)sidhe(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Simplified (a-la [G|N]DBM) DB access
Date: 2005-04-19 19:24:47
Message-ID: a06210207be8b0ac7f7bf@[172.24.18.155]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

At 9:40 PM +0400 4/19/05, Alexandre wrote:
>Lane, thank you, but it is not: PostISAM "generates SQL statements
>on the fly from traditional ISAM (read, write, start) statements",
>so it just add overhead, and is not what I'm looking for.

Speaking from experience, as I have a system which hides Postgres
behind an ISAM interface (though not PostISAM -- I rolled my own DB
library) as part of a legacy 4GL migration, the overhead's ignorable.
Dismissing it for that reason's not a good idea.

>On Apr 19, 2005, at 18:16, Tom Lane wrote:
>
>>Alexandre <Xlex0x835(at)rambler(dot)ru> writes:
>>>What I mean is: currently to get/put/delete/edit any data I have to
>>>compose an SQL query, which should be parsed, compiled, optimized and
>>>so on. While, in some tasks simple interface a-la [G|N]DBM should be
>>>more than enough, but it will be more preferable to store all data in
>>>one database, which support concurrent access, transactions, etc.
>>
>>I seem to recall that someone has written an ISAM-style interface
>>library, which might be more or less what you are asking for. Check
>>the archives, and/or look at gborg and pgfoundry.

--
Dan

--------------------------------------it's like this-------------------
Dan Sugalski even samurai
dan(at)sidhe(dot)org have teddy bears and even
teddy bears get drunk

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Baldur Norddahl 2005-04-19 22:34:30 postgresql start/stop/status script
Previous Message Santharam 2005-04-19 19:13:54 Data migration from oracle