2011/5/28 Emanuel Calvo <postgres....@gmail.com>: >>> >>> Thanks Heikki for your fast response! ^^ >>> >>> >>>> The compiler would have to determine that the loop never ends, or it >>>> would complain that there's no RETURN at the end. >>>> >>>> Many compilers for other languages do that kind of analysis, but it >>>> usually only results in a warning, and compilers sometimes get that >>>> wrong. I don't think it's worthwhile to do that, but of course, patches >>>> are welcome. >>>> >>> >>> Yeah, it's not a very big concern, althougth cold be taken for future >>> improvements >>> in plpgsql. I very far for submit a patch :P >>> >> >> The deep check of embedded SQL is not possible in PL/pgSQL - this >> remove dependency between PL/pgSQL and database objects. Deeper checks >> mean a broken compatibility :(. >> > > Good point. > >> PL/PSM has different philosophy where full check is implemented now. >> > > Do you think that make some test in 9.1 worthwhile for this > language? I see that the last contrib was submitted years ago. >
I worked on new implementation called PL/PSM - but it is not mature. It should to work with 9.1. https://github.com/okbob/plpsm0 all features https://github.com/okbob/plpsm0/blob/master/test.sql are supported, but there are no real project that is based on this language now. Regards Pavel Stehule > Regards, > > > -- > -- > Emanuel Calvo > Helpame.com > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
