| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Greg Jaskiewicz <gryzman(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Dynamic queries in stored procedure |
| Date: | 2013-07-05 14:26:42 |
| Message-ID: | 51D6D7A2.3030206@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Misa Simic | 2013-07-05 14:46:31 | Re: Dynamic queries in stored procedure |
| Previous Message | Greg Jaskiewicz | 2013-07-05 13:57:06 | Dynamic queries in stored procedure |