Peter Eisentraut wrote:
> Jan Wieck writes:
>
> > There is no
> > reason other than that we'll have more PL handlers to
> > support,
>
> ... which is a pretty big reason ...
>
> > why we shouldn't have two or three different
> > procedural SQL dialects. All can coexist and only those used
> > in your DB schema will get loaded.
>
> Or you can make one PL support alternative, non-conflicting dialects.
Hmmm,
combining it, we need a place to tell the language handler about it's personality. So the handler in
plpgsql.so could serve more than one dialect and just jump into different gram.y path's. Note that it already
doeskinda that by faking a first token telling if actually a function or trigger get's compiled.
Will sleep over that idea.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
