Well said, Shawn...
Having taken care of all/most security considerations, I wanted to
design a simple(or not so simple set of function that would return a
"conditional" value). That is, given a SELECT statement, I wanted to
be able to look at the row(s) returned and say: Given case (a), return
column a,b, and c; Given case (b), return c, a, d...and if all else
fails, return null. I used the login mechanism as an example, but this
could be used in a number of cases...I know this is possible, I guess
I have to read a bit more about the PL/PGSQL syntax...I want to use
functions/stored procedures because I can re-use it later...
On 10/24/05, Shawn <[EMAIL PROTECTED]> wrote:
> Aiming for compact and efficient code is usually a good thing. But
> sometimes
> the "eloquent" solution is just not as easy to understand 6 months later,
> and
> doesn't really buy that much in terms of performance. Troubleshooting
> someone else's code, or even your own a year or so after the fact helps
> drive
> this home. :) (but good commenting helps)
>
> Shawn
>
> On Monday 24 October 2005 23:28, Cirez Communications, inc. wrote:
> > Thanks a bunch for the info...I guess I would leave things the way
> > they are. The code is not as compact as I would like; but it minimizes
> > the risks....
> >
>
>
--
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
-------------------Cirez Communications, inc.----------------
----------------------Juan Alberto Cirez---------------------
-----------------------Senior Consultant---------------------
[EMAIL PROTECTED]
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
Sunny and Beautiful Vancouver, Canada.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
