Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in full text search.
Stefan
Dr Marta Divall wrote: |
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome.
David Pilgram wrote: |
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes. In your case suffixes may be better, but I hope you get the point.
Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.
Dr Marta Divall wrote: |
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best,
Marta
Stefan Ritt wrote: |
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best,
Stefan
Dr Marta Divall wrote: |
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks!
|
|
|
|
|
|