I am using SQLiteJDBC to save and load files using the native libraries on both OS X and Windows. During the opening or creation of a file, when running on OS X with the file located on a network share, I always get a "database is locked" error in the executeUpdate function. Files that are located on the local machine save and load just fine. I have updated to the 034 driver version (Thanks for that David).
I don't know too much about Mac file sharing, but I do not think the set up of the network shares is the problem here. I can save other files to and from those shares, even from inside my Java application. For example, my export to PDF feature works fine to these shares. I have also used other SQLite utilities, such as SQLiteManager, to open my database files from these shares, or to create a new SQLite database in these shares without a problem. In addition, during saving of a file, SQLiteJDBC does actually create a new file in the share, during the getConnection call, it is just the first call to executeUpdate that believes the database is locked or busy. It seems to be just a Mac issue, because from Windows my application can save files to these shares and open files from these shares with no problem, no matter what platform (Mac, Windows, Intel, PPC) the share happens to reside on. The same problem occurs on both Intel and PPC Macs on OS X 10.4.9. Has anyone else seen this? Am I missing something here? Does anyone have suggestions for the easiest way to debug into the native dynamic library from Java on the Mac? Thanks. -- Rod --~--~---------~--~----~------------~-------~--~----~ Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
