Hi Richard, Your such class is called as a Component class in Hibernate, a ComplexType class in Entity Framework. In OrientDB, they are just casual classes, and you could use EMBEDDED relationship to them, and there is no limit of nested levels like other frameworks.
Hope it helps! My Best, Hung Tran On Tuesday, March 1, 2016 at 5:21:29 PM UTC+7, [email protected] wrote: > > Hi, > The description above is a sample of the data I want to save. > Calculator, expenses, limits, rates, etc are what I'm considering as the > properties of the object. > Type and Currency are just orientdb classes with { name, description } > > As part of what I'm doing, I'm to save a product which have the structure > above. There are a number of nested properties some being arrays of objects > containing arrays, etc. > > I'm asking for the best way to structure the data so that queries and > inserts are performant. > > > regards, > Richard. > > > On Monday, February 29, 2016 at 5:02:14 PM UTC, [email protected] wrote: > >> Hi, >> >> I didn't understand very well your structure, >> What are calculator, expenses, limits and parameter rates? >> What do you mean with type and currency? >> and what do you wanna do exactly? >> >> Thx >> >> Regards, >> Michela >> > -- --- 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.
