I tried just that line and it doesn't work. So I added (on a whim) doc.save(); and it then worked. So it seems, it is necessary.
Is there a log for errors on functions like this? How can one troubleshoot errors on functions, which are triggered? Also, I feel like a blind (ding)bat because of the missing information on how to use functions and triggers. And yes, being able to add custom functions at runtime adds a good bit of flexibility to the database. If it is at all performant, this is actually a USP above (I believe) MongoDB and Neo4J, especially with the ability to hook custom functions dynamically to CRUD triggers. This opens up a whole bunch of possibilities. I personally just need to learn more about how to use it and the missing docs is killing me. LOL! Scott -- --- 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.
