You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great news -- when I first started working on DataMigrator there wasn't a MySQL Client for dart that supported auth using caching_sha2_password (default since MySQL 8). Since then, that functionality has been contributed to this package: https://pub.dev/packages/mysql_client
So work on a MySQL DataOrigin is ready to move forward!
What use cases are you wanting for a MySQL source / destination?
I am thinking of providing the ability to:
connect to any MySQL instance that supports the MySQL client (anything that workbench can connect to)
as a source, it can add tables as a source SchemaMap
as a source, it can define a specific query (with iterating placeholders to handle going through the results) to define a SchemaMap
completing the index support that is already stubbed out in the schema data modeling
add support to define indices in a SchemaMap, so you can control how a MySQL table's primary keys are created
I'm currently thinking about and designing how to support relationships between data. I'll be adding support for standardized deeply nested data and a part of that is being able to pull in a schema model's parent attributes when being converted. This mostly applies to JSON data, however the correlated use case for MySQL is supporting the relational data.
Does anyone have any use cases that have to do with inserting and migrating out of MySQL when it comes to handling the relational data?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Great news -- when I first started working on DataMigrator there wasn't a MySQL Client for dart that supported auth using caching_sha2_password (default since MySQL 8). Since then, that functionality has been contributed to this package: https://pub.dev/packages/mysql_client
So work on a MySQL DataOrigin is ready to move forward!
What use cases are you wanting for a MySQL source / destination?
I am thinking of providing the ability to:
I'm currently thinking about and designing how to support relationships between data. I'll be adding support for standardized deeply nested data and a part of that is being able to pull in a schema model's parent attributes when being converted. This mostly applies to JSON data, however the correlated use case for MySQL is supporting the relational data.
Does anyone have any use cases that have to do with inserting and migrating out of MySQL when it comes to handling the relational data?
Beta Was this translation helpful? Give feedback.
All reactions