Hi Itai,
To prevent data corruption in future pelase udate to 2.2.17 version.
This version contains a fix for two issues which may cause given behavior,
so I do suggest you to update to latest version.
About fix of currently broken record. There are two approaches:
1. Make export/import of
Thanks Luigi.
Worked like a charm!
On Tuesday, February 21, 2017 at 12:10:52 AM UTC-8, Luigi Dell'Aquila wrote:
>
> Hi,
>
> You can create a List and store it as a property value, eg.
>
> OrientVertex v = ...
> List values = new ArrayList();
> for(...){
> ODocument item = new ODocument("Bid");
William,
first of all, I don't know much about any of the options you request.
Regarding Studio, I find it useful when looking for confirmation of a
structure
after uploading data even in a large scale.
However, visualizing graphs of 2000+ nodes/edges makes little sense in
Studio.
Don't know
Thanks.
Unfortunately, some of the results from a match search that I might want to
visualize are larger than what the UI in Studio can handle... I'm also
interested in layout algorithms other than the force-directed layout that
Studio supports.
The Java API from OrientDB wouldn't happen to have
Hi Roberto,
Please refer to the following application classes for a Spring Boot
application with OrientDB JDBC Driver. This project is saving Samples, but
if one of the Samples failed to be saved, it would not roll back and dirty
data would be existing. Could you please advise if there is a
William,
old news I'm afraid. Given up, but since Studio has improved tremendously
over the last year I find it useful.
Please consider using match {} return $elements. This way you may downsize
your graph to make more sense.
Hope you have enough RAM to bump up -Xmx...
Good luck!
Tore
On
