Leszek Gawron wrote:
I was right. That is how JdbcEsqlQuery.getResultRows() shoud look like:
public void getResultRows() throws SQLException {
if ( getSkipRows() > 0 )
getResultSet().absolute(getSkipRows());
setPosition(getSkipRows());
}
I am not familiar with patch submitting so someone ple
I was right. That is how JdbcEsqlQuery.getResultRows() shoud look like:
public void getResultRows() throws SQLException {
if ( getSkipRows() > 0 )
getResultSet().absolute(getSkipRows());
setPosition(getSkipRows());
}
I am not familiar with patch submitting so someo
On Thu, Jan 09, 2003 at 11:03:38AM +0100, Torsten Curdt wrote:
> >No I don't.
> >
> >Shouldnt JdbcEsqlQuery.getResultRows() look like this (just a guess - I'm
> >not
> >experienced with jdbc):
> >
> >public void getResultRows() throws SQLException {
> > if ( getSkipRows() > 0 )
> >
No I don't.
Shouldnt JdbcEsqlQuery.getResultRows() look like this (just a guess - I'm not
experienced with jdbc):
public void getResultRows() throws SQLException {
if ( getSkipRows() > 0 )
getResultSet().absolute(getSkipRows());
setPosition(getSkipRows());
}
current ver
On Thu, Jan 09, 2003 at 10:39:42AM +0100, Torsten Curdt wrote:
> Leszek Gawron wrote:
> >I'm using cocoon to communicate with MS SQL Server via MS JDBC driver (Java
> >1.3). After switching to current HEAD I get an error message that did not
> >exist in my previous version:
> >
> >org.apache.cocoon
Leszek Gawron wrote:
I'm using cocoon to communicate with MS SQL Server via MS JDBC driver (Java
1.3). After switching to current HEAD I get an error message that did not
exist in my previous version:
org.apache.cocoon.ProcessingException: Exception in
ServerPagesGenerator.generate(): java.lang.R
I'm using cocoon to communicate with MS SQL Server via MS JDBC driver (Java
1.3). After switching to current HEAD I get an error message that did not
exist in my previous version:
org.apache.cocoon.ProcessingException: Exception in
ServerPagesGenerator.generate(): java.lang.RuntimeException: Error
