I need to increase the answer code length - by: Ben_V

Hi Tammo,

tammo wrote: Isn't this very dangerous, since when updating possibly one (disastrous!), multiple (also disastrous) or all these modified files may be overwritten?

As you already know, GNU GPL licensed softwares allow to adapt the code to fit all your needs, so it's easy to understand that you can't get everything (huge customization + keep receiving standard updates from the master branch)
This said you're 100% right; This have to be said and said again:
Do not apply any standard actualization to customized installations except if you know exactly what you are updating. Always write down all your critical changes and backup db & files.

tammo wrote: Shouldn't this be sent to the developers either as a change request, and when it is very important, with some money or as a well documented Pull Request?

I'm sorry but I'm not really sure about how answer your question for the following key reasons:

1) We are not exactly talking about a new feature but about the dev team agreement to increase a critical value (sounds easy but possible side effects).
2) This limit is well known; there are some existing (old & recent) related entries in the forum & feature(s) request(s)
Additionally you may find a clear allusion included in Tom's todo list (around 2012).
manual.limesurvey.org/User:TMSWhite

TMSWhite wrote: At present, the main features which still need to be ported include:

• new tables to support item banking and standardization of items using LOINC and SNOMED