Donald,
For the project I am working on, we mostly need to query databases and do
some simple transformations on it, we don't need the fancy stuff that xsp's
provide.
We also need to use stored procedures and the code for the SQLTransformer
could easily be adapted to add this functionality (don't know if this is
possible with esql)
A more personal note: i don't like to mix a lot of things, i think it is
better to use a transformer more or to split up the logic in multiple
matchers and concatenate the result with aggregation.
Sven
-----Original Message-----
From: Donald Ball [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2001 7:51 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [C2.1] bug SQLTransformer.java
On Thu, 21 Jun 2001, Beauprez Sven wrote:
>
> Dims,
>
> i will update the documentation i have now and i will post them asap.
> (but probably not before the weekend)
>
> There is one thing that should be changed to the SQLTransformer at line
64:
> - public static final String my_uri = "http://apache.org/cocoon/SQL";;
> + public static final String my_uri =
> "http://apache.org/cocoon/SQL/2.0";;
>
> This is because we still use to old way here and i forgot to change it
please change it instead to:
http://apache.org/cocoon/SQL/Transformer/2.0
to avoid confusion with the esql logicsheet's namespace. just out of
curiousity, why do you prefer to do sql queries using the sql transformer
instead of the esql logicsheet?
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
