Hi Matus, current behavior is exactly what you described, records that have to be excluded are just skipped during evaluation. It's not a bad idea to optimize the select statement to act in a more efficient way, I suggest you to open an issue about this, so that it can be addressed in next releases. In the roadmap there is a big effort about query execution and optimization, this could be an important part of it
Thanks Luigi 2015-05-27 12:50 GMT+02:00 Matus Zeman <[email protected]>: > Anyone please? > > > On Tuesday, 19 May 2015 15:10:47 UTC+2, Matus Zeman wrote: >> >> Hi there, >> I'm planning to build social network. I'm considering to use ORestricted >> to control access. >> There is a hook which implements this functionality >> com.orientechnologies.orient.core.metadata.security.ORestrictedAccessHook. >> ORestrictedAccessHook.onRecordBeforeRead SKIP the record if current user >> doesn't have access to this record. >> >> I'm not really sure about how "select" is implemented internally but it >> seems like that it works as following: >> Imagine I have 1000 documents and only 1 record is accessible by current >> user. >> DB engine would need to select/parse all 1000 documents and "don't skip" >> only 1 out of 1000 without using any index. >> >> Am I thinking about how it's implemented correctly? Could somebody >> elaborate on performance implication please? >> >> Thanks, >> Matus >> >> -- > > --- > 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.
