Hey

I just did a little test with my own data, and it seems if I create a 
string field on a vertex e.g. foo, and enter a value that looks like an 
@RID (and lets say for arguments sake it's valid), then using a fetchplan 
select against this vertex, then foo is populate with that record it was 
pointing to. Even though, there's no schema set to says it a link, nor does 
it have the conventional in or out prefixes. 

Isn't this unwanted behaviour / security risk? My instinct was that unless 
the field is either defined as a link via a schema, or has the known prefix 
of in_ / out_ (I'm guessing here on the internals of orientdb for edge 
properties) then it should not be fetched.

Any light casting available?


Thanks

Sky



-- 

--- 
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.

Reply via email to