Formal option for persisted computed columns
Software Factory
Could we get an option to set the persisted flag on computed columns? To my understanding this should improve the performance of such columns (with more data usage as a trade-off). Is there any reason for this option to not be there yet?
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Keep in mind there are some limitations when using persisted computed columns, they must be deterministic.
However, as long as we do not need other parts of the Software Factory, IAM, Indicium or GUI's to make a distinction between persisted and non-persisted columns there's not much to gain.
Yes, there are no sanitizations done on the expressions you write here, so be careful ;)
I wouldn't go as far as to call it SQL injection as this is a setting configured during the development phase by a developer, not in a live environment by an end-user. None of these snippets ever be modifyable by an end-user so there's no risk there. Same counts for templates, SQL prefilters, validations etc.
I use the solution, suggested by Anne, quite often, but I still think the option to set persisted as an option is preferable as it is a property of the calculated column and not part of the calculation/expression itself. Upvote.
I agree with@Harold and @Arie V that this should be a formal setting. I note down I learned this four years ago but had forgotten it in the meantime. A checkbox / formal setting would have lead to a situation you cannot forget and a more transparent way of solving this problem.