I believe OrientDB is setting it as a BigDecimal (https://github.com/orientechnologies/orientdb/wiki/Network-Binary-Protocol#wiki-record-format under numbers).
The regex in OrientDB used to recognize the "c" after the "6" is making it look like a number is the value. And in my case it is a hash. OrientDB should look at the whole value instead of a number and the first character after. Hopefully it is an easy fix. We are using the latest version from git. Thanks!! -- --- 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/groups/opt_out.
