I have always been interested in Rust. Having the backend written in a programming language with a reliable thread safety could allow for some powerful ETL functionality.
Interesting idea. I think it make adoption of AGE a lot easier if it can work on a database without needing a data migration.
AGE uses Agtype l, which is a superset of JsonB for its uses, the primary addition is the edge and vertex type.
AGE can handle that and recursive ctes can as well, but AGE has mechanisms to handle cyclic graphs as well.
I have always been interested in Rust. Having the backend written in a programming language with a reliable thread safety could allow for some powerful ETL functionality.
Interesting idea. I think it make adoption of AGE a lot easier if it can work on a database without needing a data migration.
AGE uses Agtype l, which is a superset of JsonB for its uses, the primary addition is the edge and vertex type.
AGE can handle that and recursive ctes can as well, but AGE has mechanisms to handle cyclic graphs as well.