Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 65531 invoked from network); 10 Feb 2004 17:10:12 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 10 Feb 2004 17:10:12 -0000 Received: (qmail 11379 invoked by uid 500); 10 Feb 2004 17:08:44 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 11338 invoked by uid 500); 10 Feb 2004 17:08:43 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 11242 invoked from network); 10 Feb 2004 17:08:42 -0000 Received: from unknown (HELO server8a.software-ag.de) (193.26.193.47) by daedalus.apache.org with SMTP; 10 Feb 2004 17:08:42 -0000 Received: from atmsg00.software-ag.at by server8a.software-ag.de; (8.11.6/8.9.3) id i1AH8fr13811; Tue, 10 Feb 2004 18:08:41 +0100 Received: by atmsg00.software-ag.at with Internet Mail Service (5.5.2657.72) id <1FZWRKXK>; Tue, 10 Feb 2004 18:08:25 +0100 Message-ID: <210EF74CED81D611A41A0002A5DA31CEE22E09@atmsg00.software-ag.at> From: "Schweigl, Johann" To: users@cocoon.apache.org Subject: SQL Transformer generates illegal element names Date: Tue, 10 Feb 2004 18:08:23 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3EFF8.7DA45D3C" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C3EFF8.7DA45D3C Content-Type: text/plain Hi all, recently I ran into a problem with SQL Transformer. The column names returned from the database are used for naming the children of sql:row, but those names can be something like "count(distinct xxx)" or 'SYS$xxxx', which violates the wellformed conditions of the return document. Is there any implementation of SQLTransformer that generates instead of , which would solve the problem? For predefined statements I can control the SQL that is passed to the transformer, but I run into big hassle when letting the user enter SQL directly. Thx, Johann ------_=_NextPart_001_01C3EFF8.7DA45D3C Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Hi all,

 

recently I ran into a problem with SQL = Transformer. The column names returned from the database are used for naming the = children of sql:row, but those names can be something like "count(distinct = xxx)" or 'SYS$xxxx', which violates the wellformed conditions of the return = document.

 

Is there any implementation of SQLTransformer = that generates <column name=3D"xxx"> instead of <xxx>, = which would solve the problem?  For predefined statements I can control = the SQL that is passed to the transformer, but I run into big hassle  when = letting the user enter SQL directly.

 

Thx,

Johann

------_=_NextPart_001_01C3EFF8.7DA45D3C--