Hello,
I'm trying to figure out if the following stored procedure is safe in a
high concurrency environment. I'm using the Postgresql 9.4 with all the
default settings.
create procedure test(in topic_id int)
as
declare i_forum_id int;
declare i_post_tally int;
begin
delete from forum_topics
,i_param_with_very_very_long_name integer)
> RETURNS ...
>
> Which one will suit everybody?
>
> Also I think that vertical formatting shouldn't be applied where
> number of parameters is less than two.
>
>
> Saturday, October 25, 2014, 4:10:14 PM, Raymond
Hello All,
We have a postgresql database that is using stored procedures exclusively
to communicate with the web application. The stored procedures often have
upto 50 input/output parameters! We're using the latest version of pgadmin3
in Debian Stable (1.14.2-2)
Anytime we try to edit the stored
I have a stored procedure with several input/output parameters (about 50 of
them). Everytime I go to edit the stored procedure in pgAdmin3, it prints
all of the parameters in the same line...even if I last saved it with new
lines. This makes it really difficult to see the parameter list as I have
t
