Live data from Hacker News

PartiQL: One query language for all your data

aws.amazon.com

51–60 of 88 posts

Re: PartiQL: One query language for all your data

#51
post #24

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?

The posted article says it was designed and built in house, where it is currently dogfooded, and the specification doc is dated today (2019-08-01):

https://partiql.org/assets/PartiQL-Specification.pdf

Re: PartiQL: One query language for all your data

#56
post #55

This 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

The SQL standard is different from what databases actually support. No RDBMS supports this yet. Only Elasticsearch, Couchbase, and managed services like Rockset and CosmosDB.

Re: PartiQL: One query language for all your data

#57
post #36

This 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.

It's not the same at all, and it gets much more verbose with minor complexity and lacks functionality.

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

#58
post #53
post #5

Anyone know how this compares to Presto and zetasql?

I also am trying to figure out how this stacks up against Apache Drill.

It's just a language, not a query engine. You can add PartiQL to Drill and Presto so that they can support a richer querying syntax over the unstructured/schemaless data sources they handle.

Re: PartiQL: One query language for all your data

#59
post #52
post #50

Is 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.

GraphQL is intended for public APIs which are interacted with by arbitrary, possibly malicious, queries.

This appears to be for known queries. Unless it is designed for arbitrary queries, DoS is a likely problem.

Post reply on HN