Calling a procedure in MySQL ETL flow
I'm trying to create a pivot table output using a stored procedure, but I'm getting an error while call the procedure.
when I to execute the procudure, I'm getting the error as:
Let me know what wrong I'm doing here.
Thanks in Advance,
Srinivas V
Best Answer
-
i would start by paring back my stored proc to ensure that i had the proper syntax for CREATE-ing and calling a stored proc. keep in mind we're on mysql v 5.6 i believe.
THEN i would take a really close look at the error message.
it says <number> FROM.
I would guess that you have values in your table that contain spaces so SQL is 'mininterpreting' how to handle table creation, OR you're not properly separating the values as column names in your GROUP_CONCAT statement in a way that SQL can interpret into separate columns.
Try taking your SQL statement out of the Stored PROC and running it as a straight SELECT statement. Make sure the results are as you expect.
LASTLY, MySQL is not strong at Pivot Statements. Consider using MagicETL. I know it's a pain to setup and ideally you don't want to have to maintain code, but long term it will probably be more performant than SQL.
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0
Answers
-
i would start by paring back my stored proc to ensure that i had the proper syntax for CREATE-ing and calling a stored proc. keep in mind we're on mysql v 5.6 i believe.
THEN i would take a really close look at the error message.
it says <number> FROM.
I would guess that you have values in your table that contain spaces so SQL is 'mininterpreting' how to handle table creation, OR you're not properly separating the values as column names in your GROUP_CONCAT statement in a way that SQL can interpret into separate columns.
Try taking your SQL statement out of the Stored PROC and running it as a straight SELECT statement. Make sure the results are as you expect.
LASTLY, MySQL is not strong at Pivot Statements. Consider using MagicETL. I know it's a pain to setup and ideally you don't want to have to maintain code, but long term it will probably be more performant than SQL.
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 -
Thanks.
As you correctly mentioned, The column names were not getting populated correctly from the procedure. Executed the code manually and found that out.
0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 601 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 689 Beast Mode
- 43 App Studio
- 39 Variables
- 658 Automate
- 170 Apps
- 441 APIs & Domo Developer
- 42 Workflows
- 5 DomoAI
- 32 Predict
- 12 Jupyter Workspaces
- 20 R & Python Tiles
- 385 Distribute
- 110 Domo Everywhere
- 269 Scheduled Reports
- 6 Software Integrations
- 112 Manage
- 109 Governance & Security
- 8 Domo University
- 25 Product Releases
- Community Forums
- 39 Getting Started
- 29 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive