Thanks for the help.
Is it possible to work with temporary tables inTryton?
The table handler has nothing for that in standard. Mainly because we have never had the need.
There is a need to perform quite complex calculations in a temporary table. Without this table, there are a lot of nested queries.
I do not see any advantage of temporary table when you have python-sql and CTE that abstract the queries. The database engine will materialize or not the sub-queries if it find it is needed.
I can see that the calculations in the temporary table are much faster than with a lot of sub-queries.
Of course if you duplicate the sub-queries. But using a CTE this should not happen except for some cases where it will be better to materialize it (see Bug 82: Add MATERIALIZED to CTE definition - python-sql tracker).