So I assume this is a rebranding of some other open source project with the amazon brand stuck on it, or is it actually something distinct?
PartiQL: One query language for all your data
51–60 of 88 posts
Re: PartiQL: One query language for all your data
#52Is this a GraphQL alternative or more for accessing DBs in the backend?
Re: PartiQL: One query language for all your data
#53Anyone know how this compares to Presto and zetasql?
Re: PartiQL: One query language for all your data
#54Is there a specification in anything besides PDF easily available to link to?
Re: PartiQL: One query language for all your data
#55This is pretty nice. If only because using a SQL dotted syntax seamlessly with JSON data.
Re: PartiQL: One query language for all your data
#56This is pretty nice. If only because using a SQL dotted syntax seamlessly with JSON data.
The SQL standard includes JSON support: https://modern-sql.com/blog/2017-06/whats-new-in-sql-2016
Re: PartiQL: One query language for all your data
#57This is pretty nice. If only because using a SQL dotted syntax seamlessly with JSON data.
Postres has had this for years. It's arrows instead of dots, but that's the only visual difference.
PG is working on adding SQL/JSON support for JSON Path queries for the next version. It'll be a major improvement but still not as nice as what PartiQL has here.
Re: PartiQL: One query language for all your data
#58Anyone know how this compares to Presto and zetasql?
I also am trying to figure out how this stacks up against Apache Drill.
Re: PartiQL: One query language for all your data
#59Is this a GraphQL alternative or more for accessing DBs in the backend?
Correct me if I'm wrong, but I believe the answer is "both", at least as far as I've read.
This appears to be for known queries. Unless it is designed for arbitrary queries, DoS is a likely problem.
Re: PartiQL: One query language for all your data
#60Is this a GraphQL alternative or more for accessing DBs in the backend?