|
|
|
|
|
by eMerzh
2855 days ago
|
|
I've used the mysql FDW for a project at work, it was really helpfull. We've replaced an old "ETL" using a bunch of hard to maintain scripts to mysql_fdw and some materialized view. It was easier for us because it helps write maintainable logic, you can easily sync multiple databases, multiple servers, without much changes. A few things to note though: - we had issues with 0000-00-00 dates that are valid in mysql but not in postgres. So we had to write include a convertion in plsql into the mat view. - We stumble upon a bug in mysql_fdw, in which the selected row is skipped if the size of a column exceed a given size. This is reaaaaally hard to catch and really bad experience as you won't get any error, notice or warning. - we had trouble with a few type casting like json and others. |
|