I ended with 125384 entries like the one above.

Everything works fine but ......... [U]tteerrrriibbllee[/U] [B]slow[/B].  CPU usage is constant at 99%.  

I tried to split the one file produced by the import into 2 chunks but that did not improve the situation.

My question is : Is there a rule of thumb for the size of the "database" in which elog keeps it's performance, or better : is there a solution for this for elog.


 

First thanks for the great software! My only question would be how to implement audit trail feature. I know you can control who edits and that's great but in regulated environments like mine there's a requirement that the original record, the one edited, is not deleted or overwritten. If not possible right now the only thing I could think of is a mechanism, maybe possible thru configuration, that when the record is edited it is copied to an audit trail logbook (i.e. if logbook name is 'test' it's audit logbook will be named 'test-audit' which is read only) and have a link to the audit trail of the record (show only changes of the current record).

I'm more than aware that it's possible thru configuration but I'm short on that dept. Any help/idea?

Thanks in advance!

You can achieve this via replies. First you disable any edits on the original message by removing the Edit command via 'Menu commands' or by using 'Restrict edit time' appropriately. If someone wants to edit an entry, she or he makes a reply. If the original entry is formatted with ELCode, it will be enclosed by a [quote] tag, which can be easily removed. Then the text can be edited and submitted. This way you get the history of an entry in a chain of replies. That's the only way I see to accomplish this functionality.