[MCOL-45] CREATE PROCEDURE fails Created: 2016-05-06  Updated: 2016-09-17  Resolved: 2016-09-17

Status: Closed
Project: MariaDB ColumnStore
Component/s: DMLProc
Affects Version/s: None
Fix Version/s: 1.0.3

Type: Bug Priority: Major
Reporter: David Hall (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Environment:

Centos 6/5

Issue Links:
PartOf
is part of MCOL-280 Beta issues Closed
Sprint: 1.0.3

 Description   

ref: working_tpch1_comparLogOnly/partitionOptimization/aCreateViews.sql

All CREATE PROCEDURE statements fail with:
ERROR 1303 (2F003) at line 32: Can't create a PROCEDURE from within another stored routine

This may or may not mask other issues in this test suite, as it stops everything in the directory from running.

 Comments   
Comment by Dipti Joshi (Inactive) [ 2016-05-23 ]

Since stored procedure has limited functionalities in MariaDB ColumnStore - hence putting this lower priority right now.

Comment by Chris Calender (Inactive) [ 2016-08-23 ]

Affects customer.

Comment by Chris Calender (Inactive) [ 2016-08-23 ]

Similar issue occurs with Events also.

Comment by David Hall (Inactive) [ 2016-09-02 ]

It seems we now need a lex_end(thd->lex) when returning -1 from idb_vtable_process. Changes in mariadb cause this need. In the past it didn't matter.

Comment by Andrew Hutchings (Inactive) [ 2016-09-07 ]

Looks good to me, moving to QA

Comment by Daniel Lee (Inactive) [ 2016-09-17 ]

Build verified

mscadmin> getsoft
getsoftwareinfo Fri Sep 16 19:33:13 2016

Name : mariadb-columnstore-platform
Version : 1.0.3
Release : 1
Architecture: x86_64
Install Date: Thu 15 Sep 2016 04:25:09 PM CDT
Group : Applications
Size : 25431329
License : Copyright (c) 2016 MariaDB Corporation Ab., all rights reserved; redistributable under the terms of the GPL, see the file COPYING for details.
Signature : (none)
Source RPM : mariadb-columnstore-1.0.3-1.src.rpm
Build Date : Thu 15 Sep 2016 03:41:46 PM CDT

Verified the script on a tpch1g database.

Generated at Thu Feb 08 02:18:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.