Hi, Transactions don't support returning of single values, yet. But if you execute atomic command you could get back the RID and entire record by adding RETURN AFTER at the INSERT command:
INSERT INTO user_login (user_id, login, ip, user_agent) VALUES (#11:0, 1391722545, "127.0.0.1", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36") RETURN AFTER Lvc@ On 13 February 2014 00:57, Erik Weinmaster <[email protected]> wrote: > Luca, > > Thanks for the quick reply. I was in fact using 1.6.4, and once I > downloaded 1.7.rc1 I was able to insert into the database (without setting > the content-type to application/json). However, I must side with yapro and > his issue (https://github.com/orientechnologies/orientdb/issues/1944). I > need to get the last inserted rid from an insert into command. Otherwise, I > don't understand how to hook up an edge to a new vertex if I don't have the > last one that was inserted. > > Thanks again for the response, > > -Erik > > > On Wednesday, February 12, 2014 12:13:27 PM UTC-8, Lvc@ wrote: > >> Hi, >> what release are you using? With 1.6.x please add content type in request >> header. Starting from 1.7 we fixed it by making it optional >> (default=application/json) >> >> Lvc@ >> >> >> On 12 February 2014 20:10, Erik Weinmaster <[email protected]> wrote: >> >>> I'm using the orientdb-odm doctrine driver and for some reason the >>> INSERT INTO command times out. I'm inclined to say this is a DB issue since >>> SELECT is working perfectly. My INSERT INTO isn't too complicated its >>> bascially inserting into a class that logs user login times. So an example >>> of an insert that I'm sending would be this: INSERT INTO user_login >>> (user_id, login, ip, user_agent) VALUES (#11:0, 1391722545, "127.0.0.1", >>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, >>> like Gecko) Chrome/32.0.1700.107 Safari/537.36"). Also, I have user_id as a >>> string since I really don't want an edge associated with it, its merely a >>> reference as to who logged in when. >>> >>> The weird thing is that the curl_exec command times out, but when I >>> check the db, I do see the new entry for the user_login class. Is there >>> something I'm forgetting or is this a bug? >>> >>> Any help is much appreciated, >>> >>> -Erik >>> >>> -- >>> >>> --- >>> 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. > -- --- 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.
