From: Scott Barney <scott@calculatedsteam.com>
To: pgsql-performance@postgresql.org
Subject: Re: Dynamic queries in stored procedure
Date: Fri, 05 Jul 2013 09:50:47 -0500
Message-ID: <51D6DD47.6020606@calculatedsteam.com> (raw)
In-Reply-To: <51D6D7A2.3030206@dunslane.net>
References: <96F5E9DF-8F6E-4EF6-B0AE-43B585B11F94@gmail.com>
<51D6D7A2.3030206@dunslane.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
I do this all the time; In fact, I've written a dynamic aggregate engine
that uses a sudo bind variable technique & dynamic joins with dependency
injection because the table names and query logic are not known at run
time - all in plpgsql.
sb
On 7/5/2013 9:26 AM, Andrew Dunstan wrote:
>
> On 07/05/2013 09:57 AM, Greg Jaskiewicz wrote:
>> Hey,
>>
>> We have a search method that depending on search params will join 3-5
>> tables, craft the joins and where section. Only problem is, this is
>> done in rather horrible java code. So using pgtap for tests is not
>> feasible.
>> I want to move the database complexity back to database, almost
>> writing the query construction in the plpgsql or python as stores
>> procedure, any suggestions ?
>>
>> Unfortunately PostgreSQL won't eliminate unnecessary joins from a
>> view, so I can't just create one view and simple code adding where's,
>> order by, etc.
>>
>> No, I don't want to use orm.
>>
>
> It's a matter of taste. Pretty much every PL has facilities for
> constructing and running dynamic sql. PLPgsql ,PLPerl, PLV8 ...
>
> cheers
>
> andrew
>
>
>
>
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott@calculatedsteam.com
Subject: Re: Dynamic queries in stored procedure
In-Reply-To: <51D6DD47.6020606@calculatedsteam.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox