Add Postgres 11.x as an ETL option
Dean_Wangerin
Contributor 
Why are we still stuck with such an old version of MySQL for our ETLs? How about adding an option to use a more modern database for our ETLs, like Postgres 11.x? There would be significant language functionality benefits as well as performance benefits.
Also note that you could keep the existing version of MySQL for legacy flows; just add in another database option for new flows.
Tagged:
3
This discussion has been closed.
Categories
- 10.5K All Categories
- 8 Connect
- 918 Connectors
- 250 Workbench
- 472 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 477 Datasets
- 202 Visualize
- 255 Beast Mode
- 2.1K Charting
- 12 Variables
- 17 Automate
- 354 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 247 Distribute
- 63 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 179 Product Ideas
- 1.2K Ideas Exchange
- 12 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive