On Thu, Jan 04, 2007 at 06:53:09PM -0700, Scott Ribe wrote: > What about: > > create function set_emp_id() returns void as $$ > begin > drop table if exists emp_1_id; > select emp_id into temp emp_1_id from secureview.tbl_employee where > username = current_user; > end; > $$ language plpgsql; > > create function get_emp_id() returns int as $$ > return select emp_id from emp_1_id; > $$ language plpgsql stable; > > Call set_emp_id once on connection, then use get_emp_id thereafter. > Would that be any faster? (This is what Erik meant by "a temp table > is pretty much a session variable" in his earlier message.)
You can use PL/Perl's %_SHARED hash <http://www.postgresql.org/docs/current/static/plperl-global.html> to store session-long variables, and you don't need to worry about cleanup :) Similar things exist in PL/Python and possibly others. Cheers, D -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote! ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
