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

From Vlad
Subject Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Date
Msg-id cd70c68105050211513046aeb4@mail.gmail.com
Whole thread Raw
In response to Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe  (David Wheeler <david@kineticode.com>)
Responses Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
List 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.

--
Vlad

pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Tuning queries inside a function
Next
From: Tom Lane
Date:
Subject: Re: Tuning queries inside a function