@KK,
Currently I have a checkbox editable and wish to have some flexibility with naming my values. If I use bare numeric minimum for values (1, 2, 3, .. ) then less than 100 such numeric values would already hit the limit, taken into account that values must be enclosed with 1 symbol from both sides to be correctly used later in custom_field filtering (100, 101, ... ,999).
TLDR
I will add to this question some description of the usecase to prevent any ranting about 'this is not for everybody'.
Actually, everybody can have some kind of form (as I am now), which may have 100-200 YES/NO answers. Making such a form with separate checkbox editable for each question row has proved itself inconvenient, given the amount of background calculations Couch does upon each page load. So even 300 editables in a template is overkill for it (slows down dramatically). SO, my optimisation now includes making it ONE editable with multiple options and take care of the rest (packing multiple regular 'unbound' inputs together into one list of values) with my code in k_success.
Thanks.
Currently I have a checkbox editable and wish to have some flexibility with naming my values. If I use bare numeric minimum for values (1, 2, 3, .. ) then less than 100 such numeric values would already hit the limit, taken into account that values must be enclosed with 1 symbol from both sides to be correctly used later in custom_field filtering (100, 101, ... ,999).
TLDR
I will add to this question some description of the usecase to prevent any ranting about 'this is not for everybody'.

Thanks.