DB::autoExecute limitations

First of all I love autoExecute-- it works great for vanilla inserts and updates. This is a minor annoyance and there are plenty of work around but I thought I would mention it anyway. Most everything gets interpreted as a string so it is impossible to access other database entities, database constants, functions, sub-selects etc. It sure would be nifty to be able to generate something like: update my_table a set col1 = col2, date_field = to_char('YYYY-MM-DD', current_date), denormalized_summary_field = (select max(amount) from other_table b where b.id = a.id) where id = 1; Maybe an additional optional parameter that specified data types? I don't know what this would entail so I might be asking for the impossible here. Meanwhile I can always generate my sql manually when I need to get fancy :) culley