Nested CFQuery Uses Wrong Datasource

Question

I'm using CF MX 7.0.2, and it's come to my attention that there is a problem with how CF handles nested queries. To illustrate it simply:
<cfquery name="insert" datasource="one">
     <cfquery name="select" datasource="two">
       select * from table
     </cfquery>
     insert into test values('blah')
</cfquery>
This set of code will attempt to insert the 'blah' value into datasource "two"! Not the expected "one". While this seems like a terrible way to make things, consider a more common scenario:
<cfquery name="insert" datasource="one">
   insert into test values('#myfunction()#')
</cfquery>
<cffunction name="myfunction">
  <cfquery name="select" datasource="two">
    select * from table
  </cfquery>
  <cfreturn "blah">
</cffunction>
Again, this will attempt to insert into datasource "two". Please tell me there's a hotfix I can't find for this...

Answer 1

I'm not sure what you gain by nesting the queries and not keeping them separate but thought you'd might like to know that the two scenarios you described function the same in CF8 as you note for CF7.
The following code works fine for me on both CF7 and 8:
Opt 1:
<cfquery name="q1" datasource="dsn1">
select role from end_users
</cfquery>
<cfquery name="q2" datasource="dsn2">
insert into role (id) values('#q1.role#')
</cfquery>
Opt 2:
<cfscript>
myStr = testFunc();
</cfscript>
<cfquery name="q1" datasource="dsn1">
insert into role (id) values('#myStr#')
</cfquery>
<cffunction name="testFunc" returntype="string">
<cfquery name="q2" datasource="dsn2">
select role from end_users
</cfquery>
<cfreturn q2.role />
</cffunction>
Doesn't seem like either one would be a significant rewrite or movement of your code.
Anyway, I thought you'd might like to know that both your scenarios work the same in 8 as 7 and, as a result, I don't think there would be a hotfix for CF7.