On Tuesday 07 April 2009, Roger Leigh wrote: > On Tue, Apr 07, 2009 at 01:19:53AM +0200, Sune Vuorela wrote: > > you would prefer if they used oracle or postgresql? > > I really think using mysql is much better than reimplementing a fast > > storage that allows concurrent access. > > Depending on /any/ database *server* is not acceptable. It should > be using the *client interface* like every other program out there. > This means either the client program, client library, or some other > database abstraction library are used to connect to the server. It is actually using an abstraction, the Qt SQL plugin system and the database access code is also quite centralized. Adding support for other database engines is possible, just not that high on the priority list as getting the rest of the infrastruture running and porting the applications. Once support for more than one database engine is available, it might be possible to create a meta package and have it provided by several database packages. > If it wants to embed a server, then sqlite exists for just this > purpose. There is also mysql embedded, but unfortunately it doesn't work reliably enough either (IIRC it doesn't support transactions). Starting a local mysql instance is basically a workaround that provides the necessary features in a reliable way and does not require administrator level settings like using a system daemon. (this is supported though) > Directly running an entire database server instance for a single > client is *wrong*, bloated and broken design. And I'm forced to > run a system mysql instance unless I take special steps to > disable it, with all the security issues that implies. No thanks. As Sune already wrote it is unfortunate that the mysql server package also contains the global startup mechanism. Makes sense if running a single instance is the only use case, but obviously breaks for others. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
Attachment:
signature.asc
Description: This is a digitally signed message part.