I was just reading the Postgresql 11 roadmap and it mentions native graph
support. I would be interested in following the design work for this.
Would this require a the new pluggable storage which is currently in
development or would the existing storage engine be sufficient? I am just
wondering i
From: Henry M
> This may be interesting... they implement cypher (unfortunately they
had to fork in order to have cypher be a first class query language
with SQL).
>
> https://github.com/bitnine-oss/agensgraph
I'm sorry for my very late reply.
Thanks for the information. AgensGraph is certainly
This may be interesting... they implement cypher (unfortunately they had to
fork in order to have cypher be a first class query language with SQL).
https://github.com/bitnine-oss/agensgraph
On Mon, Aug 21, 2017 at 12:44 AM Chris Travers
wrote:
> On Sun, Aug 20, 2017 at 4:10 AM, MauMau wrote:
On Sun, Aug 20, 2017 at 4:10 AM, MauMau wrote:
> From: Chris Travers
> > Why cannot you do all this in a language handler and treat as a user
> defined function?
> > ...
> > If you have a language handler for cypher, why do you need in_region
> or cast_region? Why not just have a graph_search()
On 20 August 2017 at 10:10, MauMau wrote:
> From: Chris Travers
> > Why cannot you do all this in a language handler and treat as a user
> defined function?
> > ...
> > If you have a language handler for cypher, why do you need in_region
> or cast_region? Why not just have a graph_search() funct
From: Chris Travers
> Why cannot you do all this in a language handler and treat as a user
defined function?
> ...
> If you have a language handler for cypher, why do you need in_region
or cast_region? Why not just have a graph_search() function which
takes in a cypher query and returns a set of r
"MauMau" writes:
> I'm thinking of making PostgreSQL a multi-model database by supporting
> data models other than the current relational model. A data model
> consists of a query language (e.g. SQL for relational model, Cypher
> for graph model), a parser and analyzer to transform a query into a
On Sat, Aug 19, 2017 at 4:29 PM, MauMau wrote:
> Hello,
>
> Please forgive me for asking such a stupid and rough question.
>
> I'm thinking of making PostgreSQL a multi-model database by supporting
> data models other than the current relational model. A data model
> consists of a query language
Hello,
Please forgive me for asking such a stupid and rough question.
I'm thinking of making PostgreSQL a multi-model database by supporting
data models other than the current relational model. A data model
consists of a query language (e.g. SQL for relational model, Cypher
for graph model), a p