MySQL/MariaDB database management for macOS. Tweets by @sequelpro/developers
All around the world.
Joined April 2008
- Tweets351
- Following7
- Followers3.3K
- Likes10
Don't bother submitting crash reports from 1.1.2. It's too far behind the current development version, which can be found on sequelpro.com/test-builds
Yes, we are aware of those issues. See github.com/sequelpro/sequelp…
If you feel adventurous, we have a new nightly build fixing some crashes (especially on 10.14 and when using MySQL 8.0 databases): sequelpro.com/test-builds
That makes you the first person to ever have a positive comment about that warning in the previous 8 or so years 😀 ^ML2
1.2 isn't released yet, but you could try a development build, they are rather close: sequelpro.com/test-builds ^ML2
Take a loot at this huge collection of Sequel Pro color themes! teapaw.org/daylerees/status/94692…
Is your @sequelpro missing out on some theme love? Of course it's not! Enjoy the sexy pancakes. #rainglow github.com/rainglow/sequel-p…
You can use a development build from sequelpro.com/test-builds. For now they are identical to plans for 1.2 ^ML2
You got an answer: github.com/sequelpro/sequelp… Also it looks like this particular issue only affects about 5% of our user base ^ML2
We have nothing against Windows, but porting it would be quite a lot of work and we have no developer with Windows coding experience and/or interest in that. So... yeah, probably not gonna happen ^ML2
We are using libmysqlclient 5.5.42 with 1.1.2 and 5.5.56 with nightlies. Try enabling mysql protocol compression (SP has this by default).
Use this SHA256 Hash to verify the download: 7b34fd63c13e9e9ca4f87d548241ff9df9a266b554af23549efd7be006f387c6 sequel-pro-1.1.2.dmg
We use GitHub for release hosting. Someone else probably distributed some malware via @github and now the whole domain got blocked...