Skip site navigation (1) Skip section navigation (2)

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

From: Vlad <marchenko(at)gmail(dot)com>
To: David Wheeler <david(at)kineticode(dot)com>
Cc: Steve Atkins <steve(at)blighty(dot)com>, 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 18:51:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
> > 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().

in our web application similar SQL queries (like load an object)
executed over and over again with high frequency. So it's very
desirable to use prepare_cached. I think we are going to adjust our
ORM (object relation mapper) to always use full path to reference DB
objects in query.


In response to


pgsql-general by date

Next:From: Jonel RientonDate: 2005-05-02 18:56:04
Subject: PostgreSQL 8.0.2 and Tiger
Previous:From: Joshua D. DrakeDate: 2005-05-02 18:27:27
Subject: Re: Tuning queries inside a function

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group