Hi Kae, Usual approach is to represent concepts with vertexes and relationships with edges. Some additional information, like date, you can store in properties.
I'm not sure that understand what do you want to represent, so can't advice anything. Best regards, Artem Orobets *Orient Technologies the Company behind OrientDB* 2014-05-28 11:16 GMT+03:00 kae <[email protected]>: > Hello, > > i want to make a financal social system. > > Konto type v > Buchung type e > Budeget type e > > Now i should have time level like year (2014,2015, and so on) > > which type level should the time have. e or v. > > konto out Buchung > konto in Buchung > > konto out Budget > konto in Budget > > or year is type e > > Konto out Buchung > Konto in Buchung > Konto out year > Konto in year > > or have you an other solution. > > -- > > --- > 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.
