cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <ba...@webslingerZ.com>
Subject Re: [C2] esql connections diff
Date Thu, 02 Nov 2000 05:34:24 GMT
On Wed, 1 Nov 2000, Marcus Crafter wrote:

> 	2 things to be aware of though - the results are those from the last
> 	query; all others are dumped (not so bad), however the 'last' query
> 	may be xslt implementation dependant (ie. is the parse order of a
> 	stylesheet defined ?).
> 
> 	Any suggestions or improvements are welcomed.

hmm... that's definitely a good idea, i'm just not so sure the grammar is
as i'd like it. i think the query and the results elements should be
coupled more closely. perhaps if connection information were to be put
into its own element, and then whenever a query is executed, the closest
connection information element parent of the query node would be used?

<esql:connection>
 <esql:driver>...</esql:driver>
 <esql:execute-query>
  <esql:query>select * from department_table</esql:query>
  <esql:results>...</esql:results>
 </esql:execute-query>
 <esql:execute-query>
  <esql:query>select * from user_table</esql:query>
  <esql:results>
   <!--connection to other database for nested query-->
   <esql:connection>
    <esql:driver>...</esql:driver>
    <esql:execute-query>
     <esql:query>select * from password_table</esql:query>
     <esql:results>...</esql:results>
    </esql:execute-query>
   </esql:connection>
   <!--end connection to other database-->
  </esql:results>
 </esql:execute-query>
</esql:connection>

that way the scope of the connection is explicit... perhaps even paving
the way for support for manual commits and transactions and such. hmm. any
thoughts from other esql/sql users?

- donald


Mime
View raw message