On 29-05-2017 04:41, Pali Rohár wrote:
> On Sunday 28 May 2017 23:04:57 Paulo Lieuthier wrote:
>> Hey, Pali. I thought history2 was the best option today.
> 
> history2 does not support rich text messages, so no is not a good.
> 
>> I just updated my
>> timetable aiming to convert the XML-based one, and start by preparing the 
>> schema
>> and searching for a good database solution.
> 
> Look into mailing list archive. There were already some ideas, so better
> do not invent wheel from the start, but rather fix design of some
> existing schemas.

I had already tried to read previous discussions on the mailing list archive,
but it is always empty to me ("No messages have been posted to this list yet, so
the archives are currently empty").

>> Do you think converting the SQLite-based plugin into another backend is 
>> worth it
>> (that if SQLite is not the chosen database solution)? I can do it if there is
>> enough time.
> 
> I think SQLite should be fine for metadata. If text messages itself
> should be in SQLite it would depends on doing some experiments if it is
> fast enough. Also we need full text search support. SQLite has some
> plugins for it, but probably different indexes would be better (or
> not?).

You are right, better not to reinvent the wheel. But I'm yet to understand where
we are right now, to be able to move forward. From what I understood, I should
start from the XML-based plugin, but (probably) use SQLite for storage. That
sounds like a merge, right?

Maybe I'm missing something obvious to get to the ML archive, maybe someone
should fix some permission thing. I'd really like to read the previous
discussions. Anyway, I need help to know which direction to go to.

Paulo

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to