News for hackers. Stuff that matters.
Re:SQLite now allows multiple recursive SELECT statements in... by pbronez on Wednesday October 21, 2020 @08:34AM (#24847140)
I’d love to learn more about your use case... I think SPARQL and RDF are pretty interesting technologies, but haven’t seen many real applications using them.
Re:SQLite now allows multiple recursive SELECT statements in... by zozbot234 on Wednesday October 21, 2020 @08:47AM (#24847274)
I'd describe SPARQL and RDF as general interfaces focused on interop, not "technologies" per se. You could use any technology to provide a SPARQL/RDF endpoint, including a relational database.
Re:SQLite now allows multiple recursive SELECT statements in... by zimpenfish on Wednesday October 21, 2020 @10:21AM (#24848130)
My current use case is that I'm working on something which is basically things in groups (which may also be in groups) and seeing if things like "items in group A which are linked to group C via linkages to items in group B" are easier with SPARQL + graph database than they are with Postgres.

(Previous use case was converting music industry data into RDF and providing query interfaces on top. That 1.1GB TTL is a CWR file converted to RDF as a stress tester.)

Re:SQLite now allows multiple recursive SELECT statements in... by zozbot234 on Wednesday October 21, 2020 @12:45PM (#24849547)
> "items in group A which are linked to group C via linkages to items in group B"

Relational databases are actually quite convenient for such cases because you can model each "group" of items via a database table, including potentially an associative table which provides "linkage" between items in the database. Graph-based models are generally more limited than that, e.g. RDF and SPARQL are limited to simple triples which link a "source" and a "target" entity (both of which are essentially non-typed) according to a fixed "predicate". You can sort of materialize triples and endow them with extra information, but it gets clunky.

Re:SQLite now allows multiple recursive SELECT statements in... by zimpenfish on Wednesday October 21, 2020 @07:28PM (#24853425)
> Relational databases are actually quite convenient for such cases

I believe that someone may have done this in a nice way but every time I've encountered it (3 times thus far), it's always ended with complex SQL and tables being bent out of shape to try and keep performance.

> RDF and SPARQL are limited to simple triples which link a "source" and a "target" entity according to a fixed "predicate"

But can also infer transitive relations based on those predicates - `A canSee B`, `B canSee C` => `A canSee C` - which is handy when you're trying to discover those relationships in your data.

Re:SQLite now allows multiple recursive SELECT statements in... by zozbot234 on Wednesday October 21, 2020 @07:30PM (#24853444)
> But can also infer transitive relations based on those predicates - `A canSee B`, `B canSee C` => `A canSee C` - which is handy when you're trying to discover those relationships in your data.

You can do this sort of inference in a view if you use relational databases. (A view is a sort of "virtual" table based on the result of some database query. Many databases can also materialize views for improved performance, though this can make it a bit challenging to manage updates.)

Re:SQLite now allows multiple recursive SELECT statements in... by zimpenfish on Thursday October 22, 2020 @03:58AM (#24855830)
> You can do this sort of inference in a view if you use relational databases.

You'd need to use recursive queries though, I think, and there be dragons.

> [materialized views] can make it a bit challenging to manage updates

We're not using them with Postgres because refreshing materialized views is very much a blunt hammer and it'd cause more hassle than it would solve. Which is annoying because they've been great when I've used them previously.