cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sonney <>
Subject Re: Which comes first?
Date Thu, 17 Aug 2000 10:41:51 GMT
On Thu, 17 Aug 2000, Wong Shin Neng wrote:
> I thought using the XSP SQL logicsheet is an alternative?  What's the big
> difference?  Althogh I thought using the SQL processor seems more efficient
> because u put the connection definitions is one chuck and use them any part
> in the xml document.

Actualy, development ahs halted on the SQL Logicsheet. Donald has said so
several times on list, and I suppose that the cocoon dev guys (*hint*
*hint*) might want to mark it as depricated like they do with the DSP

The big thing is that the XSP SQL Logic sheet uses XSP, and therefor
allows you to actually use more than *JUST* the request data and XSL to
get query info. 

And you can still define a single connection block, like so :

<!-- begin sample sql doxument -->
<?xml version="1.0"?>
<!DOCTYPE xsl:stylesheet [
<!ENTITY sql_params SYSTEM "db_defs.xml">

<?cocoon-process type="xsp"?>
<?cocoon-format type"text/html"?>


	<sql:query>select * from sample_table</sql:query>
<!-- End Sample page -->

<!-- begin db_defs.xml -->
<?xml version="1.0" encoding="UTF-8"?>


<!-- end db_defs.xml -->

I'm designing an app that uses jsut *ONE* db_defs.xml for about 30 pages
so far. 


| Kevin Sonney |
| Systems Programmer |

View raw message