Threaded emails, posted by Paul O'Shaughnessy on Fri Nov 21 11:16:04 2008
|
Can you email a thread of log entries. I think this would be a very useful function, which would enable the logger in effect to send an entire history of a particular issue to the interested parties. |
Last 3 days of log entries, posted by Paul O'Shaughnessy on Wed Feb 10 15:27:43 2010
|
Is it possible to create a drop down menu for the last 3 days of log entries. Currently we have the last day, month, 3 month, etc.
Reason being, after a weekend most people would like to view the log entries for the last three days. Can anyone help me out here? |
|
CSV importing, posted by Paul Harrington on Fri Apr 23 11:50:07 2004
|
I have been importing data from a CSV file into elog which has worked.
However I'd like to import data from the CSV file, directly to the 'text'
field, rather than just to one an attribute fields. Is it possible to do
this?
Paul |
|
can attrinute fields contain more that one line, posted by Paul Harrington on Tue Apr 27 17:40:25 2004
|
Is there any way to configure elog so that attribute fields can be edited
on more than line like the 'text' field?
(This would be useful so that attributes could contain larger portions of
text including line breaks)
thanks
Paul |
Re: CSV importing, posted by Paul Harrington on Fri Apr 30 12:58:54 2004
|
> > However I'd like to import data from the CSV file, directly to the 'text'
> > field, rather than just to one an attribute fields. Is it possible to do
> > this?
>
> Not yet, but I can implement it. Do you always have a column "text" in your
> CSV data or would you like to be able to select which column goes into the
> "text" field? Can you apend some sample CSV data so that I can have a look at it?
I've been trying an alternative approach which is basically to :
1. Import the data (not including the text field) into elog from a CSV file
2. Stop the elog server
3. Use a perl script to add each text entry to the appropriate record within the
logbook file.
(I.e. between the =============================== of the appropriate entry
and the next ' |
|
length of fields, posted by Paul Harrington on Wed Feb 23 13:02:59 2005
|
When creating/updating entries in elog, excluding the main text field are
there any limits on the size of the other fields?
many thanks
Paul |
|
Re: length of fields, posted by Paul Harrington on Thu Mar 3 10:21:21 2005
|
> > When creating/updating entries in elog, excluding the main text field are
> > there any limits on the size of the other fields?
>
> Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> currently set to 1500 characters. You can try to increase this and recompile,
> but at some point you will produce a stack overflow and elogd will crash. So
> the current length is a compromise.
>
> - Stefan
Thanks. Thats useful to know.
Paul |
|
Re: length of fields, posted by Paul Harrington on Tue Mar 8 13:16:14 2005
|
The reason for the earlier question is that we are trying to use Elog to store
data in a form we'd need to store more 1500 characters in more than one field.
Is it possible to get around this problem by having more then one main text field
per record?
thanks
Paul
> > > When creating/updating entries in elog, excluding the main text field are
> > > there any limits on the size of the other fields?
> >
> > Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> > currently set to 1500 characters. You can try to increase this and recompile,
> > but at some point you will produce a stack overflow and elogd will crash. So
> > the current length is a compromise.
> >
> > - Stefan
>
> Thanks. Thats useful to know.
>
> Paul |