[Cubicweb] Which way to go to do remote RQL ?
aurelien.campeas at gmail.com
Thu Aug 7 13:31:14 CEST 2014
2014-08-07 10:14 GMT+02:00 Yann Cointepas <yann at cointepas.net>:
> Thanks for the awnser Aurélien.
> Big requests are an issue in genetics. I am not directly involved here but
> a collegue of mine (Antoine for those who know him) have reach the limit
> and he had to develop a workaround for some requests (via a view allowing
> to download the request in a JSON file).
We need to hear this in detail.
A couple months (or a bit more ?) ago, someone posted a script showing
performance degradation over many consecutive requests.
Is this related ?
> I use multiple requests transactions because users are sending packages of
> data. We garantie that a package that cannot be fully integrated in the
> base will be rejected (and possibly corrected and resent by the user).
> Rejected package leave nothing in the base. Since a package can contains
> various data (e.g. MRI Scans, MRI scans with processing results, only
> processing results, etc.), the content of the package in processed in a
> transaction. At the top level of the code there is a try...except:
> rollback() else: commit() and the DB insertion job is implemented in
> various classes. Each class is responsible of a specific kind of data or
> processing. Without commit/rollback, I would need to provide a way for
> these classes to record all what they have done to allow to "undo"
> everything that have been done prior to the error. AFAIK it is not trivial
> to implement (and it already exists in Cubicweb).
Ok. I think you should open a ticket with this.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cubicweb