On Jun 23, 2009, at 9:45 AM, Vishal Shetye wrote:
> I initially thought of putting all the queries per operation in a
> runInteraction. However this results in code-duplication as many
> queries are shared between different operations.
It seems like the easiest way to deal with this would be t
Hi,
I am working on an application that uses twisted and twisted.e.adbapi with
sqlite in the backend.
All db queries are put in separate functions in class say tableGateway.py which
uses runOperation, runQuery etc as appropriate.
A layer that uses it, lets say objectGateway.py, defines operations
