Revision as of 06:29, 16 June 2022 edit 2409:4043:209c:b221:3990:f39e:91cc:c03e (talk) →Questions about use of Whatsapp: new section ← Previous edit		Revision as of 06:55, 16 June 2022 edit undo 2601:648:8202:350::90b2 (talk) →Split/Explode calculations in SQL Next edit →
Line 39: I do not know if that term applies within the SQL ecosystem, but across the Python/Matlab/etc. scientific calculation world, that is called "vectorized code" or "[[array programming]]". [https://www.cs.cornell.edu/courses/cs1112/2015sp/Exams/exam2/vectorizedCode.pdf Here’s an exam sheet] with easy-to-understand examples. [[User:Tigraan\|<span style="font-family:Tahoma;color:#008000;">Tigraan</span>]]<sup>[[User talk:Tigraan\|<span title="Send me a silicium letter!" style="color:">Click here for my talk page ("private" contact)</span>]]</sup> 17:09, 14 June 2022 (UTC) What with the unpacking and packing, this is essentially ''[[unfold (higher-order function)\|unfold]]''–''[[map (higher-order function)\|map]]''–''[[fold (higher-order function)\|fold]]'', which is also related to the [[MapReduce]] paradigm. Like Tigraan, I don't know if such terminology has gained any currency in the SQL world.  --[[User talk:Lambiam\|Lambiam]] 19:11, 14 June 2022 (UTC) That kind of thing is usually not done in SQL, which traditionally puts one value per cell. Lately there have been some extensions to put JSON or arrays into SQL, but that is pretty nonstandard and something of an antipattern. But it slightly resembles some programming patterns like [[map-reduce]]. [[Special:Contributions/2601:648:8202:350:0:0:0:90B2\|2601:648:8202:350:0:0:0:90B2]] ([[User talk:2601:648:8202:350:0:0:0:90B2\|talk]]) 06:55, 16 June 2022 (UTC) = June 15 =

Wikipedia:Reference desk/Computing: Difference between revisions