So long as it stays in its own branch, it shouldn't have any conflicts with
AGE's source code. As it stands now, the PR was merged into the branch
PROPOSAL_PG_Graph, by me.
Again, this needs to go through the proper procedures. Otherwise, I'm fine
with the addition.
john
On Fri, May 24, 2024 at
Hi Everyone,
To add one top of what has already been mentioned,
AGE as an independent graph DBMS sounds interesting. It seems the file and
folder structure of such a project will be very different from the AGE as
an extension. In my opinion, there may be some challenges to maintain them
in the
If I am understanding this correctly, this is a PR for a new project along side
of the Apache AGE extension. It does not modify nor extend the actual extension
itself, which is Apache AGE. It merely adds an alternative, rooted in
PostgreSQL version 13, to the extension.
I am not opposed to
Dear Everyone,
I hope you are doing great.
We would like to have a conversation about a recent Pull Request [1] that we
received for Apache AGE. This Pull Request seems to introduce new extension
features for AGE within the DBMS core engine. Currently, it utilizes
PostgreSQL13 and aims to
