RE: Dbtags dumps SQL code to output page on empty result

[Xose Ramon Sousa Vazquez]

Perhaps this help you
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4877
See the last comment from Matthias Rambold



-Mensaje original-
De: VP Research [mailto:[EMAIL PROTECTED]]
Enviado el: martes, 26 de noviembre de 2002 0:03
Para: [EMAIL PROTECTED]
Asunto: Dbtags dumps SQL code to output page on empty result


We're using the dbtags tag library (v 1.0) to retrieve and format data from
a
back-end database in a Struts web-app. When a query has no results, the SQL
code for the query will appear in the output page. This may be useful for
debugging in some cases, but since empty results are expected in our queries
and are accounted for using the dbtags:wasEmpty tag, we need to be able to
suppress the SQL code dump.

We understand that in some incarnations of the dbtags tag library, there was
an option to dump the SQL code under programmer control. We cannot find this
feature in the current documentation or taglib descriptors, and cannot find
any reference to control of the code-dumping behavior in the on-line docs or
through Google.

Note that even behavior attached to the dbtags:wasEmpty tag cannot provide
proper warnings in all cases. Some database operations within a page (e.g.,
queries resulting in the creation of a temporary table when the back-end
database SQL implementation does not support nested queries) are triggered
by a dbtags:execute tag rather than by the dbtags:resultSet tags. To our
understanding, the dbtags:wasEmpty tag can only be used following the
dbtags:resultSet tags.

It may be worth noting that we use these queries for the original purpose of
tags -- that is, allowing non-programmers to modify and maintain their own
web pages. The in-page queries are read-only for security and we have found
this approach useful in moving small page-maintenance tasks out of the
programming team and back into the domain of the page-designers. More
complex database activities, including any updates, take place through our
business-entity lightweight classes (a lightweight replacement for the EJB
architecture) and are retained within the programming team.

We would like to control the presence or absence of the code-dumping
behavior, or -- at the very least -- be able to suppress it completely. Any
suggestions compatible with continued use of dbtags?


--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

Transactions with dbTags

[Xose Ramon Sousa Vazquez]

I am working with dbTags and PostgreSQL. I'd like to perform TRANSACTIONS
with dbTags. How can i do it?.
I have tried to send a several queries like BEGIN insert.. COMMENT, but
it performs an error before the first insert.
Is it posible to make a transaction using only dbtags sql:statement id=a
con=b/sql:statemenmt?

Thanks in advance

Xosé Ramón Sousa Vázquez
Optare Solutions S.L.
[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

dbtags Tomcat 4.1.12

[Xose Ramon Sousa Vazquez]

We are seeing some strange behavior from dbtags since we switched to
Tomcat 4.1.12.  I'm pretty sure it's related to the new tag pooling
feature of Tomcat. I am wondering if anyone else is having problems.

If we have two statements on the same page, where the first one
 returns rows, but the second does not, the second statement tag prints
 out the actual text of it's query instead of nothing.

 For example:
   sql:statement id=stmt2 conn=conn
 sql:queryselect * from foo/*a query that returns rows*//sql:query
 sql:resultSet id=rset2
 /sql:resultSet
   /sql:statement

   sql:statement id=stmt3 conn=conn
 sql:queryselect * from bar /*a query that returns NO
 rows*//sql:query
 sql:resultSet id=rset3
 /sql:resultSet
   /sql:statement
 Would actually send back to the browser

   select * from bar /*a query that returns NO rows*/

Thanks

Xosé Ramón Sousa Vázquez
Optare Solutions S.L.
[EMAIL PROTECTED]
Tlfno: 986 410 091


--
To unsubscribe, e-mail:   mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:taglibs-user-help;jakarta.apache.org

Srollable result rows

[Xose Ramon Sousa Vazquez]

I was developing a web application and i am using dbTags. Is there any way
to take only some rows from a query without pass it manually. I am talking
about something like a scrollable query sql:resultSet scroll=yes
maxrows=20.
Thanks


Xosé Ramón Sousa Vázquez
Optare Solutions S.L.
[EMAIL PROTECTED]
Tlfno: 986 410 091


--
To unsubscribe, e-mail:   mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:taglibs-user-help;jakarta.apache.org