18:56 can LINQ abstract over predicates if the predicate can't be expressed as SQL, or will it literally have to get every tuple back and apply the F# predicate to it in the client? Or is there something in the server that can execute the predicate?
Im probably missing the whole point, but I’ll ask my question anyway. I don’t understand what this talk could possibly have taught people? I expected to see how to use F# to generate SQL, and then use this. I expected something like Common Lisp macro’s to be honest, or how to create our own ORM library. But this talk doesn’t define the “run” and “database” functions at all. So I’m probably just missing the point 😅 hope someone can answer my question and point me to materials I might need to read up on to better grasp this video.
I don't think so. It doesn't even have functions or procedures, or at least it didn't when I learnt it, it was strictly a language to define a database, the relations in it and some simple invariants the data and relations should have and to populate and update that database and do queries on it. You couldn't do a recursive query, say to explode a particular assembly in a manufacturing database to find the bill of materials, instead you had to basically do this in some other language that could throw out SQL queries and accumulate the results. And yes, most program logic had to also be expressed in that other language also, although there are now things like stored procedures and rules.
![คุณอาเรียโต๊ะข้างๆ พูดรัสเซียหวานใส่ซะหัวใจจะวาย ตอนที่ 4 [ซับไทย] 【Ani-One Thailand】](http://i.ytimg.com/vi/_vK_cden2f8/mqdefault.jpg)
This guy really likes lambda calculus. :)
people dont understand how truly awesome this type of guy is - senior guru of the digital arts
thanks !!
Finally found someone who uses F#.
18:56 can LINQ abstract over predicates if the predicate can't be expressed as SQL, or will it literally have to get every tuple back and apply the F# predicate to it in the client? Or is there something in the server that can execute the predicate?
Im probably missing the whole point, but I’ll ask my question anyway.
I don’t understand what this talk could possibly have taught people? I expected to see how to use F# to generate SQL, and then use this. I expected something like Common Lisp macro’s to be honest, or how to create our own ORM library. But this talk doesn’t define the “run” and “database” functions at all. So I’m probably just missing the point 😅 hope someone can answer my question and point me to materials I might need to read up on to better grasp this video.
The slides: homepages.inf.ed.ac.uk/wadler/papers/qdsl/curryon.pdf
Wait, SQL has recursion, right?
I don't think so. It doesn't even have functions or procedures, or at least it didn't when I learnt it, it was strictly a language to define a database, the relations in it and some simple invariants the data and relations should have and to populate and update that database and do queries on it.
You couldn't do a recursive query, say to explode a particular assembly in a manufacturing database to find the bill of materials, instead you had to basically do this in some other language that could throw out SQL queries and accumulate the results. And yes, most program logic had to also be expressed in that other language also, although there are now things like stored procedures and rules.
@@MrGoatflakes Actually recursive queries in SQL do exist now, as of standard SQL:1999. You could do that you described.
@@skyeplus oic
I forgot it also has stored procedures
oof this kinda looks like a bad idea