Paul wrote: > I've been testing SQLite JDBC for use in my application, and i've run > up against the above error message. Is this a limitation of SQLite > JDBC, or SQLite natively? How likely is it that this limitation will > be removed in the near future?
I was asked this question recently off list with regards to OpenOffice, which apparently relies on other types of cursors. The short story: it is a 'limit' of SQLite, it would require lots of messy code to circumvent this 'limit' in the JDBC driver, and so I do not intend to. A more complete story is that it is no limit at all. Cursors are a strange, unnecessary invention with very complex performance/memory use implications depending on the nature of the SQL query. Like all strange, unnecessary inventions, they are a bad idea. SQL is a powerful enough language to achieve the same effects, and as an added benefit you actually get some idea of the algorithmic complexity of your query. Most people want cursors to move back and forwards in a result set. This is how you do it with SQL: http://www.sqlite.org/cvstrac/wiki?p=ScrollingCursor d. --~--~---------~--~----~------------~-------~--~----~ Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
