Details
-
New Feature
-
Status: In Testing (View Workflow)
-
Major
-
Resolution: Unresolved
-
Q3/2025 Server Development
Description
DELIMITER ||
|
CREATE OR REPLACE PROCEDURE p(a INTEGER DEFAULT 9999) |
DETERMINISTIC
|
BEGIN
|
SELECT a; |
END || |
DELIMITER ;
|
SELECT * FROM information_schema.PARAMETERS WHERE SPECIFIC_NAME = 'p' \G |
 |
*************************** 1. row ***************************
|
SPECIFIC_CATALOG: def
|
SPECIFIC_SCHEMA: test
|
SPECIFIC_NAME: p
|
ORDINAL_POSITION: 1
|
PARAMETER_MODE: IN |
PARAMETER_NAME: a
|
DATA_TYPE: int |
CHARACTER_MAXIMUM_LENGTH: NULL |
CHARACTER_OCTET_LENGTH: NULL |
NUMERIC_PRECISION: 10
|
NUMERIC_SCALE: 0
|
DATETIME_PRECISION: NULL |
CHARACTER_SET_NAME: NULL |
COLLATION_NAME: NULL |
DTD_IDENTIFIER: int(11) |
ROUTINE_TYPE: PROCEDURE |
As a general rule, I'd avoid releasing new DDLs until they are visible in the information_schema. SHOW CREATE output needs to be parsed, so it's not a replacement.
Attachments
Issue Links
- causes
-
MDEV-37489 SIGSEGV in get_param_default_value | store_schema_params
-
- In Review
-
- is caused by
-
MDEV-10862 Stored procedures: default values for parameters (optional parameters)
-
- Closed
-