Fabien Herfray
Fabien Herfray
I just found the solution actually. The go modules tool is not able to resolve C dependencies so it doesn't see that some `.c`/`.h` files are actually in the `internal`...
Hahaha perfect #RaceCondition
To be honest, I also don't really understand why the ArangoDB team never implemented some kind of delete cascade. The [remove vertex operation](https://docs.arangodb.com/GeneralGraphs/Management.html#remove-a-vertex) from the graph management interface is Javascript...
Actually, the best solution I found for now is using the AQL traversals like that: ``` go t := arangolite.NewTransaction( nil, []string{"users","dashboards","dashboardRights","devices","deviceRights"}, ).AddQuery("users", ` FOR u IN users REMOVE u...
Yeah I know and I totally agree with you. There should be some simple way to cascade when there's a deletion...
When you say `creating a new database`, you mean creating a new database object right? You can easily switch any parameter at any moment using the `Options` method, as shown...
Oh ok for read operations good point. I'm just trying to keep the tiniest API surface possible to be able to refactor easily in case of missing features (and there...
I'd be interested in merging https://github.com/garmeeh/next-seo/pull/1062 too 🙏
Me too, thanks for the work ! I'll implement it and create issues if I found any bugs :+1:
The thread safe fix with Faraday works perfectly ! No more segmentation fault. Thx a lot !