-
Notifications
You must be signed in to change notification settings - Fork 844
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
Need MySQL 8.0 support #2699
Comments
The causing query here is Mysql 8.0 describes the returned column ("Databases") as:
whereas MySQL 5.5 describes it as:
The important difference is the binary flag in 8.0. |
OK, I take that back. The issue is more complex:
According to the manual we would have to:
Side note: this is also important for #2321 |
So with charset conversion disabled the column type for MySQL 8.0: `Databases` VARCHAR(64) BINARY CHARACTER SET utf8 COLLATE utf8_bin NOT NULL MySQL 5.5: `Databases` VARCHAR(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' That may also mean our conversion logic is flawed? |
@mpyw If you can compile Sequel Pro yourself this should work now, otherwise you'll have to wait until our nightly builds are fixed. |
Should be fixed tomorrow. |
Related reports: http://log.sequelpro.com/view/6553 |
Experiencing this issue as well.
|
any info on the next release? |
Test builds are more up-to-date. The latest (3477d22) worked with MySQL 8.0. |
Can we use Sequel Pro to connect MySQL 8 Server? Please confirm someone? |
still only via the nightly builds I suppose; i'm using build 5224 for a couple of months now without any major issues |
Where I can have that nighty build? Please help as I desperately need Seque Pro for MySQL 8 to connect and use.
… On 14-May-2018, at 1:49 PM, Jakub Wiśniewski ***@***.***> wrote:
still only via the nightly builds I suppose; i'm using build 5224 for a couple of months now without any major issues
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#2699 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANRWW_vSa3IlV-Cl-eNcszIVKeg80Y5eks5tyUUSgaJpZM4MIacH>.
|
https://sequelpro.com/test-builds - it's linked on the main page, in the header under the |
Hi, I want to add my +1 to this. Hoping for an official release that supports MySQL 8 --- or at the very least a dev build that supports 8.0.12. Any update? Thanks. |
A whole year has passed.... |
Hi. Just started using Sequel Pro. And It crashed on trying to use MySQL 8. Read through this bug issue and sounds like the same as mine. I see this is still an open issue. Is there any news of a workaround solution that does not require a user to compile ? |
Please someone fix these crashes on Mojave |
Same issue here when connecting to a mysql 8.0.12 docker container. |
I also have this issue. I'm running on Mojave |
Mohave, trying to connect to 8.0.12 over SSH. Pretty disappointing to see that this issue has been around for so long without a fix. Extra disappointing when trying to use Sequel Pro to diagnose and fix an issue in the middle of a site outage, and running into this bug. Even better, I tried to submit the crash report, and the crash reporter errors out with a connection issue when trying to send the report.... 😑 |
I found an Easy Solution and this is exactly what I did to fix the issue.
If your databases are on localhost, the data will still be there |
To everyone complaining, you can at least try to install the nightly builds. I'm on Mojave. It works. And it's been said before.
|
@jpmurray We're talking about nightly, not even beta? If something happened to somebody's production database whilst using the nightly, can we hold you responsible for suggesting a foolish option? You're one of the few people who actually come with possible solutions, so that is good, but do realize that not everybody can take the risks. Even if there are backups in place. Many people can't contribute directly with code, but I'm sure that many people wouldn't mind paying for Sequel Pro if it ensured that the main developer will spend more time on this beautiful project. |
I just downgraded MySQL to 5.7 and it doesn’t crash anymore |
@sebastiaanspeck that's not solution, that's stupid. You shouldn't sacrifice your database because of this. @jpmurray did you ever think it maybe doesn't work for everybody? We are not all on Mojave yet. Some cannot upgrade yet. |
Downgrading MySQL is no longer an option for some: https://aws.amazon.com/about-aws/whats-new/2018/10/amazon-rds-now-supports-mysql-8/ (probably other managed services will upgrade). Maybe creating a fork and resuming development with another team would be a good solution? |
@jpmurray I ended up downgrading in the end as the infrastructure I was deploying to wouldn't support 8. @scrnjakovic Heads up that everyone here is giving up their free time so I would consider toning down the anger a little bit. |
@tommym9 I'm not angry, I just maintain that suggesting to downgrade and change infrastructure because of a broken tool is terrible thing to do and therefore terrible advice to give. |
@scrnjakovic Agreed. Because there are workarounds like brew cask or builds compiling. Downgrading just for an updated tool is not a right solution. |
Or you wait with upgrading MySQL till the tools you want, also support the upgraded MySQL-version... |
I don't want to kidding here, but in my opinion, one year for this issue is so much time. |
@sebastiaanspeck Database > tool. P.S. I'm aware SequelPro is free and based on donations, however I wouldn't mind it being commercial, I'd be happy to pay for it. If it worked. |
The discussion is getting too off topic. Also many people are subscribed to this issue and are only interested when it will be fixed not in discussions that lead nowhere. |
Please read about the future in new topic - #3705 |
It crashes immediately...
The text was updated successfully, but these errors were encountered: