There is another consideration for scheme checking other than integrity check. Database URL is not statically defined inside the application. It is provided by user configuration and should be checked as any other user input.
On Monday, August 25, 2014 10:20:35 PM UTC+4, Lvc@ wrote: > > Hi, > With 2.0 we introduced more strict relationship between schema and > instances. So in 2.0 when you change type of a property, an integrity check > is issued before the change. > > In 1.7.x each document is validated against its schema, but in 2.0 we made > this validation more efficient. > > Lvc@ > > ᐧ > > > On 25 August 2014 18:48, scala solist <[email protected] <javascript:>> > wrote: > >> I work with orientdb using java document api in scheme-full mode. After >> opening database with docemunt API I want to check if the database confirms >> to a certain class scheme. So all classes needed for the application should >> be defined and should containt certain fields. For now I just fetch all >> classes manually and inspect its properties. It seems to be pretty common >> task for scheme-full applications. Is there any high-level constructions >> that took scheme description in some text format and checks database >> metadata against 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] <javascript:>. >> 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.
