[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xsp-dev
Subject:    Re: [ESQL]4 ideas for discussion
From:       "Tagunov Anthony" <atagunov () nnt ! ru>
Date:       2001-01-26 15:26:22
[Download RAW message or body]

On Fri, 26 Jan 2001 13:51:09 +0000 (GMT), Matt Sergeant wrote:

> On Fri, 26 Jan 2001, Tagunov Anthony wrote:
> 
> > On Thu, 25 Jan 2001 18:52:13 -0500 (EST), Donald Ball wrote:
> > 
> > > On Wed, 24 Jan 2001, Tagunov Anthony wrote:
> > > 
> > > > I've seen a pretty high traffic on the list in the last 20 minutes and
> > > > desided to remind again about questions I've been asking about
> > > > esql.xsl taglib in the last mounth.
> > > > 
> > > > Basicly, I was asking for 4 improvements (features?) to the official ESQL:
> > > > 
> > > > 1) there's a nice
> > > > }
> > > > <xsl:apply-templates/>
> > > > } finally {
> > > > 
> > > > section in the esql.xsl where actually all the db queries get
> > > > expanded. This is also a place where the connecting to database stuff
> > > > comletes and starcts database interaction. We've got a way to catch
> > > > errors in execute-query (error-results). What do you think if we do
> > > > something like esql.diff (this is just a draft, maybe there's a nicer
> > > > way to do this..)
> > > 
> > > um, what are you suggesting here?
> > 
> > well, my suggestion is to have some <esql:error-connection> in<esql:connection>
> > and instatiate it's contents in case Exception is throw from the code performing \
> > connection to the database. Speaking in tersms of esql.xsl this is what i have \
> > drafted in esql.diff (see the attachment). Of cource, I mean that if \
> > <error-connection> is instantiated the exception does not propaged up the stack. 
> > Thus we have a way to catch connection exceptoin \
> > (<esql:connection><esql:error-connection>) and a way to catch exception in query \
> > execution (<esql:execute-connection><esql:error-results>)
> 
> I think we should remove exception handling from esql altogether, and
> create a new exception taglib:
> 
> <except:try>
> ...
> <except:catch>
> <except:get-type/>
> <except:to-string/>
> <except:backtrace/>
> <except:throw/>
> </except:catch>
> </except:try>
> 
> I don't think it should be too fancy about catching any particular type of
> exception, because they will obviously vary from language to language.
> 
> Thoughts?
> 

Well, having such a taglib will be definetly NICE :))
But nevertheless, <esql:error-results> may be viewed as general handling of the \
errors that may happen while database interaction, and that does make sence to keep \
in the esql taglib, doesn't it?

Best regards,
 Tagunov Anthony


[prev in list] [next in list] [prev in thread] [next in thread]