> > Are you using an OrientDB graph database or an OrientDB document database? > > I am doing both. I wanted to have 2 overlapping model. First data linked (so not embedded) with each other like in a regular relational database, and second graph linking objects together.
To give you an implementation idea, one of the use if for a board game. The "relational" model is to store component data and make links between data if any. The graph part is to record the geographical position of the components (tree structure). But so far, I tried the document and object API and I am rapidly facing issues hard to resolve. I might stick to an old relational database with JDBC, it seems to works much more easily and I am more familiar with relational databases. Thanks again. On Monday, March 2, 2015 at 10:46:00 AM UTC-5, Colin wrote: > > Greetings. > > Are the records you're creating documents or vertices? > > Are you using an OrientDB graph database or an OrientDB document database? > > If you use documents, you must manage the links manually. If you use the > graph database and vertices and edges, then the links will be managed by > the database. > > Regards, > > -Colin > > Colin Leister > > Orient Technologies > > The Company behind OrientDB > > > On Sunday, March 1, 2015 at 8:45:55 PM UTC-6, [email protected] wrote: >> >> While reading the documentation, I learned that there are a way to make >> some sort of light weight edges when no edge variables are required. For a >> one to many relation, it is done by placing a record list on one side and a >> record reference on the other side. For example, let say you have 2 tables >> where 1 hold record A and B while the second table hold record 1-5. >> >> In a relational database you would proceed this way >> >> table 1 >> A >> B >> >> Table 2 >> 1A >> 2A >> 3A >> 4B >> 5B >> >> In other words you add the ID of the linked record. But in orient DB you >> would proceed this way >> >> Table 1 >> A {1,2,3} >> B{4,5} >> >> Table 2 >> 1A >> 2A >> 3A >> 4B >> 5B >> >> This make sure that in either direction, you have direct access to the >> linked record. >> >> Now from the documentation, they explained how to create the fields, but >> I have no idea how to establish the relation between those fields. Of >> course I could manage it manually but that is rather complex because links >> must be recorded in both tables. Each time a new entry is added in table 2, >> the record list in table 1 needs to be updated. I would have expected that >> orient DB would manage such modifications. >> >> Else how do you query using those relations. Can you use the EXPAND >> command like for edges, are you restricted to use TRAVERSE, again did not >> found any information about it. >> >> >> >> -- --- 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.
