Tolga Ulas
Tolga Ulas
Hey, sorry for late response. No I did not. But your previous inquiry made us rethink it; as arcadedb now supports many protocol i.e postgresql etc we are now playing...
Yes, asked my colleague who will share the details here as much as possible without revealing too much data :)
Will do if things is harder to sanitize for public, otherwise we like to keep public for future generations. :)
Ok i think the problem is not import, but our habits from oriendtb sql language. In orientdb, we had `v1`, `v2` vertices and `v1v2` edge from `v1` to `v2`. So,...
And on the grafana part, definetly their postgres adapter is not compatible with current arcadeb; we're not getting results we're getting with postgres clients out of arcadedb. Also we could...
This is `select from v1v2` : ``` { "result": { "vertices": [ { "p": { "foo": "bar" }, "r": "#25:0", "t": "v2", "i": 1, "o": 0 }, { "p": {...
In orientdb, we used to have a lot data (hence functionality) on edges; like the ongoing activities in between the vertices. Should I understand that with arcadedb we should use...
> What version? v.3.1.11, also updated the issue @vcastellm
latest, just installed on the ticket date. On Thu, May 12, 2022 at 11:17 PM Victor Castell ***@***.***> wrote: > What version? > > — > Reply to this email...
Still down.