Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.6.11, 10.11.1
Description
If having use a procedure, then in another connection, this procedure is changed (removing one parameter), a call to INFORMATION_SCHEMA.parameters will not reflect the changes in the the first connection.
example to reproduce :
create procedure :
create or replace procedure metaChange(p1 int, p2 int) |
BEGIN
|
select p1 as 'p1'; |
END |
The failing scenario:
- connection 1 : execute
call metaChange(1, 2)
- connection 1 : execute
SELECT * FROM information_schema.parameters where SPECIFIC_NAME='metaChange';
=> return the p1 and p2 parameters as expected
- connection 2 : change procedure:
create or replace procedure metaChange(p1 int)
BEGIN
select p1 as 'p1';
END
procedure has now only one parameter
- connection 2 : execute
SELECT * FROM information_schema.parameters where SPECIFIC_NAME='metaChange';
=> return the p1 parameters as expected
- connection 1 : execute
SELECT * FROM information_schema.parameters where SPECIFIC_NAME='metaChange';
=> still return the p1 and p2 parameters
Attachments
Issue Links
- blocks
-
CONJ-1069 DatabaseMetaData#getProcedureColumns reports incorrect data after executing a stored procedure
- Closed