Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe

From: David Wheeler <david(at)kineticode(dot)com>
To: Steve Atkins <steve(at)blighty(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, dbdpg-general(at)gborg(dot)postgresql(dot)org
Subject: Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Date: 2005-05-02 16:19:46
Message-ID: B466C0B0-6B75-48EE-AD89-38DD72828E18@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On May 1, 2005, at 23:16 , Steve Atkins wrote:

> Isn't this behaving as documented? prepare_cached() is supposed to
> return the original statement handle when you pass it the same string
> a second time.

Yes.

> The docs for prepare_cached() are littered with "Don't do this unless
> you understand the implications" warnings, as well as some kludges to
> differentiate different cases.

Which is why Vlad should use prepare() instead of prepare_cached().

Regards,

David

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Wheeler 2005-05-02 16:24:02 Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Previous Message David Wheeler 2005-05-02 16:19:04 Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe