go-driver
go-driver copied to clipboard
arangodb
The official ArangoDB go driver.
This ArangoDB Go driver is still under heavy development, but the concepts behind the API and most of the API functions & types are getting close to what we want...
There is no way to close a connection and it's resulting in memory leak my 8gb RAM is filled within 1.5 minutes ``` Get http://localhost:8529/_db/redbus/_api/database/current: dial tcp 127.0.0.1:8529: connect: cannot...
Environment: * Golang ArangoDB driver ( "github.com/arangodb/go-driver v0.0.0-20200107125107-2a2392e62f69 ") * Go version ("go1.13.6 darwin/amd64") * ArangoDB version ("3.6") . Issue: driver.Database.Query() with bindVars is always empty. Verified same AQL query...
url to DB ist with vst-protocol 1.1 "vst://mydb:8529 ``` goroutine 2247 [IO wait]: internal/poll.runtime_pollWait(0x7f50275d0e08, 0x72, 0xffffffffffffffff) /usr/local/go/src/runtime/netpoll.go:182 +0x56 internal/poll.(*pollDesc).wait(0xc0000fe918, 0x72, 0x1000, 0x1000, 0xffffffffffffffff) /usr/local/go/src/internal/poll/fd_poll_runtime.go:87 +0x9b internal/poll.(*pollDesc).waitRead(...) /usr/local/go/src/internal/poll/fd_poll_runtime.go:92 internal/poll.(*FD).Read(0xc0000fe900, 0xc01d74f000, 0x1000,...
I'm trying to upload a bunch of json data to an arango server. Here is my code ``` go package main import ( "context" "encoding/csv" "encoding/json" "fmt" "io" "io/ioutil" "os"...
The integer 0 is omitempty `Available float64 `json:"available"`` if I set not the value then saved arango the value 0. I must ever set all INT values ala patch though...
Is it supported to do AQL queries on views with the driver? I have a simple collection with a view defined on it with includeAllFields set to true, no other...
driver.SetCollectionPropertiesOptions has an int64 while driver.CreateCollectionOptions has a simple int. I have to explicitly cast it. From a modeling perspective one needs to be chosen over the other.
It would be beneficial and make it more inline with many other go drivers for other databases to use a unique name for the json marshal/unmarshalling. One specific use case...
