Add MySQL datasource

[bharatkashyap]

• Closes Support MySQL data source #792
• Visual demonstration

MySQL_conn.mov

• Please follow the the contributing guide on how to create great pull requests.

[render]

Your Render PR Server URL is https://toolpad-pr-1313.onrender.com.

Follow its progress at https://dashboard.render.com/web/srv-cdlldqien0hskv3hfsn0.

[Janpot]

Most SQL datasources will have a large overlapping feature set. I was hoping we could reuse as much code as possible for all of them. I was thinking, instead of copy+pasting the PG datasource, we should reuse as much code as possible. Would it be possible to create a "datasource factory" that we could use to create both the pg and mysql variant with. That way bugfixes and new features to one will also make it to the other. (e.g. we add UI to show available tables)

[bharatkashyap]

Most SQL datasources will have a large overlapping feature set. I was hoping we could reuse as much code as possible for all of them. I was thinking, instead of copy+pasting the PG datasource, we should reuse as much code as possible. Would it be possible to create a "datasource factory" that we could use to create both the pg and mysql variant with. That way bugfixes and new features to one will also make it to the other. (e.g. we add UI to show available tables)

Agreed, I tweaked the implementation to follow this

[Janpot]

I was wondering whether it would make sense to abstract the whole datasource?

export function createSqlServerDatasource<...>({ execSql, tablesQuery }): ServerDatasource<...> {
  // ...
}

[bharatkashyap]

Agreed. I've pushed a change that does this

[prakhargupta1]

Should we also update the docs about MySQL?
The preview that comes after Insert, Delete has it also started coming for PostgreSQL? #1586

[bharatkashyap]

Should we also update the docs about MySQL?

Yes

The preview that comes after Insert, Delete has it also started coming for PostgreSQL? #1586

You could check and update that issue with the status

[oliviertassinari]

Awesome 👌