[GitHub] [incubator-age] bravius opened a new issue #176: nodejs-pg-age driver returns 'undefined' for primitive column types (v0.7.0)

[GitBox]

bravius opened a new issue #176:
URL: https://github.com/apache/incubator-age/issues/176


   According to the documentation on Apache AGE types 
(https://age.apache.org/docs/master/intro/types.html):
   
   > AGE uses a custom data type called agtype, which is the only data type 
returned by AGE
   
   I'm using the nodejs driver as per the instructions on the README page 
(https://github.com/apache/incubator-age/tree/master/drivers/nodejs/README.md):
   
   The driver works fine as long as the query returns an agtype that contains 
an object or an array, but for all other types the driver returns _undefined_.
   
   For example, for the query:
   
   `SELECT * FROM cypher('dev', $$ RETURN 555 as value $$) as (value 
agtype)`
   
   the nodejs-pg-age driver returns this (note the return value is undefined).
   
   ```
   Result {
 command: 'SELECT',
 rowCount: 1,
 oid: null,
 rows: [ { value: undefined } ],
 fields: [
   Field {
 name: 'value',
 tableID: 0,
 columnID: 0,
 dataTypeID: 16448,
 dataTypeSize: -1,
 dataTypeModifier: -1,
 format: 'text'
   }
 ],
 ...
   ``` 
   
   It seems the driver's type parser only recognizes objects and arrays. 
   
   If I define the column type as integer it returns the expected value:
   
   `SELECT * FROM cypher('dev', $$ RETURN 555 as value $$) as (value 
integer)`
   
   ```
   Result {
 command: 'SELECT',
 rowCount: 1,
 oid: null,
 rows: [ { value: 555 } ],
 fields: [
   Field {
 name: 'value',
 tableID: 0,
 columnID: 0,
 dataTypeID: 16448,
 dataTypeSize: -1,
 dataTypeModifier: -1,
 format: 'text'
   }
 ],
 ...
   ``` 
   
   My question is, shouldn't the nodejs driver (node-pg-age) be parsing all 
valid agtype values -- including numbers, strings and booleans -- not just 
objects and arrays?
   
   
   
   
   
   
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [incubator-age] emotionbug commented on issue #176: nodejs-pg-age driver returns 'undefined' for primitive column types (v0.7.0)

[GitBox]

emotionbug commented on issue #176:
URL: https://github.com/apache/incubator-age/issues/176#issuecomment-1018161534


   It will fix it.
   
   https://github.com/apache/incubator-age/pull/177


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [incubator-age] bravius closed issue #176: nodejs-pg-age driver returns 'undefined' for primitive column types (v0.7.0)

[GitBox]

bravius closed issue #176:
URL: https://github.com/apache/incubator-age/issues/176


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [incubator-age] bravius commented on issue #176: nodejs-pg-age driver returns 'undefined' for primitive column types (v0.7.0)

[GitBox]

bravius commented on issue #176:
URL: https://github.com/apache/incubator-age/issues/176#issuecomment-1018174047


   @emotionbug - Thanks very much for the speedy fix, works as expected now. 
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [incubator-age] aked21 commented on issue #176: nodejs-pg-age driver returns 'undefined' for primitive column types (v0.7.0)

[GitBox]

aked21 commented on issue #176:
URL: https://github.com/apache/incubator-age/issues/176#issuecomment-1018175927


   Thanks @emotionbug 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

After openCypher

[Young Seung Andrew Ko]

Thank you, AGE team!

It seems the project is nearing to the completion of implementing an engine
to process openCypher-based graph queries to an extent that it can allow
many important graph operations on PostgreSQL.

Any suggestions or recommendations on what should follow after this
meaningful milestone?
- Support for PostgreSQL 12, 13 and 14
- Making AGE + PostgreSQL distributed
- Some tools to make AGE easier to use
- ...

Andrew Ko

Re: After openCypher

[Jasper Blues]

I’m not sure if it is part of the official openCYPHER spec, however I would 
like to see support for: 

https://neo4j.com/blog/cypher-graphql-neo4j-3-1-preview/ 


Also is it possible to use AgensGraph drivers with AGE? 

The reason for asking is I would like to support GraphQL in DRIVINE.ORG 
 such that: 

Default queries and mutations can be auto-generated 

^— This will mean that using AGE with DRIVINE can serve GraphQL APIs on par 
with the leading graph DB, and AGE can be promoted as part of the GraphQL buzz. 

> On Jan 21, 2022, at 2:50 PM, Young Seung Andrew Ko 
>  wrote:
> 
> Thank you, AGE team!
> 
> It seems the project is nearing to the completion of implementing an engine
> to process openCypher-based graph queries to an extent that it can allow
> many important graph operations on PostgreSQL.
> 
> Any suggestions or recommendations on what should follow after this
> meaningful milestone?
> - Support for PostgreSQL 12, 13 and 14
> - Making AGE + PostgreSQL distributed
> - Some tools to make AGE easier to use
> - ...
> 
> Andrew Ko

Re: After openCypher

[Joe Fagan]

Congratulations on the great work todate.


Would be nice to add


Graph Algorithms eg

Traversal and Pathfinding (ShortestPath, ShortestWeightedPath, Minimum
Weight SPanning Tree)

Centrality (PageRank)

Community Algoriths (Cluster detection, Louvain modularity

Agreement on the many graph formats to export and import from. GraphML,
Graphviz Dot etc


On Fri, 21 Jan 2022 at 06:50, Young Seung Andrew Ko <
youngseung.and...@gmail.com> wrote:

> Thank you, AGE team!
>
> It seems the project is nearing to the completion of implementing an engine
> to process openCypher-based graph queries to an extent that it can allow
> many important graph operations on PostgreSQL.
>
> Any suggestions or recommendations on what should follow after this
> meaningful milestone?
> - Support for PostgreSQL 12, 13 and 14
> - Making AGE + PostgreSQL distributed
> - Some tools to make AGE easier to use
> - ...
>
> Andrew Ko
>

Re: After openCypher

[Jasper Blues]

+1 Graph Algorithms!

> On Jan 21, 2022, at 3:05 PM, Joe Fagan  wrote:
> 
> Congratulations on the great work todate.
> 
> 
> Would be nice to add
> 
> 
> Graph Algorithms eg
> 
> Traversal and Pathfinding (ShortestPath, ShortestWeightedPath, Minimum
> Weight SPanning Tree)
> 
> Centrality (PageRank)
> 
> Community Algoriths (Cluster detection, Louvain modularity
> 
> Agreement on the many graph formats to export and import from. GraphML,
> Graphviz Dot etc
> 
> 
> On Fri, 21 Jan 2022 at 06:50, Young Seung Andrew Ko <
> youngseung.and...@gmail.com> wrote:
> 
>> Thank you, AGE team!
>> 
>> It seems the project is nearing to the completion of implementing an engine
>> to process openCypher-based graph queries to an extent that it can allow
>> many important graph operations on PostgreSQL.
>> 
>> Any suggestions or recommendations on what should follow after this
>> meaningful milestone?
>> - Support for PostgreSQL 12, 13 and 14
>> - Making AGE + PostgreSQL distributed
>> - Some tools to make AGE easier to use
>> - ...
>> 
>> Andrew Ko
>>