From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [PATCHES] prepareable statements |
Date: | 2002-07-28 15:21:31 |
Message-ID: | Pine.LNX.4.44.0207272218020.9620-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Neil Conway writes:
> On Thu, Jul 25, 2002 at 10:54:04PM +0200, Peter Eisentraut wrote:
> > I'm not sure I like that. It seems too confusing. Why not keep
> > it as the standard says? (After all, it is the PREPARE part that
> > we're adjusting, not EXECUTE.)
>
> I think it's both, isn't it? My understanding of Tom's post is that the
> features described by SQL92 are somewhat similar to the patch, but not
> directly related.
What I was trying to say is this: There is one "prepared statement"
facility in the standards that allows you to prepare a statement defined
in a host variable, whereas you are proposing one that specifies the
statement explicitly. However, both of these are variants of the same
concept, so the EXECUTE command doesn't need to be different.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-28 16:32:36 | Re: tuple concurrently updated |
Previous Message | Luis Alberto Amigo Navarro | 2002-07-28 10:22:53 | Re: Question about LWLockAcquire's use of semaphores instead of spinlocks |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-07-29 05:24:34 | anonymous composite types for Table Functions (aka SRFs) |
Previous Message | Neil Conway | 2002-07-27 20:19:08 | Re: START TRANSACTION |