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:
cd70c68105050211513046aeb4@mail.gmail.com (view raw or flat )
Thread:
2005-05-02 01:25:38 from Vlad <marchenko(at)gmail(dot)com>
2005-05-02 01:46:47 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2005-05-02 03:01:54 from Vlad <marchenko(at)gmail(dot)com>
2005-05-02 03:19:16 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2005-05-02 05:05:45 from Vlad <marchenko(at)gmail(dot)com>
2005-05-02 05:44:33 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2005-05-02 12:59:58 from Vlad <marchenko(at)gmail(dot)com>
2005-05-02 13:14:19 from Neil Conway <neilc(at)samurai(dot)com>
2005-05-02 13:36:05 from Vlad <marchenko(at)gmail(dot)com>
2005-05-02 16:24:48 from David Wheeler <david(at)kineticode(dot)com>
2005-05-02 16:24:02 from David Wheeler <david(at)kineticode(dot)com>
2005-05-02 13:15:35 from "Julian Mehnle" <bulk(at)mehnle(dot)net>
2005-05-02 16:17:55 from David Wheeler <david(at)kineticode(dot)com>
2005-05-02 06:16:50 from Steve Atkins <steve(at)blighty(dot)com>
2005-05-02 16:19:46 from David Wheeler <david(at)kineticode(dot)com>
2005-05-02 18:51:30 from Vlad <marchenko(at)gmail(dot)com>
2005-05-02 20:38:44 from David Wheeler <david(at)kineticode(dot)com>
2005-05-03 02:01:33 from "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
2005-05-03 12:25:08 from Vlad <marchenko(at)gmail(dot)com>
2005-05-02 13:31:11 from Andrew Dunstan <andrew(at)dunslane(dot)net>
2005-05-02 13:40:50 from Andrew Dunstan <andrew(at)dunslane(dot)net>
2005-05-02 16:28:56 from David Wheeler <david(at)kineticode(dot)com>
2005-05-02 04:30:56 from Neil Conway <neilc(at)samurai(dot)com>
2005-05-02 04:49:47 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2005-05-02 04:51:19 from Vlad <marchenko(at)gmail(dot)com>
2005-05-02 16:19:04 from David Wheeler <david(at)kineticode(dot)com>
2005-05-02 16:34:17 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2005-05-02 16:53:12 from David Wheeler <david(at)kineticode(dot)com>
2005-05-02 01:55:58 from Dana Hudes <dhudes(at)tcp-ip(dot)info>
2005-05-02 02:36:39 from Vlad <marchenko(at)gmail(dot)com>
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.
--
Vlad
In response to
Responses
pgsql-general by date
Next :From: Jonel RientonDate: 2005-05-02 18:56:04Subject : PostgreSQL 8.0.2 and TigerPrevious :From : Joshua D. DrakeDate : 2005-05-02 18:27:27Subject : Re: Tuning queries inside a function
