Post the stack trace of the exception and what specific sqlite jdbc 
function fails. Maybe from this information it will be obvious and you
can propose a fix.

--- [EMAIL PROTECTED] wrote:
> Some more information...  would this error be due to Sun's
> CachedRowSet?  Is the SQLite JDBC Driver doing anything different with
> resultsets that other drivers, because we were able to use the same
> code below with drivers for MySQL, Microsoft SQL Server, Oracle, etc
> without any problems.
> 
> We seem to only run into the issue described above (NYI error) with
> the SQLite JDBC Driver.
> 
> Thanks for any responses, we really want to get this resolved.
> 
> Eugene
> 
> On Apr 25, 9:31 am, [EMAIL PROTECTED] wrote:
> > Thanks for your response... Actually the code snippet I gave
> > previously was wrong.. this is what we are using:
> >
> >              CachedRowSetImpl crs = null;
> >              crs = new CachedRowSetImpl();
> >              ResultSet rs = stmt.executeQuery(sqlCmd);
> >              crs.populate(rs);
> >
> > And again, we get a NYI error.
> >
> > Thanks,
> > Eugene
> >
> > crs = new CachedRowSetImpl();
> > On Apr 23, 8:22 pm, Joe Wilson <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > --- [EMAIL PROTECTED] wrote:
> > > > Here is a snippet of the code we are using...
> >
> > > >             CachedRowSetImpl crs = null;
> > > >             ResultSet rs = stmt.executeQuery(sqlCmd);
> > > >             crs.populate(rs);
> >
> > > > The error occurs on the populate command...



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SQLiteJDBC" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlitejdbc?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to