Any help here as well? I'm currently getting the record for the ID and setting the version/id from this record to the updated POJO and save the pojo. Doesn't seems to be an ideal solution.
Thanks in advance Aym On Sunday, December 22, 2013 11:43:36 PM UTC+8, Aymer wrote: > > Hi, > > I'm struggling to implement a quite common use case of a web application > with OrientDB. > > I've a POJO (created from user inputs - via form params) and saved in > OrientDB. But I'd need to give user an option to modify/update/delete this > POJO in later point of time. > I'm passing the recordID in the URL for all subsequent request for the > record. (So that I can associate the record) > But I'm not able to find an elegant way of updating this POJO with > modified user input. > > 1) Any recommended way to do that using ObjectDatabase API? > > Couple of follow up questions as well. > 2) How to get the recordId in a POJO after saving the document? (Currently > I'm using db.getRecordByUserObject( pojo, true > ).save().getIdentity().toString(); ) > > 3) Happened to see @OId, @OVersion annotations. Is it useful in anyway? Or > are these deprecated? couldn't find any docs around these. > > I'm using OrientDB 1.6.2, Java 1.7 on Ubuntu 13.10. > > Thanks > Aym > -- --- 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.
