Re: mysql in execute, posted by Stefan Kanitz on Sat Dec 13 14:31:53 2008
|
| Stefan Ritt wrote: |
|
| Stefan Kanitz wrote: |
|
This doesn't work:
Execute new = mysql -h localhost -u root -D test1 -e "insert into `test2` (Autor, Adressat, Teil1, Teil2, Teil3,
Teil4, Teil5, Teil6, Teil7, Teil8 ) values ('$Autor', '$Adressat' , '$Teil1', '$Teil2', '$Teil3', '$Teil4', '$Teil5',
'$Teil6', '$Teil7', '$Teil8' )"
|
In the elogd.cfg file, you cannot have multi-line options. Either you put everything on a single line (I guess there is also some limit at a few hundred characters) or you call a batch file which then calls the mysql command.
|
Thanks!
|
Grouping Logbooks, posted by mike cianci on Sun Dec 14 17:04:24 2008
|
I really appreciate your help and I hope that my questions warrant your time.
What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.
Three logbooks
Logbook A
Logbook B
Logbook C (just informational, write protected)
Two Groups
Top Group 1 = Logbook A, Logbook C
Top Group 2 = Logbook B, Logbook C
What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.
Actual Code:
;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps
|
|
Re: Grouping Logbooks, posted by Stefan Ritt on Mon Dec 15 09:01:35 2008
|
| mike cianci wrote: |
|
I really appreciate your help and I hope that my questions warrant your time.
What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.
Three logbooks
Logbook A
Logbook B
Logbook C (just informational, write protected)
Two Groups
Top Group 1 = Logbook A, Logbook C
Top Group 2 = Logbook B, Logbook C
What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.
Actual Code:
;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps
|
You cannot put the same logbook into two groups. All you can do is to define two logbooks C1 and C2, and force their data directories to be the same (via the "Subdir = ..." directive), so they will actually look at the same data. |
|
Problems with execute delete, posted by Stefan Kanitz on Tue Dec 23 11:02:26 2008
|
Hi all,
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
Here is the config:
Attributes = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten
Show Attributes = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten
Show Attributes Edit = Counter, Autor, Adressat, Start, Ende, Mitteilung, TextBeachten
Type Start = date
Type Ende = date
Required Attributes = Autor, Adressat, Start, Ende, Mitteilung
Extendable options = Adressat
Preset Autor = $long_name
Preset Counter = SoMi-#####
Locked Attributes = Autor, Counter
Required Attributes = Adressat, Start, Ende, Mitteilung
Options Adressat = Alle, 1. Semester, 2. Semester, 3. Semester, 4. Semester, 5. Semester, 6. Semester, 7. Semester, 8. Semester
MOptions Textbeachten = Bitte Mitteilungs-Text anzeigen lassen
Execute new = C:\xampp\mysql\bin\mysql.exe -h localhost -u root -p123456 -D screen -e "insert into somi (counter,adressat,start,ende,kumi,mitlami,lami) values ('$Counter', '$Adressat', '$Start', '$Ende', '$Mitteilung', '$TextBeachten', '$text')"
Execute delete = C:\xampp\mysql\bin\mysql.exe -h localhost -u root -p123456 -D screen -e "delete from somi where counter='$Counter'"
Thanks in advance and Merry Christmas!!
Steve
|
|
Re: Problems with execute delete, posted by Stefan Ritt on Tue Dec 23 11:34:25 2008
|
| Stefan Kanitz wrote: |
|
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
|
Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix. |
|
Re: Problems with execute delete, posted by Stefan Kanitz on Tue Dec 23 12:17:06 2008
|
| Stefan Ritt wrote: |
|
| Stefan Kanitz wrote: |
|
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
|
Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix.
|
This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))
Steve
|
|
Re: Problems with execute delete, posted by Stefan Ritt on Tue Dec 23 12:22:51 2008
|
| Stefan Kanitz wrote: |
|
| Stefan Ritt wrote: |
|
| Stefan Kanitz wrote: |
|
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
|
Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix.
|
This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))
|
For 'execute edit' this worked from the beginning. |
|
Re: Problems with execute delete, posted by Stefan Kanitz on Tue Dec 23 12:31:39 2008
|
| Stefan Ritt wrote: |
|
| Stefan Kanitz wrote: |
|
| Stefan Ritt wrote: |
|
| Stefan Kanitz wrote: |
|
i have problems with execute delete (execute new works fine) in following config (the attribute 'Counter' will not evaluated). Can anybody help me?
|
Attribute substitution on 'execute delete' was not implemented, since I thought that the ELOG message ID would be used as the primary key in an SQL database, so one would not need the attributes. I added howver this functrionality in SVN revision 2159, so the next release will contain this fix.
|
This sounds very good! Thank you very much (Could you please add this functionality for execute edit too? Please :-))
|
For 'execute edit' this worked from the beginning.
|
Thank you! |
|