11–20 of 47 posts
Back in the early days PostgreSQL was a NoSQL database called Postgres, using a query language called POSTQUEL.
Then SQL was added, becoming PostgreSQL.
With Agens Graph adding an optional non-SQL query language back to it, it seems like it's gone a full circle. Hopefully on an upward slope though. :)
If anyone's interested in the pre-SQL Postgres, there's some info here: https://www.postgresql.org/about/history/
Wondering if anyone has experience with it... there's a lot of competition in graph database market, curious to see if this is worth investing time in.
There isn't a lot of competition in the "free/libre database" market though. The only serious players are Jena/Fuseki (an RDF store) and Janus (a graph store).
Wondering if anyone has experience with it... there's a lot of competition in graph database market, curious to see if this is worth investing time in.
There isn't a lot of competition in the "free/libre database" market though. The only serious players are Jena/Fuseki (an RDF store) and Janus (a graph store).
Heh Heh Heh Back in the early days PostgreSQL was a NoSQL database called Postgres, using a query language called POSTQUEL. Then SQL was added, becoming PostgreSQL. With Agens Graph adding an optional non-SQL query language back to it, it seems like it's gone a full circle. Hopefully on an upward slope though. :) If anyone's interested in the pre-SQL Postgres, there's some info here: https://www.postgresql.org/about/…
https://en.wikipedia.org/wiki/QUEL_query_languages
QUEL is a better language (more consistent), and SQL won not on technical grounds, but because Larry Ellison is a better salesman than Michael Stonebraker.
Heh Heh Heh Back in the early days PostgreSQL was a NoSQL database called Postgres, using a query language called POSTQUEL. Then SQL was added, becoming PostgreSQL. With Agens Graph adding an optional non-SQL query language back to it, it seems like it's gone a full circle. Hopefully on an upward slope though. :) If anyone's interested in the pre-SQL Postgres, there's some info here: https://www.postgresql.org/about/…
NoSQL refers to non-relational DBMSes, not a literal lack of SQL... QUEL is, if anything, closer to relational algebra than SQL is. https://en.wikipedia.org/wiki/QUEL_query_languages QUEL is a better language (more consistent), and SQL won not on technical grounds, but because Larry Ellison is a better salesman than Michael Stonebraker.
I'd be interested in seeing performance comparisons as it seems Agens is implemented in C.
Earlier quoted context omitted.
NoSQL refers to non-relational DBMSes, not a literal lack of SQL... QUEL is, if anything, closer to relational algebra than SQL is. https://en.wikipedia.org/wiki/QUEL_query_languages QUEL is a better language (more consistent), and SQL won not on technical grounds, but because Larry Ellison is a better salesman than Michael Stonebraker.
Yeah, I wondered if anyone was going to be pedantic about that. ;)
Earlier quoted context omitted.
There isn't a lot of competition in the "free/libre database" market though. The only serious players are Jena/Fuseki (an RDF store) and Janus (a graph store).
There is also Cayley ( https://github.com/cayleygraph/cayley ) which supports more query languages, including GraphQL, and multiple backend stores.
This is awesome. So many of the problems in legacy projects that I've had to deal with have been from trying to shoehorn a graph business process into a tree database.
A "graph business process" is borderline content free. All business processes can be expressed by graphs. What is a graph? A dynamic data structure. That is it. So what is a "tree database"? A graph database with a bias for a specific ordering of its nodes. Does that make a tree database a query result (path traversal) in a graph database? The confusion of it all. So imho one uses a "graph database" when (a) the doma…