Personally, if I was having issues like yours I would just create my own Id's (uuid), but it's seems more of a AngularJS problem, not Orientdb. good luck.
On Tuesday, March 11, 2014 6:31:04 AM UTC-5, Gaurav Dhiman wrote: > > I am sure many users of orient must have face this challenge. Kindly > suggest simplest way to handle. > > Scenario: > 1. Calling server function over REST > 2. Server returns multiple records of a class with # in RIDs > 3. Client user received RIDs to make further REST document calls, but due > to # chanracter presence, calls go without RID argument > > Due to # character, call to > *http://<<host>>:<<port>>/document/<<db>>/#RID* is considered as > *http://<<host>>:<<port>>/document/<<db>>* > > Workaround: > While receiving response from server, remove all # characters from > response, but this add un-required processing. It would have been better if > # has not been there. > > Question: > What is the significance of having # in RID ? Can't we get rid of it ? If > yes, how ? > > Regards, > Gaurav > -- --- 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.
