The reason it's suggested is because it can do everything the Document API can do plus adds all the capabilities and benefits of using a graph.
However, it's completely possible to use the Graph API to store document-type records and never once create a connection (edge). Having said that, you can also use the Document API with links to other records, you just have to maintain the connections yourself. Something to note, the Graph API automatically uses a transaction and will save your properties when they are set. The Document API requires you to begin a transaction, and you have to call save() explicitly after you modify fields. Hope that helps. -Colin Orient Technologies The Company behind OrientDB On Thursday, April 23, 2015 at 8:14:49 AM UTC-5, Newbee to OrientDB wrote: > > Hey guys, in the orient-db documentation ( > http://orientdb.com/docs/last/Tutorial-Java.html) The Graph API is marked > as suggested. Is there a reason for that ? Does this mean that it's always > better to always use a Graph database ? Is a Graph database in OrientDB > exactly the same as a Document database plus graph features ? > -- --- 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.
