[HN Gopher] Apache Age: A Graph Extension for PostgreSQL
       ___________________________________________________________________
        
       Apache Age: A Graph Extension for PostgreSQL
        
       Author : based2
       Score  : 84 points
       Date   : 2021-03-04 18:02 UTC (4 hours ago)
        
 (HTM) web link (age.apache.org)
 (TXT) w3m dump (age.apache.org)
        
       | ForHackernews wrote:
       | FWIW, Postgres already has good support for representing and
       | querying graph structures using the LTree extension
       | https://www.postgresql.org/docs/current/ltree.html
        
       | yamrzou wrote:
       | This is based on AgensGraph: http://bitnine.net/downloads-2020/
       | 
       | I found this presentation from 2017 about AgensGraph:
       | https://www.slideshare.net/mobile/kisung80/agensgraph-a-mult...
        
       | jacques_chester wrote:
       | How would this compare with something like pgRouting
       | (https://pgrouting.org/)?
        
       | jeiklo wrote:
       | Though i appreciate all the hard work people put into this and
       | offer it so generously for free, it kind saddens me to see yet
       | another property graph database that supports some non-
       | standardized (not really anyway) query language. I would really
       | like to see a free, solid and rdf based triple-store with good
       | SPARQL support. But all the activity seems to be in the property-
       | graph camp, with a new product every couple of month.
        
       | znpy wrote:
       | old: https://news.ycombinator.com/item?id=26309560
        
       | philsnow wrote:
       | the projects are not related at all but this and
       | https://github.com/FiloSottile/age have a name conflict.
        
       | fatsdomino001 wrote:
       | I wonder how the inclusion of graph features in Postgres 14 will
       | affect this project.
        
         | jhoechtl wrote:
         | From where do you get that? I was searching the internets for
         | this purported feature and couldn't find it. Link?
        
           | cldellow wrote:
           | Version 14 adds some features to recursive CTE expressions to
           | do BFS/DFS searches and cycle detection. As always, depesz
           | has a nice write up of it:
           | https://www.depesz.com/2021/02/04/waiting-for-
           | postgresql-14-...
           | 
           | I _think_ it's just syntactic sugar and doesn't let you do
           | anything you couldn't already do, although perhaps it would
           | leave room in the future for the Postgres team to optimize
           | query execution.
        
       | ajankelo wrote:
       | Fantastic that they are using Cypher. Love that language, if one
       | could say that about a Query language.
        
         | hc-taway wrote:
         | Cypher's pretty much the only thing about Neo4j that I found to
         | be both pleasant-to-use and... well, any good, really. Love
         | seeing it borrowed by other graphDBs. I'm far from being a SQL
         | hater, but being able to bounce into Cypher to replace (at
         | least some large subset of) recursive CTEs would be a huge
         | developer-experience improvement for PostgreSQL, for multi-
         | model DBs.
         | 
         | Example from the n4j Cypher docs, for the curious:
         | MATCH (user:User { name: 'Adam'
         | })-[r1:FRIEND]-()-[r2:FRIEND]-(friend_of_a_friend)
         | RETURN friend_of_a_friend.name AS fofName
         | 
         | Returns names of friends-of-friends (connected with FRIEND-
         | labeled edges) User nodes having the "name" property "Adam".
         | Stuff like "friend_of_a_friend" is set as an alias for the
         | matched nodes, like in SQL. () denotes a node, [] an edge.
         | (It's been a while, so this explanation may be subtly wrong,
         | but it's close)
        
       ___________________________________________________________________
       (page generated 2021-03-04 23:00 UTC)