So, can you provide me a query to execute against GratefulDeadConcerts database that demonstrate the problem? I tried:
CREATE CLASS Users INSERT INTO Users set id="6ce3ef04cb2cb750d4ce0d0f9648066f" Then: select from Users and this is the (correct) result @rid @version @class id #14:0<http://localhost:2480/studio/index.html#/database/GratefulDeadConcerts/browse/edit/14:0>1Users6ce3ef04cb2cb750d4ce0d0f9648066f Lvc@ On 30 January 2014 12:53, Giraldo Rosales <[email protected]> wrote: > Typo in my initial email. The actual object sent is: > > {"userID":"6ce3ef04cb2cb750d4ce0d0f9648066f"} > > I'm trying to find the number formatting in the source code. I think if it > is temporarily turned off, it will fix the insert. > > As a permanent fix, if the number formatting is fixed it should recognize > a value of "6c" is different than "6ce3ef04cb2cb750d4ce0d0f9648066f" > > Now that I think of it, the numbers shouldn't be formatted unless a schema > is specified and a number field is set. > > What if I wanted to insert a string of, "6c"? OrientDB will insert it as > "6" even though I specified the field as string. Or what if I don't even > specify a string field property, a schema-less case? I wouldn't want > OrientDB to format "6c" as a number if I actually wanted it as a string > value (for whatever reason). > > Thanks Luca! > On Jan 30, 2014 6:39 AM, "Giraldo Rosales" <[email protected]> wrote: > >> The value is wrapped with quotes. It is with a SQL INSERT command. >> Haven't tested with UPDATE. >> >> Try it with the exact value I sent. I was able to recreate each time. >> >> When I insert the hash, only "6" is actually inserted, not the full hash. >> >> I believe it is the formatting of the BigDecimal. Since this example >> starts off with "6c...". It only inserts "6". >> On Jan 30, 2014 2:01 AM, "Luca Garulli" <[email protected]> wrote: >> >>> Hi, >>> Why the value isn't between quotes? >>> >>> Sent from Mobile device >>> Il 30/gen/2014 05:22 "Giraldo Rosales" <[email protected]> ha scritto: >>> >>>> I believe OrientDB is setting it as a BigDecimal ( >>>> https://github.com/orientechnologies/orientdb/wiki/Network-Binary-Protocol#wiki-record-formatunder >>>> 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. >>>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "OrientDB" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/orient-database/KYwZrXaL_LE/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> -- > > --- > 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. > -- --- 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.
