[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: Database library (was Re: Bug?)
From:       Nicholas Hagen <nicholas () Tommy ! digi ! com>
Date:       2000-12-23 17:35:28
[Download RAW message or body]

I agree...using a database seems to give KMail several advantages to its 
system, and if the implementation only means changing a few classes, I think 
it would be a logical idea to look into it for the future for a later 
release.  And the use of import/export tools to grab Mail from places like 
Netscape, etc and then store to the Database would in my opinion relatively 
simple to develop.  But yeah...stuff like IMAP and functionality and bug 
fixes should be first.

Nick

On Friday 22 December 2000 10:25 am, Don Sanders wrote:
> We need persistent message ids. Currently there will be problems unmarking
> a message as read if it is moved (or copied) from one folder to another.
>
> It's probably worth investigating using a database library like gigabase to
> store mail in, instead of the current mbox format. This is not the same as
> using a 'real' (out of process) database, it just means linking to another
> library. This can potentially buy us a few things.
>
> 1) Persistant message ids so that messages can be found even after events
> have been processed (and a message may have been moved to a different
> folder).
>
> 2) Much faster move/copy and filters. Because the entry for a message in
> the database can contain a list of folders the message is in. And we simply
> have to change the list of folders entry when the message is moved.
>
> 3) No need to worry about compaction.
>
> 4) Virtual folders, it will be easy to say find all unread messages in any
> folder, and create a new folder containing just those messages.
>
> 5) Message links. A message can be in several folders and when it is read
> in one folder it will (well can) be marked as read in all folders it is
> contained in.
>
> 6) Archiving and advanced filters will be easier. We can iterate over all
> messages easily and say check to see which message are older than some
> date.
>
> 7) Perhaps we can add new fields to a message without changing the index
> file format.
>
> That's all I can think of off the top of my head.
>
> This doesn't necessarily require changing any KMail classes, if will just
> require a new implemenation of KMFolder (and KMFolderDir), and perhaps new
> classes for iterating over all messages, and getting a persistent message
> id from a message and finding a message given a persistent message id.
>
>
> But really IMAP support is much more important and this stage and the focus
> should be on IMAP, and fixing bugs.
>
> BFN,
> Don.
>
> On Friday 22 December 2000 14:02, Nicholas Hagen wrote:
> > Yeah,
> >
> > It was me who sent it...forgot that I never submitted a real patch.  But
> > I never repiled back to it, because of that fact of the drafts folder.
> > However, I could make a real patch that does fix the problem of
> > cancelling while still running KMail, but if the user exits and then
> > re-opens and sends the message it won't get a replied to sign.  Maybe we
> > need to store somewhere in the mail being sent the reply to information
> > so we can easily find the associated message and mark that message as
> > replied to once the user does in fact send the message to the outbox. 
> > Though, I don't see this to be much of a bug to worry bout.
> >
> > Let me know if you want the real patch, not a description.
> >
> > Nick
> >
> > On Friday 22 December 2000  5:09 am, Michael Häckel wrote:
> > > On Friday 22 December 2000 03:42, Nicholas Hagen wrote:
> > > > This is a known issue.  I had a patch which fixed part of it, but due
> > > > to the drafts folder it does not fix the issue that if the message is
> > > > moved to drafts folder and then kmail shutdown and then restarted and
> > > > then the message removed and cancelled.
> > >
> > > Some time ago, indeed a "patch" for that was send to the list, I'm not
> > > sure if it was you or someone else, but it was not a real patch, but a
> > > description what to change in the code. It did not work for me and the
> > > one who sent the patch did not reply.
> > >
> > > Regards,
> > > Michael Häckel
> > > _______________________________________________
> > > Kmail Developers mailing list
> > > Kmail@master.kde.org
> > > http://master.kde.org/mailman/listinfo/kmail
> >
> > _______________________________________________
> > Kmail Developers mailing list
> > Kmail@master.kde.org
> > http://master.kde.org/mailman/listinfo/kmail
>
> _______________________________________________
> Kmail Developers mailing list
> Kmail@master.kde.org
> http://master.kde.org/mailman/listinfo/kmail
_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]