mysql in execute, posted by Stefan Kanitz on Fri Dec 12 08:57:41 2008
|
Hello all,
i have a question to mysql inexecute: |
Re: mysql in execute, posted by Stefan Ritt on Fri Dec 12 09:16:19 2008
|
Stefan Kanitz wrote:
|
|
Re: mysql in execute, posted by Stefan Kanitz on Sat Dec 13 14:31:53 2008
|
Stefan Ritt wrote:
|
Attribute value lost when adding to another extendable attribute, posted by Dennis Seitz on Thu Dec 11 03:13:31 2008
|
Here is an excerpt from my config file:
Type Last Edit = datetime
Preset Last Edit =$entry time |
|
Re: Attribute value lost when adding to another extendable attribute, posted by Stefan Ritt on Fri Dec 12 08:07:59 2008
|
Dennis Seitz wrote:
|
|
Re: Attribute value lost when adding to another extendable attribute, posted by Dennis Seitz on Sat Dec 13 02:13:51 2008
|
Stefan Ritt wrote:
|
Conflict between Select-Edit and attribute types, posted by Richard Stamper on Thu Dec 11 17:50:35 2008
|
When doing a Select->Edit operation, if an attribute has a type of "numeric" and the records selected already have (some) values for that
attribute, then the "- keep original values -" message that is inserted to indicate that the values should be preserved causes the type check
to fail. |
|
Re: Conflict between Select-Edit and attribute types, posted by Stefan Ritt on Fri Dec 12 07:45:14 2008
|
Richard Stamper wrote:
|
Please add Subst on Duplicate, posted by Dennis Seitz on Tue Dec 9 00:25:52 2008
|
I would like to be able to substitute some attribute values when an entry is duplicated. I don't see Subst on Duplicate available in the cfg file
syntax. Can you add that?
|
|
Re: Please add Subst on Duplicate, posted by Stefan Ritt on Tue Dec 9 08:04:00 2008
|
Dennis Seitz wrote:
|
|
Re: Please add Subst on Duplicate, posted by Dennis Seitz on Wed Dec 10 03:11:01 2008
|
Stefan Ritt wrote:
|
|
$entry time not readable by Subst, else not datetime type?, posted by Dennis Seitz on Wed May 7 17:10:07 2008
|
I posted this on the end of an earlier thread but I thought it might be better to repost as a separate thread:
|
|
Re: Re: $entry time not readable by Subst, else not datetime type?, posted by Dennis Seitz on Thu May 15 01:06:21 2008
|
[quote="Dennis Seitz"]I posted this on the end of an earlier thread but I thought it might be better to repost as a separate thread:
|
|
Re: Re: $entry time not readable by Subst, else not datetime type?, posted by Stefan Ritt on Mon Jun 2 12:01:47 2008
|
[quote="Dennis Seitz"]OK, now I realize how stupid I sound here. To partially answer my own question: $entry time is a string and Last Edit is now a number
since I have changed it to the datetime type so that it will sort properly.
|
|
Re: Re: $entry time not readable by Subst, else not datetime type?, posted by Dennis Seitz on Mon Jun 2 23:41:15 2008
|
[quote="Stefan Ritt"][quote="Dennis Seitz"]OK, now I realize how stupid I sound here. To partially answer my own question: $entry time is a string and Last
Edit is now a number since I have changed it to the datetime type so that it will sort properly.
|
|
Re: Re: $entry time not readable by Subst, else not datetime type?, posted by Stefan Ritt on Tue Jun 3 12:47:13 2008
|
[quote="Dennis Seitz"]Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference)[/quote]
Yes, of course I mean '$entry time', sorry for the misspelling. |
|
Re: Re: $entry time not readable by Subst, else not datetime type?, posted by Dennis Seitz on Thu Jun 5 01:38:17 2008
|
[quote="Stefan Ritt"][quote="Dennis Seitz"]Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference)[/quote]
Yes, of course I mean '$entry time', sorry for the misspelling.[/quote]
|
|
Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?, posted by Dennis Seitz on Fri Nov 21 18:21:36 2008
|
[quote="Dennis Seitz"][quote="Stefan Ritt"][quote="Dennis Seitz"]Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date
in the elogd.cfg reference)[/quote]
|
Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?, posted by Stefan Ritt on Mon Nov 24 20:00:05 2008 
|
[quote="Dennis Seitz"]FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
|
|
Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?, posted by Dennis Seitz on Tue Nov 25 17:01:55 2008
|
[quote="Stefan Ritt"][quote="Dennis Seitz"]FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
|
|
Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug?, posted by Dennis Seitz on Tue Dec 9 00:22:41 2008
|
[quote="Dennis Seitz"][quote="Stefan Ritt"][quote="Dennis Seitz"]FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
|
Auto-increment attributes, posted by Steve Williamson on Wed Nov 26 10:00:25 2008
|
We have an auto-incrementing reference attribute defined as:
# RFC
|
|
Re: Auto-increment attributes, posted by Steve Williamson on Fri Dec 5 16:14:19 2008
|
Steve Williamson wrote:
We have an auto-incrementing reference attribute defined as: |
|
Re: Auto-increment attributes, posted by Stefan Ritt on Mon Dec 8 10:09:14 2008
|
I finally found some time to address this problem. It is indeed related to the fact that the new number gets assigned when you click on 'New'.
So if two people edit the new entries at the same time, they get assigned the same number. To fix this problem, I made the tag generation work with the
'Subst' command, which is evaluated at the entry submission, and not when you click on 'New'. So to make this work, you need to upgrade |
|
Re: Auto-increment attributes, posted by Steve Williamson on Mon Dec 8 13:13:13 2008
|
Stefan Ritt wrote:
I finally found some time to address this problem. It is indeed related to the fact that the new number |
|
Change background color, posted by mike cianci on Sat Dec 6 22:30:56 2008
|
I copied the following line from the ELOG documentation file to my config file (with the appropriate changes to the attribute and value fields)
and nothing happens. Am I missing something?
Style importance severe = background-color:red
Thanks for all your help.
|
|
Re: Change background color, posted by Stefan Ritt on Mon Dec 8 08:59:56 2008
|
mike cianci wrote:
|
|
How to attach screen shot in elog, posted by weiluo on Tue Dec 2 01:10:39 2008
|
I want to know if there were some way to insert a screen shot directly into the log book instead of going through the "save-attach" procedure.
i.e. add some plug in button to do this under Linux?
Or, can I just make a plain log file "xxxx.log" and put it into the directory? Will that work? |
|
Re: How to attach screen shot in elog, posted by Stefan Ritt on Tue Dec 2 10:20:52 2008
|
weiluo wrote:
I want to know if there were some way to insert a screen shot directly into the log book instead of going through |
|
Re: How to attach screen shot in elog, posted by weiluo on Tue Dec 2 17:10:05 2008
|
Stefan Ritt wrote:
|
|
Re: How to attach screen shot in elog, posted by Stefan Ritt on Tue Dec 2 17:15:36 2008
|
weiluo wrote:
|
|
Re: How to attach screen shot in elog, posted by weiluo on Tue Dec 2 17:18:10 2008
|
Stefan Ritt wrote:
|