pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@trust.ee>
To: Taral <taral@cyberjunkie.com>
Cc: pgsql-hackers@hub.org
Subject: Re: [HACKERS] PREPARE
Date: Tue, 17 Nov 1998 10:15:56 +0200
Message-ID: <365130BC.FD2E87E2@trust.ee> (raw)
References: <000501be119e$6c16efa0$8a14f7d0@taral.dobiecenter.com>

Taral wrote:
> 
> It seems that full support for CORBA and the COS Query Service requires us
> to enable the user to parse, prepare, and execute the query in three
> separate stages. Are we also planning to support PREPARE? If so, we should
> co-ordinate the effort, since the full COSQS support will require pulling
> apart pg_parse_and_plan().

We should.

Currently we do support PREPARE (kind of) in  the SPI interface.

However, it is not strictly necessary (both ODBC and JDBC currently 
simulate it on the client side), but it would enable interactive 
applications perform much better if we did.

The current FE<->BE protocol is strange mix of CLI and directly 
usable psql replacement ;)

BTW, what does CORBA prescribe about transactions (if anything) ?

Is the current transaction model adequate or do we need nested 
transactions ?

PS. It would probably be beneficial to look also at Microsofts ADO for
ideas,
afaik this is the DCOM version of what we are trying to do with CORBA.

------------
Hannu



view thread (18+ messages)  latest in thread

Message-ID: <365130BC.FD2E87E2@trust.ee>
Permalink:  ../365130BC.FD2E87E2@trust.ee/
Also on:    postgresql.org/message-id/365130BC.FD2E87E2@trust.ee

 · 

reply

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: hannu@trust.ee, taral@cyberjunkie.com, pgsql-hackers@hub.org
  Subject: Re: [HACKERS] PREPARE
  In-Reply-To: <365130BC.FD2E87E2@trust.ee>

* 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