It sounds wise to save the default value in the responses table. And not construct the data. If the code changes, the default value might change. To be sure about what value was chosen when the survey was conducted save the default value to the database. The additional storage is not wasted.

You don't want to have the return of no data as an proxy for default data. That sounds like begging for issues in the long run.

Keep it simple stupid. If storage is an issue, LimeSurvey should start with the session size abuse ;-)

QuestionAttribute::model()->findByAttributes() only returns DB values

yes : it's the definition … https://www.yiiframework.com/doc/api/1.1/CActiveRecord#findByAttributes-detail

If need a getQuestionAttribute near https://github.com/LimeSurvey/LimeSurvey/blob/12cd8e5a2ca9975a3a45a0b10ca0630344d55e7d/application/models/QuestionAttribute.php#L210 : good

I already make a feature request near this : https://bugs.limesurvey.org/view.php?id=14228 or https://bugs.limesurvey.org/view.php?id=14248 some year ago.

It sounds wise to save the default value in the responses table. And not construct the data. If the code changes, the default value might change. To be sure about what value was chosen when the survey was conducted save the default value to the database. The additional storage is not wasted.

It work like this for years , and we never have issue reported … but why not. It's the case (when you save question) in 4.X currentlyè

Else : it make bigger lss size. To test :

1. Import https://github.com/LimeSurvey/LimeSurvey/blob/master/docs/demosurveys/ls3_sample_survey_multilingual_fr_de_en_it.lss in 4.X
2. Goes to each question and save value
3. Export : compare size.

My opinion :

1. Create a getQuestionAttribute($qid,$attribute, $language = null) : return DB value or default value if not set, by current language or set if i18n
2. Add it in LimeSurvey API
3. Add it in TwigRender function

Then :

1. Plugin dev are happy, they have something fixed
2. QuestionTheme dev are happy : they have something

Saving all the values in the database does not make sense either, because saving redundant values is also a bad idea.
Use the functions (getQuestionAttributes) from the model and you are good.

Saving all the values in the database does not make sense either, because saving redundant values is also a bad idea.

It's the case in 4.4, need to report ?

With ls3_sample_survey_multilingual_fr_de_en_it lss file updated maybe ?