Oh, well yeah, of course there's always that. :)
But once the original poster said "better start learning Tcl" the
commitment had already been made to learn something new. So why not just
go straight for pl/pgsql? Granted, it's got a learning curve, but I find
it a lot easier to tinker with than C functions when you don't know what
you're doing.
On Mon, 2003-11-10 at 18:11, Joshua D. Drake wrote:
> Ben wrote:
>
> >Sorry, I'm coming into this thread late so I must have missed something...
> >what's wrong with pl/pgsql?
> >
> >
> The fact that it is pl/pgSQL? Seriously though, I think that pl/pgSQL is
> counter
> intuitive to some people and those of us who are coming from say a Perl
> background are going to be much more proficient in using pl/Perl then having
> to learn YET another language.
>
> Sincerely,
>
> Joshua Drake
>
>
>
> >On Mon, 10 Nov 2003, Alvaro Herrera wrote:
> >
> >
> >
> >>On Mon, Nov 10, 2003 at 03:00:34PM -0800, Joshua D. Drake wrote:
> >>
> >>
> >>
> >>>>>Better start learning Tcl ...
> >>>>>
> >>>>>
> >>>What are we torturing people now? Can plPython do this?
> >>>
> >>>
> >>Well, aparently Tcl is not up to the task either, nor is plPython. At
> >>least I can find no mention on the docs nor the source code. Can your
> >>plPHP or plPerl do it?
> >>
> >>It seems the only choices left are PL/pgSQL and C ...
> >>
> >>--
> >>Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
> >>"Acepta los honores y aplausos y perderás tu libertad"
> >>
> >>---------------------------(end of broadcast)---------------------------
> >>TIP 8: explain analyze is your friend
> >>
> >>
> >>
> >
> >
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo@postgresql.org so that your
> > message can get through to the mailing list cleanly
> >
> >
