Uh oh!
There was an error while loading. Please reload this page.
[clean](plsql) remove plsql - #58700
Conversation
hello-stephen
commented
Dec 4, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
morrySnow
commented
Dec 4, 2025
run buildall |
hello-stephen
commented
Dec 4, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
doris-robot
commented
Dec 4, 2025
TPC-H: Total hot run time: 35091 ms |
doris-robot
commented
Dec 4, 2025
TPC-DS: Total hot run time: 181993 ms |
doris-robot
commented
Dec 4, 2025
ClickBench: Total hot run time: 28.49 s |
doris-robot
commented
Dec 4, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Dec 4, 2025
FE UT Coverage ReportIncrement line coverage |
hello-stephen
commented
Dec 4, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
hello-stephen
commented
Dec 4, 2025
FE Regression Coverage ReportIncrement line coverage |
morrySnow
commented
Dec 4, 2025
run buildall |
doris-robot
commented
Dec 4, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
doris-robot
commented
Dec 4, 2025
TPC-H: Total hot run time: 34489 ms |
doris-robot
commented
Dec 4, 2025
TPC-DS: Total hot run time: 179383 ms |
doris-robot
commented
Dec 4, 2025
ClickBench: Total hot run time: 28.4 s |
doris-robot
commented
Dec 4, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Dec 4, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Dec 4, 2025
FE Regression Coverage ReportIncrement line coverage |
doris-robot
commented
Dec 5, 2025
ClickBench: Total hot run time: 28.5 s |
doris-robot
commented
Dec 5, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
morrySnow
commented
Dec 5, 2025
run buildall |
doris-robot
commented
Dec 5, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
doris-robot
commented
Dec 5, 2025
TPC-H: Total hot run time: 34435 ms |
doris-robot
commented
Dec 5, 2025
TPC-DS: Total hot run time: 179993 ms |
doris-robot
commented
Dec 5, 2025
ClickBench: Total hot run time: 28.49 s |
hello-stephen
commented
Dec 5, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Dec 5, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Dec 5, 2025
FE Regression Coverage ReportIncrement line coverage |
hello-stephen
commented
Dec 5, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Dec 5, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Dec 5, 2025
FE Regression Coverage ReportIncrement line coverage |
1 similar comment
hello-stephen
commented
Dec 5, 2025
FE Regression Coverage ReportIncrement line coverage |
PR approved by at least one committer and no changes requested. |
Uh oh!
There was an error while loading. Please reload this page.
…iable with MySQL (#66659) ### What problem does this PR solve? Problem Summary: PL/SQL stored procedures were removed in #58700 because the implementation had many bugs. That removal also deleted the `SHOW (PROCEDURE|FUNCTION) STATUS` grammar, the `ShowProcedureStatusCommand`, and the `information_schema.routines` scanner. Clients such as Bytebase send `SHOW FUNCTION STATUS WHERE Db = '...'` during connection/metadata probing, and the unsupported syntax now blocks users from using the database. This PR only restores the SQL entry points so these statements parse and always return empty result sets without errors. The stored procedure functionality itself is NOT restored. Related PR: #58700
…iable with MySQL (apache#66659) ### What problem does this PR solve? Problem Summary: PL/SQL stored procedures were removed in apache#58700 because the implementation had many bugs. That removal also deleted the `SHOW (PROCEDURE|FUNCTION) STATUS` grammar, the `ShowProcedureStatusCommand`, and the `information_schema.routines` scanner. Clients such as Bytebase send `SHOW FUNCTION STATUS WHERE Db = '...'` during connection/metadata probing, and the unsupported syntax now blocks users from using the database. This PR only restores the SQL entry points so these statements parse and always return empty result sets without errors. The stored procedure functionality itself is NOT restored. Related PR: apache#58700
related PR: #30817#31574#32866
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)