HI Giulia I have 25 tables and more than 20+ edges..all tables are interrelated in some way...it will be reallly tough to import all in one go. The json will be really complex. Are you sure there is no way to split import for large schema like ours? Also, one more issue...the lookup field is not scanning the whole table...it stays at current record..if the match is at the same or previous record it returns null...how do I make full table scan...do I have to use an index mandatorily for lookup field? Currently I am using a property.
On Mon, Aug 17, 2015 at 5:29 PM, Giulia Brignoli <[email protected]> wrote: > Hi Sam, > > I don't think you can import only the edge without creating any class. The > only thing I can think of that you can do is create both the vertex and the > edges all the same JSON. > > Regards, > Giulia > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "OrientDB" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/orient-database/i_w3sVje64U/unsubscribe. > To unsubscribe from this group and all its topics, 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.
