New package: TinyMySQL v0.1.0

[JuliaRegistrator]

• Registering package: TinyMySQL
• Repository: https://github.com/nakagami/TinyMySQL.jl
• Created by: @nakagami
• Version: v0.1.0
• Commit: 1b6235bcb9d6a36e18dc901149449828f1c23b28
• Reviewed by: @nakagami
• Reference: register package nakagami/TinyMySQL.jl#1 (comment)
• Description: Julia MySQL driver

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines are all met! ✅

Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[goerz]

How does this compare to MySQL?

[nakagami]

MySQL.jl is fully featured but depends on libmariadb.

When I try to connect to Ubuntu's MySQL from my macOS, I get the following error:

ERROR: LoadError: (1045): Plugin caching_sha2_password could not be loaded: dlopen(/Users/nakagami/.julia/artifacts
/2046d7b35ab3596d63adebb5695b62a30a85a977/lib/mariadb/plugin/caching_sha2_password.so, 0x0002): Library not loaded:
@rpath/libssl.3.dylib

I suspect installing libssl.3.dylib should resolve this, but TinyMySQL
handles the MySQL network protocol itself, so it doesn't encounter this error.

[goerz]

Have you tried opening an issue with MySQL? I would be hesitant to have a whole new package, with all the duplication of effort and resulting confusion for something that could presumably be fixed

[nakagami]

This is likely an issue the user should resolve themselves,
and I understand that in my case, executing the following

brew install openssl@3

I had thought it preferable to have multiple options available,
but I understand your view that having several similar packages registered could cause confusion.

If it is not suitable, please close it.
Thank you.

[goerz]

I understand that in my case, executing the following

brew install openssl@3

I'm not a user of MySQL.jl myself, but I'm surprised by this. I was under the impression that Julia libraries typically bundle their binary dependencies. It would definitely be something to bring up in an issue / Slack / Discourse.

If it is not suitable, please close it.

I'm not saying that… I'm in no position to "reject" packages, definitely not for something as subjective as this. There can certainly be good reasons to have alternative implementations. That being said, my personal stance is indeed that refining an existing package should always be the first choice before registering an alternative. I do think it would be useful to have some community feedback around this, including with the developers of MySQL.jl (@quinnj ?)

At the very least, it would probably be good to give a clearer indication in the README about what distinguishes the package. That is, when one should use MySQL, and when TinyMySQL.

[nakagami]

Thank you.
Since it should be bundled with the package, I created an issue for MySQL.jl.

JuliaDatabases/MySQL.jl#232