Re: validation of postgresql functions
От | Ben |
---|---|
Тема | Re: validation of postgresql functions |
Дата | |
Msg-id | Pine.LNX.4.44.0310030928230.22485-100000@localhost.localdomain обсуждение исходный текст |
Ответ на | validation of postgresql functions (dinosaur8000@yahoo.com (giant food)) |
Список | pgsql-general |
I never found a way. Instead I hacked up a general stored proceedure testbed. I was going to release it when I had some time to make it somewhat clean, but if you're desperate for something now I can give you what I've got.... On 29 Sep 2003, giant food wrote: > Hi, I'm in the process of converting an Oracle database into > postgresql. One thing I've noticed is that postgresql functions keep > the entire function body in a string, e.g.: > > CREATE OR REPLACE FUNCTION f_do_something(varchar, numeric, varchar) > RETURNS varchar AS > ' > ... > ' > LANGUAGE 'plpgsql' VOLATILE; > > The problem I'm having with this is that I can never find any errors > in my functions until runtime, unlike with Oracle where the "create > function" script will fail if, for example, I misspelled a table name. > > Is there any way to force postgresql to compile functions, without > running them first? > > --Frank > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match >
В списке pgsql-general по дате отправления: