https://github.com/orientechnologies/orientdb/issues/2147
On 19 March 2014 05:34, Luca Garulli <[email protected]> wrote: > Hi, > this approach is followed by many users when they need a lightweight way > to create relationships. For such reason we'd like to introduce > mono-directional edges in 2.0, because all the edges now are always > bi-directional. With mono-directional edge, under the hood will be > identical to have a LINK (documentdb api), but at least you remain at > GraphDB API level. > > Lvc@ > > > > On 18 March 2014 23:25, Arve Knudsen <[email protected]> wrote: > >> Odysseas, thanks for chiming in. Your assessment sounds identical to my >> own thinking after working with OrientDB and reading up on its graphs and >> document DBs. Have you yet created ODocuments (not vertices) with >> connections between them? I understand that this should be possible, as a >> lighter alternative to graphs, but I haven't figured out how yet. See also >> my >> SO<http://stackoverflow.com/questions/22492248/orientdb-how-do-i-insert-a-document-with-connections-to-multiple-other-documen>question >> on the matter. >> >> Thanks, >> Arve >> >> >> On Tue, Mar 18, 2014 at 11:14 PM, Odysseas <[email protected]>wrote: >> >>> Arve, >>> >>> For various reasons, including the support for asynchronous queries, we >>> have now moved to a "mixed" data model in our application where we use >>> vertices and edges to create the objects >>> for persistence but use the document-based API on occasion when the >>> blueprints API does not do what we need to do. Under the covers OrientDB is >>> using the document >>> model to store data so even if you use the Blueprints API to construct >>> your data model, you can still use the more low level document API. I just >>> wanted to let you know that that option is available but I am sure the >>> OrientDB guys will correct me if what we are doing is not the best way to >>> go about using OrientDB. >>> >>> Odysseas >>> >>> >>> On Tuesday, March 18, 2014 4:06:34 PM UTC-4, Arve Knudsen wrote: >>> >>>> After studying the subject, I think I want to go with the document >>>> database model for now, and use links between documents (as opposed to >>>> edges between vertices). Are there any examples online of inserting a >>>> document that connects to several other documents (document links, not >>>> edges), and of reading the same documents out of the database (i.e., a >>>> parent document with a set of child documents of another class)? >>>> >>>> Arve >>>> >>>> >>>> On Tue, Mar 18, 2014 at 9:02 PM, Arve Knudsen <[email protected]>wrote: >>>> >>>>> Thanks, Andrey. I think I understand a little more about the >>>>> relationship between Orient's document and graph databases now (I also >>>>> studied Luca's slides). >>>>> >>>>> Best, >>>>> Arve >>>>> >>>>> >>>>> On Tue, Mar 18, 2014 at 2:06 PM, Andrey Lomakin >>>>> <[email protected]>wrote: >>>>> >>>>>> Hi, >>>>>> You can use in SQL queries both graph and document operators. >>>>>> >>>>>> >>>>>> On Tue, Mar 18, 2014 at 2:50 PM, Arve Knudsen <[email protected]>wrote: >>>>>> >>>>>>> Nhat, that is the document database API is it not? I'm wondering if >>>>>>> the graph API supports asynchronous querying. Bear in mind that I >>>>>>> haven't >>>>>>> yet used the graph API so it's all a bit unclear to me still. I think I >>>>>>> might want to use it though since I need to connect database records to >>>>>>> each other. >>>>>>> >>>>>>> Arve >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 18, 2014 at 1:42 PM, Nhat Nguyen < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> I am not sure but couldn´t you use the "OSQLAsynchQuery"? see >>>>>>>> link<https://github.com/orientechnologies/orientdb/wiki/Document-Database#asynchronous-query> >>>>>>>> >>>>>>>> On Tuesday, March 18, 2014 12:54:19 PM UTC+1, Arve Knudsen wrote: >>>>>>>>> >>>>>>>>> Hi >>>>>>>>> >>>>>>>>> Does the OrientDB graph API support asynchronous queries? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Arve >>>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> --- >>>>>>>> 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. >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> --- >>>>>>> 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, >>>>>> Andrey Lomakin. >>>>>> >>>>>> Orient Technologies >>>>>> the Company behind OrientDB >>>>>> >>>>>> -- >>>>>> >>>>>> --- >>>>>> 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. >>>>>> >>>>> >>>>> >>>> -- >>> >>> --- >>> 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. >>> >> >> -- >> >> --- >> 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. >> > > -- --- 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.
