Alessandro, this makes sense now. The relational db concepts gotten on my way of thinking.The @rid is referenced so heavily everywhere that I started to believe it is a regular field instead of being a metadata.
Quick question though, in the relational world we typically add an id column to a table to be able to reference it for any updates, etc. With the OrientDB I'm using @rid in place of the id column, is this a recommended practice? I find it useful, but wanted to hear from you as more experienced users to shed some more light with cons and pros of such usage for @rid. Thanks, On Thursday, October 27, 2016 at 3:24:56 AM UTC-7, [email protected] wrote: > > Hi, > subscription.fieldNames() returns only the properties and not the @rid > that is a metadata. > If you want to obtain the @rid you can use subscription.getIdentity(). > > If you print the result of subscription.toJSON() you can see the @rid. > Esample > {"@type":"d","@rid":"#41:0","@version":3,"@class":"Subscription","name":"name > 1","in_sellsTo":["#33:0"],"active":true,"@fieldTypes":"in_sellsTo=g"} > > Hope it helps. > -- --- 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.
