If no one has a good answer to that, maybe someone would have an idea of what would be better from a performance perspective, custom types or a set of hooks?
The scenario is that we only need certain fields on some classes to be encrypted. We have a pretty basic hook that can do that, but anytime we add a new property that we want encrypted, we'd have to add more to the hook to encrypt/decrypt the field on read/insert/update. Is that better from a performance point to do it in a hook at the db level or as a custom type and write the marshall/unmarshall functions into a class? Can anyone just explain how those work? By the manual, I'm not sure if we add them in just our application as a type or if we develop them and deploy them as a jar into OrientDB On Tuesday, June 23, 2015 at 2:20:11 PM UTC-4, Joel Spriggs wrote: > > Is there any tutorials or examples on how to implement a custom type for > use in OrientDB? > > I had some hooks created to help with encryption/decryption of fields in > our database, but I'd like to try it out in a custom field if it would work > as an installable custom field in the db. Mainly because our encryption > needs to be applied at field level, and not across necessarily all fields > in a record. But I haven't seen any guides or examples on the > marshalling/unmarshalling methods and implementation. > -- --- 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.
