Re: Record ID corruption, posted by David Pilgram on Mon May 4 14:55:53 2020
|
Hi Frank,
There are two interesting points about the log file.
1. Entry 5658 is timestamped later than 5659, but is earlier in the entry list. It also is "In Reply to" 5659. despite |
|
Re: Record ID corruption, posted by Frank Baptista on Fri May 22 21:03:05 2020
|
Hi David,
Well, you've made some very interesting observations, and raised some excellent questions. So, I went back and did some homework, reviewing
a number of logbooks to find instances where this strange 'record twist' occurs. You had asked, "Do you have enough information to decided |
|
Re: Record ID corruption, posted by David Pilgram on Sat May 23 16:15:38 2020
|
Hi Frank,
Good bit of detective work. To me it suggests that something as yet undetermined occurs, that, when the 57th reply happens, causes the
issue. If that "something" hasn't happened, all is well. Apart from Heinz varieties (not true, in fact), 57 isn't an obvious |
|
Re: Record ID corruption, posted by Stefan Ritt on Tue Aug 4 13:38:05 2020
|
I tried to reproduce the problem with a fresh minimal logbook (the demo one coming from the distribution). Made 60 replies and all went well. So I wonder
if it has to do with some special settings in elogd.cfg. Can you reproduce the problem with an empty logbook and an edlog.cfg which contains just the minimal
settings? |
Date conversion, posted by Martin Neumann on Tue Feb 23 12:12:14 2021
|
Hi,
I am trying to figure out how ELOG works and I have a problem.
I have one datetime attribute, where I want the user to be able to enter the time in ISO8601 format (YYYY-MM-DD HH:MM) instead of the buttons. |
|
Re: Date conversion, posted by Andreas Luedeke on Tue Feb 23 17:20:39 2021
|
If you define a field as "datetime" then you'll get the standard ELOG input field for datetime. It will be stored as seconds of the epoch
(seconds since 1.1.1970).
You can define a field as a default string input, then it is stored as a string. But you can convert that string by a shell scripts into seconds |
|
Re: Date conversion, posted by Martin Neumann on Wed Feb 24 08:44:42 2021
|
I don't feel comfortable allowing the elog daemon to execute random shell scripts. Is there no other way?
Andreas
Luedeke wrote:
If you define a field as "datetime" then you'll get |
|
Re: Date conversion, posted by Sebastian Schenk on Tue Mar 2 15:17:56 2021
|
One other way would be to do the conversion on the client-side using javascript.
Overwrite the complete datetime input cell and add an event listener to either onChange of this input or the submit event, to trigger the conversion
before submitting, so elog would get the converted time. |