Add Postgres 11.x as an ETL option
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
- 7.7K All Categories
- 3 Connect
- 919 Connectors
- 244 Workbench
- 477 Transform
- 1.8K Magic ETL
- 60 SQL DataFlows
- 446 Datasets
- 37 Visualize
- 198 Beast Mode
- 2K Charting
- 8 Variables
- 1 Automate
- 348 APIs & Domo Developer
- 82 Apps
- Workflows
- 14 Predict
- 3 Jupyter Workspaces
- 11 R & Python Tiles
- 241 Distribute
- 59 Domo Everywhere
- 241 Scheduled Reports
- 15 Manage
- 36 Governance & Security
- 27 Product Ideas
- 1.1K Ideas Exchange
- Community Forums
- 14 Getting Started
- 1 Community Member Introductions
- 49 Community News
- 18 Event Recordings
- 579 日本支部