On Sat, Feb 23, 2008 at 1:27 AM, Peter Dzwig <pdzwig@...> wrote:
> thanks for the reply. I am going to split this into two parts. The first with
> regard to the search folders, then I will deal with the flag reset.
> so (i):
> Luis Rodrigo Gallardo Cruz wrote:
> > They're not "stored", but exist as views in the database. I assume you
> > could connect to it from another app and query it, but I don't know if
> > there'd be locking issues.
> But to get to the database I must know where it is. Is there some simple
> mechanism to allow me to copy its contents to an external file/set of
> ACTUALLY what I want to do is to use the filtered feeds, ie the contents of the
> Search Folders, save them as a searchable archive and pass their updating
> contents on to others, if you like a sort of closed circulation blog, but with
> the ability to search in the archive later to track the development of items.
> I can think of a dozen applications in which you might want to do something like
> this, so I am surprised that there isn't some kind of interface? Lars are you
> able to help?
I fear I need to reject the request. The DB storage/schema is an
which might change with every release. Also when Liferea is running some tables
or the whole DB file is locked and you won't be able to access it.
At the moment there is no export interface at all to realize the described
use case. In general when I think of your use case I would describe it as an
"information router" or a "feed processor", but not as a use case for an feed
consumer end point, a "news aggregator". Yahoo Pipes might be the direction
of what you look for.
For completeness I must mention a recent request from the Beagle guys, who
implemented an indexing backend reading the XML cache files of Liferea v1.0-
v1.2. Right now they also do not know how to index the cache contents of
Liferea. But for their use case one could implement a simple incremental
item id based mass-export interface.