| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1939
|
05 Jun 2020 |
Stefan Ritt | Suggestion | ODB++ API - documantion updates and odb view after key creation | Hi Marius,
your fix is good. Thanks for digging out |
|
|
1940
|
08 Jun 2020 |
Marius Koeppel | Suggestion | ODB++ API - documantion updates and odb view after key creation | Hi Stefan,
I agree with your explanation about the size |
|
|
1951
|
16 Jun 2020 |
Marius Koeppel | Suggestion | ODB++ API - documantion updates and odb view after key creation | Hi Stefan,
I played around with the code a bit more |
|
|
1956
|
23 Jun 2020 |
Stefan Ritt | Suggestion | ODB++ API - documantion updates and odb view after key creation | Hi Marius,
thanks for your help, you identified the |
|
|
1957
|
24 Jun 2020 |
Marius Koeppel | Suggestion | ODB++ API - documantion updates and odb view after key creation | Hi Stefan,
now everything works well (Tested on: OpenSuse |
|
|
2611
|
30 Sep 2023 |
Gennaro Tortone | Bug Report | ODB page and hex values |
Hi,
|
|
|
2612
|
01 Oct 2023 |
Stefan Ritt | Bug Report | ODB page and hex values | Thanks for reporting this bug, I fixed it
in the last commit.
|
|
|
418
|
27 Nov 2007 |
Stefan Ritt | Info | ODB links to array elements implemented | In revision 4090 I implemented ODB links to
individual array elements. Now you
can have for example:
|
|
|
1953
|
18 Jun 2020 |
Ruslan Podviianiuk | Forum | ODB key length | Hello,
I have a question about length of the name |
|
|
1954
|
18 Jun 2020 |
Stefan Ritt | Forum | ODB key length | No. But if you need more than 32 characters,
you do something wrong. The
information you want to put into the ODB |
|
|
2365
|
23 Mar 2022 |
Hunter Lowe | Forum | ODB has issue with example analyzer | Trying to play with midas file but I get error:
[Analyzer,ERROR] [odb.cxx:845:db_validate_name,ERROR] |
|
|
1367
|
04 May 2018 |
Francesco Renga | Forum | ODB full | Dear expert,
I'm developing a frontend and I'm getting
this kind of error at each event:
|
|
|
1368
|
04 May 2018 |
Stefan Ritt | Forum | ODB full | Two options:
1) Do NOT send your events into the ODB. |
|
|
1378
|
20 Jul 2018 |
Konstantin Olchanski | Forum | ODB full | Concurrence.
Normally, MIDAS data events are saved to |
|
|
1760
|
13 Jan 2020 |
Peter Kunz | Forum | ODB dump format: json - events 0x8000 and 0x8001 missing | MIDAS version: 2.1
GIT revision:
Tue Dec 31 17:40:14 2019 +0100 - midas-2019-09-i-1-gd93944ce-dirty |
|
|
1763
|
13 Jan 2020 |
Konstantin Olchanski | Forum | ODB dump format: json - events 0x8000 and 0x8001 missing | (Please post messages in "plain" mode, they
are much easier to answer)
|
|
|
1768
|
13 Jan 2020 |
Peter Kunz | Forum | ODB dump format: json - events 0x8000 and 0x8001 missing | Re: MIDAS versions
Thanks for pointing that out. I wasn't actually |
|
|
1772
|
13 Jan 2020 |
Konstantin Olchanski | Forum | ODB dump format: json - events 0x8000 and 0x8001 missing | For using the release branch read the messages
in this thread. Most of the time, the develop
branch is fine, except when we are developing |
|
|
202
|
24 Mar 2005 |
Stefan Ritt | Info | ODB dump format switched to XML | Dear midas users,
I have changed the ODB dump format to XML. |
|
|
203
|
29 Mar 2005 |
Stefan Ritt | Info | ODB dump format switched to XML | > All the XML functionality is implemented
in the new mxml.c/h library, which has
> been added to the distribution, and which |
|