Hello, thanks for the answers, so I take it like "yes it s better to have a schema" :)
D. On Thu, Jan 8, 2015 at 9:32 AM, Luigi Dell'Aquila < [email protected]> wrote: > Hi, > > with current version (as Keith said) schema-defined fields are more > compact in terms of disk space. In next releases you will also have > additional advantages in terms of query speed. > But the most significant difference is that defining properties you can > - enforce constraints on fields (min, max, not null...) > - define indexes on properties to speed up property based search > > Luigi > > > > 2015-01-08 16:22 GMT+01:00 Keith Freeman <[email protected]>: > >> On advantage (recently added to orient, not sure which version) is that >> schema-defined fields don't have to be stored with every record, saving >> storage space. >> >> >> On Wednesday, January 7, 2015 5:23:17 PM UTC-7, Dlp Net wrote: >>> >>> Hello, >>> >>> >>> Is there any advantage to define a schema for a class ? I saw that it s >>> optional but is having a schema has any advantage (like speed/indexing) ? >>> >>> Thanks >>> D. >>> >> -- >> >> --- >> 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.
