Re: [Tracker] What happened to the stored procedure GetFileContents?

[jamie <jamiemcc blueyonder co uk>]

On Mon, 2007-08-13 at 15:08 +0200, Laurent Aguerreche wrote:
> Le lundi 13 aoÃt 2007 Ã 13:48 +0100, jamie a Ãcrit :
> > On Mon, 2007-08-13 at 14:31 +0200, Anders Rune Jensen wrote:
> > > Hi
> > >
> > > I got an error today. Seems there's some code still using the old sql
> > > procedure GetFileContents (tracker-dbus-files.c:405). This procedure
> > > seems to have been removed somewhere between 0.54 and 0.6. svn log and
> > > Changelog file was no help.
> >
> > yes we plan to reimplement it
> >
> > I am currently recoding some of things to use sqlite's new incremental
> > blob IO to stream stuff (which will mean you will need sqlite 3.4 or
> > higher to run future tracker versions)
> >
> > We also plan on using alloca in conjunction with blob streaming to
> > prevent heap memory growing - I hope windows and solaris supports alloca
> > natively! (they must also support setting of thread stack sizes too for
> > this to work correctly)
>
> Before doing that, perhaps we could make a tracker 0.6.2 that would
> contain:
> * Fixed Evo emails (bug #465176)
> * Fixed handling of files containing character "'" in their name (they
> were not opened by xdg_open())
> * Add alarm call to tracker spawn as safeguard
> * Remove an error message while loading file sqlite-stored-procs.sql
> * Fixed bug #397210 (Desensitize Find button when search entry is empty)
> * Fixed warnings at building time in TST


> * Fixed crasher due to non valid utf-8 creeping through emails
that one is in 0.6.1?

> * Fixed memory leaks

in 0.6.1 too

> Plus, I updated french translation and a call to other translators to
> synchronize their work to latest source code would be helpful.

there are still some urgent crashers to fix - see :
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/131842 (crash in
email indexing - looks new?)

also look at :
https://bugs.launchpad.net/ubuntu/+source/tracker/ for full list of
outstanding stuff

the deskbar fix is also urgent - that must be in the next release

we dont need to release every week - every two weeks is good

jamie