Mailinglist Archive: opensuse-kde (352 mails)

[Bruno Friedmann <bruno@xxxxxxxxxxx>]

On 10/14/2011 04:52 PM, Jon Nelson wrote:
> On Fri, Oct 14, 2011 at 2:08 AM, Bruno Friedmann <bruno@xxxxxxxxxxx> wrote:
> > On 10/13/2011 05:11 PM, Andras Mantia wrote:
> > > Bruno Friedmann wrote:
> > >
> > > > On 10/13/2011 03:38 PM, Andras Mantia wrote:
> > > > > Hi,
> > > > >
> > > > >  I'd like to draw the attention to bug 718367, in case it is still the
> > > > > case
> > > > > of shipping Akonadi to be configured to SQLite by default, please
> > > > > reconsider
> > > > > the decision. This will provide sub-optimal performance and in certain
> > > > > cases
> > > > > buggy behavior (hangs) for Akonadi based applications, including KMail2.
> > > > >
> > > > > Andras
> > > >
> > > > Andras you know that the sqlite choice was also made because there's no
> > > > upstream solution for the buggy mysql support on nfs home too :-)
> > > >
> > > > [dream on]
> > > > One unified full semantic database (that can be per user, per computer,
> > > > per network) for the whole kde desktop.
> > > > With a nice administrative stack to dig in it, backup, restore, migrate
> > > > [/dream off]
> > >
> > > Ok, I didn't know about the NFS problem (you refer to the unclear
> > > shutdown/broken suspend issue, right:
> > > https://bugs.kde.org/show_bug.cgi?id=275261 ? ).
> > > So you need to make a choice:
> > > - use sqlite and make it a problem for everybody
> > > - use mysql and those using NFS will have a problem
> >
> > > Right now I'd say even postgresql would be a better choice, but I have no
> > > idea how it works on NFS.
> > Unfortunately, the postgresql is not a solution. If you configure it
> > by hand to use an external database server, akonadi doesn't care and launch 
> > it's own instance.
> > (known bug which will be resolved in 4.8 from what was said to me)
>
> I wouldn't really consider that a bug. It'd be nice to have the choice
> between "use an external postgresql server" and "launch our own
> postgresql instance".

John it is a bug : the choice and the interface should work exactly the same as 
mysql.
run a private instance if I decide, run on central instance if I decide.

Now with postgresql (hopefully this is ending), if you use a private instance 
on an nfs home (don't do that)
or you have a shared desktop, what will happen when the postgresql server 
change its minor version
like 9.0 to 9.1 without any backups. Because the administrator of your 
workstation (you don't have root privs)
upgrade it ?

Are we sure, that if you destroy the akonadi data you are able to restart from 
scratch without reconfigure
those 16 imaps accounts and stuff ? And don't loose any data.
Like redownloading your 32GB of mail for imapsync ... even worst as thoses file 
now are just pointless file
their usage being lost during the remove of the database.

I can get that all wrong, but sorry the administration documentation shouldn't 
be build with strings
and git

> > > The fact is what I wrote: sqlite is buggy. I run into the mistake of using
> > > sqlite once, when I removed my akonadi config and run the opensuse akonadi
> > > instead of my self compiled one. And that was patched and used sqlite. I
> > > didn't notice for a day or so, but my number of gray hairs went up and
> > > couldn't understand why do I get so frequent hangs in KMail and the Akonadi
> > > server.
> > >
> > > Andras
> >
> > I've never consider sqlite as database engine.
>
> That's unfortunate - sqlite has an excellent SQL engine and is pretty
> reliable/durable. It's not intended to replace mysql or postgresql but
> for what it does, it does a very good job. 
You get me wrong it's a good sql engine, but by definition, not a server
see Andras explanation about concurrent access


-- 

Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador
GPG KEY : D5C9B751C4653227
irc: tigerfoot
-- 
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-kde+owner@xxxxxxxxxxxx