Please elaborate on the reasons behind DisableGraphDML

[brncsk]

We'd like to integrate PostGIS w/ AgensGraph, making use of PostGIS's spatial indexing.

Our use case is the following: whenever a graph vertex is inserted/updated, a trigger would extract a GeoJSON geometry from one of the vertex's properties, converting it into PostGIS's native Geometry type, and storing it in a separate column.

This fails for a number of reasons, most of which are rooted in the changes introduced by https://github.com/bitnine-oss/agensgraph/commit/1d0ea75f28de6c60cf8779168bb7eec02ffe457b. This disables a vast amount of functionality that is vital for our use case, namely:

1. Creating TRIGGERs or RULEs on a graph label.
2. Modifying graph objects with DML queries.

While I do vaguely understand the reasons behind this change (having read https://bitnine.net/blog-agens-solution/data-model-of-agensgraph/), I'd like to ask if you could elaborate on the specific reasons behind it:

• What are the exact problems this change was meant to prevent the user from creating?
• Would it be possible to either reintroduce some of this functionality, or document the technical reasons behind this decision more thoroughly, so that we could evaluate whether to fork AgensGraph?

[aberenyi]

We're facing the same issue.

A possible solution could be to create a getter/setter for DisableGraphDML.

[ns-stang]

We're facing the same issue.

A possible solution could be to create a getter/setter for DisableGraphDML.

I am also facing the same issue. Could you tell me more about the possible solution?