I don't need your query language
antonz.org
I don't need your query language
1–10 of 304 posts
Re: I don't need your query language
#2In case anyone is wondering he is talking about EdgeDB (https://www.edgedb.com/)
Re: I don't need your query language
#3Query language for database queries! I thought the argument were going to be against application query languages, like the JQL for Jira and so on, which I actually like.
Re: I don't need your query language
#4The main issue with sql is, that it is the wrong way around, which eliminates all tooling support.
You need to state what you want (select a, b, c) before you tell it from where to get it (from). And no tooling can predict that.
So switching this, moving from and joins in front of select, might be everything needed to fix sql.
Re: I don't need your query language
#5The main issue with sql is, that it is the wrong way around, which eliminates all tooling support. You need to state what you want (select a, b, c) before you tell it from where to get it (from). And no tooling can predict that. So switching this, moving from and joins in front of select, might be everything needed to fix sql.
FROM users SELECT name, id, location WHERE name LIKE 'a%';
You know I think you're right.
Re: I don't need your query language
#6In case anyone is wondering he is talking about EdgeDB ( https://www.edgedb.com/ )
No. I'm talking about "SQL shaming" and about my preference for SQL over yet-another-query-language.
I have absolutely nothing against EdgeDB or its creators. As far as I can tell, it's a great product.
Re: I don't need your query language
#7The main issue with sql is, that it is the wrong way around, which eliminates all tooling support. You need to state what you want (select a, b, c) before you tell it from where to get it (from). And no tooling can predict that. So switching this, moving from and joins in front of select, might be everything needed to fix sql.
Ain't broke.
Re: I don't need your query language
#8The main issue with sql is, that it is the wrong way around, which eliminates all tooling support. You need to state what you want (select a, b, c) before you tell it from where to get it (from). And no tooling can predict that. So switching this, moving from and joins in front of select, might be everything needed to fix sql.
Ain't broke.
GP clearly shows why it is. I think SQL is great but their point is spot on.
Re: I don't need your query language
#9The main issue with sql is, that it is the wrong way around, which eliminates all tooling support. You need to state what you want (select a, b, c) before you tell it from where to get it (from). And no tooling can predict that. So switching this, moving from and joins in front of select, might be everything needed to fix sql.
C#'s LINQ (query syntax, not methods) got it right
var result = from s in stringList where s.Contains("Tutorials") select s;
Re: I don't need your query language
#10The main issue with sql is, that it is the wrong way around, which eliminates all tooling support. You need to state what you want (select a, b, c) before you tell it from where to get it (from). And no tooling can predict that. So switching this, moving from and joins in front of select, might be everything needed to fix sql.
While I agree with your point, this isn't really as big of a stopper for tooling as you make it seem. Many programming languages use something akin to import foo from bar and their tooling is just fine.