Hi Jean Sebastien, JDBC driver supports only a subset of OrientDB, only the part you can use with commands.
If you're a Java developer, I suggest you to use the Java Graph API: http://orientdb.com/docs/last/Graph-Database-Tinkerpop.html Lvc@ On 13 April 2015 at 10:33, Jean-Sebastien Lemay < [email protected]> wrote: > I'm quite liking the SQL syntax made available to developers for OrientDB, > which I have shortly studied in the excellent Udemy course made available > by Orient. However, my software is written in Java, which means that the > native API is the suggested method for working with OrientDB. > > I was curious if there were any disadvantages to using the JDBC driver and > issuing SQL statements instead of using the native API, since I am > comfortable with the SQL syntax and I suspect the other developers in my > team will be as well. Is there anything the native API can do that the JDBC > driver/SQL syntax can't? What about performance? Would you consider them > equivalent overall? > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Best Regards, Luca Garulli CEO at Orient Technologies LTD the Company behind OrientDB http://about.me/luca.garulli -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
