The Next 50 Years of Databases (2015)

Re:The Next 50 Years of Databases (2015) by crimsonalucard on Monday November 11, 2019 @05:23PM (#21509543)

I think even before we get there, one of the big issues with SQL is how we write optimized queries. It's basically involves memorizing a bunch of hacks and hoping that those hacks compile into something that is performant.

Before we use these 5th generation languages to write natural language queries we need an API that is sufficiently high level and possible to logically optimize without resorting to hacks.

[ Parent | on HN ]

Re:The Next 50 Years of Databases (2015) by Pxtl on Monday November 11, 2019 @06:32PM (#21510075)

Exactly. I always say SQL servers are kernel of beautiful relational theory wrapped in about 4 feet of duck-tape and bubble gum.

The SQL server presents itself as a black box, saying "just say what you want and I'll figure out how to get it" and then completely fails to deliver on this and you have to open up the black box and find that its insides are dark and scary and full of jagged sharp ends.

[ Parent | on HN ]

Re:The Next 50 Years of Databases (2015) by richardwhiuk on Tuesday November 12, 2019 @04:27AM (#21512766)

All layers of abstraction are leaky when you care about performance sufficiently.

[ Parent | on HN ]

Re:The Next 50 Years of Databases (2015) by crimsonalucard on Tuesday November 12, 2019 @12:17PM (#21515851)

To an extent. Some layers are significantly more leaky than others. Rust vs. SQL for example.

[ Parent | on HN ]