-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add mysql2 package #178
add mysql2 package #178
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good thanks! Just one change and we can merge this.
packages/mysql2/package.json
Outdated
@@ -0,0 +1,39 @@ | |||
{ | |||
"name": "@sqlfx/mysql2", | |||
"version": "0.45.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you can set the version to 0.0.0, then run pnpm changeset
and add a minor changeset for the initial version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that the changeset version is literally "minor". Did you mean 0.0.1 instead? Sorry, I've never used changesets before.
Thanks Tim. Assuming that you don't want to change any of the package naming or somehow extract common logic, I think this is good to go. I am sure that there exist administrative/introspection queries where the current response type/mapping don't hold, but I think that's the same for the existing mariadb adapter. |
Add an additional mysql package based upon the node-mysql2 package, copying directly from the existing mariadb-based package. We have experienced issues with the mariadb pool implementation and would prefer to use node-mysql2. If the naming is awkward, we might consider adding suffixes to the implementation packages, ie mysql-mariadb and mysql-mysql2, or simply replacing the mariadb implementation.
The node-mysql2 promise-based connection API does not expose query streams, so we are forced to access the private, underlying connection instance.
I have successfully run the examples against a local mysql instance.