I agree. All clients issue the same sql and deal with it as they will.
The psql client for example can format the results in various ways (pset
variations etc). Your client(s) need(s) to interpret their identical
results differently. Doesn't seem to me to be the job of SQL?
Jasmin Dizdarevic wrote:
i think jasen is thinking of manipulating the result set in your
programming enviroment not in the database.
btw from the point of "clean programming" it's a bad idea to integrate
html-elements directly into your database quereis. you're mixing data
layer and design layer.
what do you mean with sometimes?
2009/7/29 Axe <i...@axier.se <mailto:i...@axier.se>>
> > Any ideas on how to achieve this? I would like to let the
original sql
> > code stay original. I can prepare postgres before executing
the sql if
> > this makes it easier to acheive the goal
>
> Have a look at CREATE RULE.
>
> Tim
>
Ok, you mean I could create a rule for the table, then I let the
script go into my "black box",
do the original selects, but get a manipulated result set back, then I
drop the rule so
that the blackbox of scripts can get the not manipulated result set
back?
I need to sometimes get the result "<div>output from query</div>" and
sometimes not
and it would be awesomw to get it with the same query, but maybe by
setting
a rule or similar. Best from performance view would be to make
something
more permanent. Is it possible to activate/deactivate a rule?
Axe
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org
<mailto:pgsql-sql@postgresql.org>)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
--
Mit freundlichen Grüßen
Dizdarevic Jasmin
Sonnenbergstr. 3
6714 Nüziders, AUT
jasmin.dizdare...@gmail.com <mailto:jasmin.dizdare...@gmail.com>
+43 664 411 79 29
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
