JoshInnis commented on issue #290: URL: https://github.com/apache/age/issues/290#issuecomment-1248721195
As you mentioned, there are three unique data types are used to represent entities in a graph, and there is a second aspect for how it is stored in Postgres. The second part of that presentation. For the datatypes, the openCypher specification works in such a way that the existing datatypes in Postgres could not suit our needs. So we created Agtype, which is based on JSONB (one of postgres's two implementations of the Json standard). ` The issue if I’m understanding correctly is, GraphQL will interpret the cypress command like postgreSQL, as normal function calls unless we intercept it to run the Cypress command which will provide AGE’s tables(labels) and data(vertices/edges/paths). Is that correct?` GraphQL is a query language, like cypher. We have already implemented cypher and GraphQL should not handle a cypher command. Personally, I see two ways to do this: 1. Create a function like cypher and create a second query language in AGE. The reason this works the way it does is the third section in the webinar. 2. Create an API that accepts GraphQL commands and converts them to Cypher Commands, and is an intermediate between a client and the server. There may be several other ways to do it as well. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
