cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kosh.Pod...@ubsw.com
Subject RE: Re: Re: ESQL support for stored procedures
Date Mon, 21 Jan 2002 13:14:06 GMT
Apologies if you have received this twice - got some mail delivery 
errors.

> -----Original Message-----
> From: Podder, Kosh 
> Sent: 21 January 2002 11:14
> To: haul
> Cc: Peter.Durrant; cocoon-dev
> Subject: RE: Re: Re: ESQL support for stored procedures
> 
> 
> Thanks Christian - I will test this, compare with our "quick 
> fix" efforts, and give you some feedback based on our usage 
> so that we can work towards something that is as 
> database-agnostic as possible with which everybody is happy.
> 
> Hopefully, this can then be pushed back into the next Cocoon release.
> 
> Cheers,
> 
> Kosh
> 
> > -----Original Message-----
> > From: haul 
> > Sent: 21 January 2002 10:24
> > To: Podder, Kosh
> > Cc: haul; Peter.Durrant; cocoon-dev
> > Subject: Re: Re: ESQL support for stored procedures
> > 
> > 
> > Kosh, Peter,
> > 
> > at long last I have put together a working patch for stored 
> procedure
> > support in esql. It works with INFORMIX and should work with
> > Oracle. Well, it should work with any DBMS but who knows.
> > 
> > As I have some problems with my CVS access right now, I 
> have included
> > a diff to today's head branch.
> > 
> > It defines a new tag <esql:call/> as a replacement for <esql:query/>
> > and will result in having a CallableStatement executed. To 
> declare out
> > or inout parameters use <esql:parameter direction="out"/> or
> > <esql:parameter direction="inout"/> plus any other 
> attributes that you
> > need. Currently, it is important to use proper cases for 
> types of out
> > parameters (e.g. "Int", "AsciiStream") because they are 
> looked up for
> > their matching JDBC type.
> > 
> > In order to make INFORMIX happy, an additional attribute for
> > <esql:call/> exists: "needsQuery='yes'" forces esql to 
> executeQuery()
> > instead of execute(). Otherwise an error "cursor already released"
> > will occur.
> > 
> > In order to make Oracle happy, an additional attribute for
> > <esql:call/> exists; "resultSetFromObject='n'" where number is an
> > integer specifying the out parameter that will be used to obtain the
> > actual result set.
> > 
> > Both additional attributes should not be necessary if the 
> DBMS adheres
> > to the JDBC standard, I think. Although we should think about how to
> > access the out parameters more consistanty. Perhaps add an attribute
> > to <esql:get-XXX outparameter="n"/> ?
> > 
> > Looking forward for comments from you and all that use stored
> > procedures with other DBMSs.
> > 
> > > Earlier today, I made the few minor additions necessary 
> to the esql 
> > > logicsheet, so that we can now use our Sybase stored procs 
> > via support 
> > > for CallableStatement, which seems to work fine. I can post 
> > it here if 
> > > anybody is interested.
> > 
> > sure thing!
> > 
> > > I'll be interested to understand more about the causes of 
> > the problems 
> > > that you are experiencing, since we may come across similar 
> > problems 
> > > using Sybase - are these really errors really orginating from the 
> > > Cocoon ESQL layer, or are they due more to the 
> > implementation of the 
> > > JDBC drivers?
> > 
> > I think it is the JDBC layer. INFORMIX doesn't like 
> CallableStatements
> > being execute()'ed but requires them to be executeQuery()'ed.
> > 
> > Cheers.
> > 
> > 	Chris.
> > 
> > -- 
> > C h r i s t i a n       H a u l
> > haul@informatik.tu-darmstadt.de
> >     fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08
> > 
> 


Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message