SQLProcessor and SQL taglib changes committed

[Donald Ball <ba...@webslingerZ.com>]

I've commited two little patches -

SQLProcessor should now _not_ print out @BF2391 or some such nonsense when
encountering a binary varchar or text field, now it should attempt to
create a String more intelligently. Please, those of you who've reported
problems in this regard, check out this code and test it so we can release
1.7.1 with a clean conscience.

SQL XSP taglib has been patched according to Ricardo's magnificent
instructions and now interpersing strings and elements in the <sql:query>
element work wonderfully. I'll probably have more changes to make to the
stylesheet now that I grok the problem in more fullness, but this
shouldn't stand in the way of 1.7.1 - if you're really using XSP, you're
grabbing cocoon from CVS anyway ;)

- donald

Re: SQLProcessor and SQL taglib changes committed

[Ulrich Mayring <ul...@denic.de>]

Donald Ball wrote:

> shouldn't stand in the way of 1.7.1 - if you're really using XSP, you're
> grabbing cocoon from CVS anyway ;)

Hmm, I'm really using XSP and waiting impatiently (sorry ;-) for the
1.7.1 release - but it would not occur to me to grab something from CVS,
which is in an undefined state.

Ulrich

-- 
Ulrich Mayring
DENIC eG, Softwareentwicklung

Re: SQLProcessor and SQL taglib changes committed

[Thorbjoern Ravn Andersen <ra...@mip.sdu.dk>]

On Wed, 29 Mar 2000, Donald Ball wrote:

> I've commited two little patches -
> 
> SQLProcessor should now _not_ print out @BF2391 or some such nonsense when
> encountering a binary varchar or text field, now it should attempt to
> create a String more intelligently. Please, those of you who've reported
> problems in this regard, check out this code and test it so we can release
> 1.7.1 with a clean conscience.

My initial tests show that I now get proper strings returned with my
datetime fields.

Thank you for a prompt fix.

-- 
  Thorbjørn Ravn Andersen               "...plus...Tubular Bells!"
  http://www.mip.sdu.dk/~ravn