* Niklas Johansson <spot@xxxxxxxx> [2006-04-03 11:04:25 +0200]: > > On 2 apr 2006, at 23.08, Niklas Johansson wrote: > > >CREATE OR REPLACE FUNCTION exec_device_type() RETURNS trigger AS $$ > > EXECUTE "SELECT device_type" || OLD.type || "(OLD.id)"; > >$$ LANGUAGE plpgsql; > > > Sorry, I was bitten by the bedbug there: a plpgsql function needs a > little more than that to be functional :) > > CREATE OR REPLACE FUNCTION exec_device_type() RETURNS trigger AS $$ > BEGIN > EXECUTE 'SELECT device_type' || OLD.type || '(OLD.id)'; > RETURN NEW/OLD/NULL; -- Depending on your application. > END; > $$ LANGUAGE plpgsql; > > But really, you should consider reworking your schema structure. > Having a thousand functions doing almost the same thing is neither > efficient, nor maintainable. Things are very diferent. For many types functions not needed, jast update. I.e. This is a way One trigger with ~1000 else if. Here was a diametral opinion. > > > > Sincerely, > > Niklas Johansson > > > > -- С уважением, Ключников А.С. Ведущий инженер ПРП "Аналитприбор" 432030 г.Ульяновск, а/я 3117 тел./факс +7 (8422) 43-44-78 mailto: alexs@xxxxxxxxxxxxxx
