Issues:
this does not need to be done on-the-fly for every query:
on first sight: compute the mapping process and cache it
based on a query signature use cached process
can also be done at compilation time
can all possible TMQL statements be converted into their SQL equivalents?
probably, but the performance of the retrieval process might vary considerably
some statements may result in nested loops in which individual SELECT statements are executed
difficult-to-use SQL know-how (call it a research challenge)
machine can reason about TMQL statements
TMCL and TMQL are considerable compatible in their semantics