Open detrout opened 5 years ago
Getting MySQL or Postgres into the flatpak would be a major pain, and making sure it runs/shuts down properly would require quite some effort and testing, which I don't have the time for, really, which is why I initially decided for SQLite.
We did some major bugfixing for 19.04 (which I'm currently waiting for to be released, so I can integrate all your changes and the update) which should solve the deadlocks and similar issues, so the experience should be so much better than it used to be.
Ok good to hear there's bug fixes. If you can please poke me when its updated so I can try it. Right now I've fallen back to neomutt and outlook online
I'd thought it might work to get the mysql/postgres drivers to compile so the flatpak could talk to a database server running on the host.
I had a brief wish that kwin could run in a flatpak, I'm having problems on wayland and it'd be nice to have a contained app + sdk that I could easily try HEAD with.
I figured out that the flatpak is using sqlite and I thought historically that was prone to deadlocks, and some of the behaviors I see when trying to use the flatpak seems like deadlocks.
Should the flatpak include a build of mariadb?
Would it make sense to build and include the mysql and psql qt5 drivers to use the flatpak with a host provided database server?