Re: [GENERAL] stored procedure revisited

>fact that it doesn't do something that most, if not all, commercially
>available db systems do can work against us,
i.e., portability and upgradability: imagine you want to change that
M$ system into Pg, or, I hate to say this, but somehow if your
success is so big that you can not live with Pg, you need go to O ect.
then, true SP will make things really easy (just systax change, you may even
just use our open source facility -- I'm sure there will be, since PL/pgSQL
are so close to other PL). In my own case, when I begin to use PL/pgSQL, I
put some thinking on the second aspect, I bet
others also did that. A true SP will make it more inviting.

C is good, and in a sense, for OSS we should encourage more C "scripting"
and "hacking" than script scripting. (perl and PL/pgSQL actually is "bad" in
this sense). Because IF everybody use C, the use and development will
inherently related and the dev. speed will
accelate exponentially. However, C/C++ is difficult (I use
both C and perl, so I know it). Also, as GOOD excuse, C/C++
is not safe. So, we need PL SP.

However, I would like to see data warehouse (or more moderately and
accurately data mart) support also -- the point: the priority?



______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com