On 10/28/2002 at 12:18 PM Shawn Bayern wrote: >On Mon, 28 Oct 2002, Donald Ball wrote: > >> When using the sql jstl taglib, is there any way to access the >> resultset metadata? I'm looking for a qnd way to get at the column sql >> types. > >EA versions of JSTL supported this, but version 1.0 of the specification >did not, primarily because it wasn't clear that JSTL should be used for >such advanced applications and because there were some tricky >implementation issues (concerning, e.g., what should be done with >exceptions that ResultSetMetaData methods throw). > >If you need access to metadata, it's probably best to write your >database-access code in a servlet. If you think it would be particularly >convenient for a future version of JSTL to offer this feature, you could >send a comment to the official JSTL feedback address at
For my bean-type object stuff, I do all of the SQL interaction in the java code hidden way behind the scenes. This component of the webapp, however, is a dataset viewer that interacts with the sql data directly. For this, the JSTL SQL taglib is a perfect fit; or would be, if I could just get access to the resultset metadata. I understand the desire to nudge people away from doing sql in their jsp pages directly, but sometimes it's what's called for. In any case, mind a quick question on the way the sql taglib is implemented? Is it the case that the code iterates over the ResultSet and pulls the data into the Result object before closing the jdbc connection? Or does it do something more clever so that the we don't have to pay the overhead of touching the data twice? > [EMAIL PROTECTED] Will do, thanks. - donald -- To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
