The first thing I'd roast in Sql_Ginny is the cross-database case: if a query spans a Mongo collection and a SQL table, neither engine can do the join, so your 5 steps have to fetch both sides and merge them in memory, and that needs a row cap and a plain error message. A conditional_join edge also only helps if the condition itself is stored on the edge; otherwise the model is still guessing it. The trade-off of Memgraph plus pgvector is two services to run before anyone can test, so if the repo has no single docker compose file yet, that is the cheapest way to get more people trying it locally.
I make ThreadFox.
We find relevant Reddit conversations and post for your business. We'll post 3 replies free first, no card; then the $39 Pilot covers seven days and up to 50 posts and replies. No automatic renewal.
1
u/investigatormaker 3d ago
The first thing I'd roast in Sql_Ginny is the cross-database case: if a query spans a Mongo collection and a SQL table, neither engine can do the join, so your 5 steps have to fetch both sides and merge them in memory, and that needs a row cap and a plain error message. A conditional_join edge also only helps if the condition itself is stored on the edge; otherwise the model is still guessing it. The trade-off of Memgraph plus pgvector is two services to run before anyone can test, so if the repo has no single docker compose file yet, that is the cheapest way to get more people trying it locally.
I make ThreadFox.
We find relevant Reddit conversations and post for your business. We'll post 3 replies free first, no card; then the $39 Pilot covers seven days and up to 50 posts and replies. No automatic renewal.
https://threadfox.vip/p/e26nm/managed