Re: Status of plperl inter-sp calling
От | David E. Wheeler |
---|---|
Тема | Re: Status of plperl inter-sp calling |
Дата | |
Msg-id | 3E7F47EA-6F5F-4BD7-9A29-026A8FDEEFAD@kineticode.com обсуждение исходный текст |
Ответ на | Re: Status of plperl inter-sp calling (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Status of plperl inter-sp calling
Re: Status of plperl inter-sp calling Re: Status of plperl inter-sp calling |
Список | pgsql-hackers |
On Dec 30, 2009, at 4:17 PM, Robert Haas wrote: >> That much works currently. Behind the scenes, when a stored procedure is >> loaded into plperl the code ref for the perl sub is stored in a cache. >> Effectively just >> $cache{$name}[$nargs] = $coderef; > > That doesn't seem like enough to guarantee that you've got the right > function. What if you have two functions with the same number of > arguments but different argument types? And what about optional > arguments, variable arguments, etc.? As Tim said elsewhere: > I don't see either of those as significant issues: "If you need more > control for a particular SP then don't use SP::* to call that SP." Best, Davdi
В списке pgsql-hackers по дате отправления: