Transaction management using REST API [moved]

[lvca]

This is Issue 90 moved from a Google Code project.
Added by 2010-07-31T10:31:12.000Z by emailmat...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.

Original labels: Type-Enhancement, Priority-Low, v1.4.0

Original description

I miss the possibility to handle transactions through the REST API. It would be great if the SQL commands START TRANSACTION, COMMIT and ROLLBACK were supported.

[odino]

this is THE missing feature

currently everyone that uses the HTTP protocol is bound to a request per query: imagine having the need to update 1k records

[lvca]

It's on my todo list!

[lvca]

Execute a batch of commands in one shot. This is useful to reduce network latency issuing multiple commands as multiple request. Batch command supports transactions.
Format: { "transaction" : , "operations" : [ { "type" : "" }* ] }
Where:

type can be:
'c' for create
'u' for update
'd' for delete. The '@Rid' field only is needed.
Example:
{ "transaction" : true,
"operations" : [
{ "type" : "u",
"record" : {
"@Rid" : "#14:122",
"name" : "Luca",
"vehicle" : "Car"
}
}, { "type" : "d",
"record" : {
"@Rid" : "#14:100"
}
}, { "type" : "c",
"record" : {
"@Class" : "City",
"name" : "Venice"
}
}
]
}

[odino]

👍

[odino]

hi @lvca, is this gonna be included in 1.4.0?

[lvca]

Course, look at the "Milestone" field in this issue ;-)

[odino]

ok, when is it scheduled to be released?

[lvca]

We're in late with that. It was planned for end of Jan, but will be released at mid Feb.

[odino]

👍