Sim Zacks wrote: > I'm a fan of unsecured languages in the database. > Obviously they should only be used by people who understand the difference. > I wouldn't want python locked down. > That would prevent so many different external functions that can now > be integrated into the database. > > Among other things that I currently do with plpythonu is a function > that reads a template file, populates it with data and saves the file > to the server. It then FTPs the file to another server. It certainly > can all be done outside of the database, but it is so much easier (and > less maintenance) to include it as a function.
Having the trusted language does not mean you lose the untrusted one. We have both plperl and plperlu, for example. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
