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

From: Alexandre <Xlex0x835(at)rambler(dot)ru>
To: Dan Sugalski <dan(at)sidhe(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Simplified (a-la [G|N]DBM) DB access
Date: 2005-04-20 06:05:53
Message-ID: e0aee76d3be42ddd2d38bab551b99ac8@rambler.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Apr 19, 2005, at 23:24, Dan Sugalski wrote:

> 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.

Does your own ISAM interface also convert ISAM calls to the SQL
queries? If so, then it is also add overhead: make a call to the some
wrapper, which will generate SQL query and send it to the sever, which
will parse, plan and compile it and execute only after that. Desirable:
make a call, which will connect to the server and get row.

But if you write ISAM interface which didn't use SQL, can you tell more
about, please?

I didn't have any legacy application, which I need to move to the new
DB, I just need more simple and fast access.

Regards,
/Alexandre.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2005-04-20 06:13:04 Re: postgresql start/stop/status script
Previous Message Alexandre 2005-04-20 06:00:43 Re: Simplified (a-la [G|N]DBM) DB access