Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Daniel Fagerstrom wrote:
We are chosen as committers as induviduals and not as representants
for our companies. From a community stand point I would say that it
is time to deprecate the SQLTransformer. As a representative for my
company I would rather say: no way, we have tons of code that depend
on it. It is a complicated question, but I don't think that the
answer is: I need it at my work so the rest of you should support it.
It is really hard to tell what is still useful and what not. Now, the
simple example of the SQLTransformer shows this: most of us seem to
agree that it's some legacy component and that flow etc. should be used
instead.
That is not correct, because of:
Now, think of a reporting tool done with Cocoon. This fetches some
hundreds of MB out of the database and just displays them. In this case
everything other than the SQLTransformer + Stylesheet is simply overkill
(ok, XSP+ESQL is fine as well) and too memory/time consuming.
SQLTransformer is the only *recommended* choice to do reporting in Cocoon.
Agree. The really ugly part of SQLTransformer is its ability to perform
insert/updates.
Yep, this part should be deprecated... Or at least discouraged.
I'm using ESQL in a number of places for publication purposes, and many
people agree that ESQL is what keeps XSP alive. We have to build an
equivalent for CTemplates.
Never used ESQL myself, no comment :-)
Vadim
