kirill-develops commented on issue #290: URL: https://github.com/apache/age/issues/290#issuecomment-1248404064
I took a look at the slides again that I saw you uploaded to the intro to AGE project. I’d love a 15min zoom call at any time just to clarify my understanding. The big take away was there are three unique types to AGE: vertices, edges and paths, with the first two being JSON data types and the later being an array/list of alternates of the former two. They are stored in AGE labels. DB complexity is something I am still tackling, so the purpose of these data types is over my head atm (something that zoom call mentioned above might clarify 😉). Nonetheless, we are looking to integrate GraphQL on querying and modifying these data types, that I believe are only accessed through the cypress command. And GraphQL needs an initial schema to understand the relationships of data and how to find the eventual user’s query. The issue if I’m understanding correctly, GraphQL will interpret the cypress command as normal function calls as does PostgreSQL unless we intercept it to run the Cypress command which will provide AGE’s tables(labels) and data(vertices/edges/paths). Am I close to comprehending the problem? Still digesting what the VLE is for aswell (did I mention I’m new?) -- 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]
