Re: [sqlite] Mac file locking
P Kishor wrote: Still, you have a point, and maybe DRH will expound and enlighten us on his reticence to enable locking style equal to one. It seems he isn't so reticent after all. See checkin [5737] from this morning at http://www.sqlite.org/cvstrac/chngview?cn=5737. Dennis Cote ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
On Sep 22, 2008, at 12:37 PM, Dave Dyer wrote: Yes, I've noticed and reported this same problem. It appears that the SQLite bundled in Mac OS X has a special flag set to allow opening database files on networked volume, and that works great. So what's the name of this special flag? Probably this: http://www.sqlite.org/compile.html#enable_locking_style Compilation option SQLITE_ENABLE_LOCKING_STYLE. Dan. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
On Sep 22, 2008, at 3:02 PM, Dave Dyer wrote: Probably this: http://www.sqlite.org/compile.html#enable_locking_style Compilation option SQLITE_ENABLE_LOCKING_STYLE. Compiling the mac version with this flad defined seems to have fixed my problem. Is there any reason this shouldn't be on by default? It only works on a Mac. The build fails on other posix platforms. D. Richard Hipp [EMAIL PROTECTED] ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
On 9/22/08, Dave Dyer [EMAIL PROTECTED] wrote: Probably this: http://www.sqlite.org/compile.html#enable_locking_style Compilation option SQLITE_ENABLE_LOCKING_STYLE. Compiling the mac version with this flad defined seems to have fixed my problem. Is there any reason this shouldn't be on by default? I am guessing because all SQLite users are not Mac users (although I am), and/or all SQLite users don't worry about network shares (I don't). ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Puneet Kishor http://punkish.eidesis.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Open Source Geospatial Foundation (OSGeo) http://www.osgeo.org/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
It only works on a Mac. The build fails on other posix platforms. Then of course, it should only be enabled on Macs. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
It only works on a Mac. The build fails on other posix platforms. Then of course, it should only be enabled on Macs. Yes, I humbly agree. Can it please be enabled by default in the source so that when compiled on a Mac, it will enable opening of files on a network volume, in the same way as does the SQLite distributed with Mac OS X? This will facilitate consistency between default and user compiled SQLite, and facilitate this functionality across the board for the Mac OS X binary download on the SQLite web site, through to all the GUI programs that use the Zentus (or other) JDBC plug ins. Seems to be a simple fix with many rewards. Thanks, Tom BareFeet -- Compare SQLite GUI programs for Mac OS X: http://www.tandb.com.au/sqlite/compare/?ml ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
On 9/22/08, BareFeet [EMAIL PROTECTED] wrote: It only works on a Mac. The build fails on other posix platforms. Then of course, it should only be enabled on Macs. Yes, I humbly agree. Can it please be enabled by default in the source so that when compiled on a Mac, h... I understood DRH's statement as no, it can't be enabled by default in the source because that flag works only for Macs and it causes breakage on other platforms. Unless, he started providing platform specific code tarballs, which, I am assuming, is unnecessary burden for him and his team, this is just as easy to flag the build at compile time. Not any much more should be required, no? it will enable opening of files on a network volume, in the same way as does the SQLite distributed with Mac OS X? This will facilitate consistency between default and user compiled SQLite, and facilitate this functionality across the board for the Mac OS X binary download on the SQLite web site, through to all the GUI programs that use the Zentus (or other) JDBC plug ins. Seems to be a simple fix with many rewards. Thanks, Tom BareFeet -- Compare SQLite GUI programs for Mac OS X: http://www.tandb.com.au/sqlite/compare/?ml ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Puneet Kishor http://punkish.eidesis.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Open Source Geospatial Foundation (OSGeo) http://www.osgeo.org/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
h... I understood DRH's statement as no, it can't be enabled by default in the source because that flag works only for Macs and it causes breakage on other platforms. Unless, he started providing platform specific code tarballs I wouldn't expect it to require multiple code versions, just one version that sets the locking flag according to what platform it's on. ie if platform == 'Mac' then SQLITE_ENABLE_LOCKING_STYLE = 1 Surely it's that easy? No? Thanks, Tom BareFeet ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
On 9/22/08, BareFeet [EMAIL PROTECTED] wrote: h... I understood DRH's statement as no, it can't be enabled by default in the source because that flag works only for Macs and it causes breakage on other platforms. Unless, he started providing platform specific code tarballs I wouldn't expect it to require multiple code versions, just one version that sets the locking flag according to what platform it's on. ie if platform == 'Mac' then SQLITE_ENABLE_LOCKING_STYLE = 1 Surely it's that easy? No? Right, does sound easy. But what if I am on a Mac (which I am), but don't want network shares support (which I don't, well, not because I have anything against it, but I just don't need it) in case it comes with some side-effects? I don't know... I am assuming he has some wise reasons for not making that special case a default. He seems like a very conservative guy when it comes to fixing what ain't broken. Still, you have a point, and maybe DRH will expound and enlighten us on his reticence to enable locking style equal to one. Thanks, Tom BareFeet ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Puneet Kishor http://punkish.eidesis.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Open Source Geospatial Foundation (OSGeo) http://www.osgeo.org/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
Right, does sound easy. But what if I am on a Mac (which I am), but don't want network shares support (which I don't, well, not because I have anything against it, but I just don't need it) in case it comes with some side-effects? Well, when you're using the SQLite that shipped on your Mac (or newer version that shipped as part of your latest Mac OS X upgrade), then network shares support is already enabled by default. If you manually compile a newer version of SQLite, then network share support will suddenly disappear. This is inconsistent. The inconsistency also spreads to make some GUI apps support network share support (those that use Mac OS X's built in library or are smart enough to have fixed the omission in their included SQLite source code), while others don't (such as those powered by the Zentus JDBC which uses the default SQLite source code settings). Of course, if you want to disable network share support for some reason in your own compile, you'd be free to override the flag. Thanks, Tom BareFeet ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
On 9/22/08, BareFeet [EMAIL PROTECTED] wrote: Right, does sound easy. But what if I am on a Mac (which I am), but don't want network shares support (which I don't, well, not because I have anything against it, but I just don't need it) in case it comes with some side-effects? Well, when you're using the SQLite that shipped on your Mac (or newer version that shipped as part of your latest Mac OS X upgrade), then network shares support is already enabled by default. If you manually compile a newer version of SQLite, then network share support will suddenly disappear. This is inconsistent. I never use any system provided software for my own creations (well, not never, but mostly never). One, I can't depend on its ingredients; two, I can depend on whether it will remain as i expect it to or not in a subsequent upgrade; and three, it will always be a few versions behind the most current version usually available from the developer. I have Leopard 10.5.5 and the /usr/bin/sqlite3 (the factory installed version) is 3.4.0. I compile my own, both libsqlite as well as DBD::SQLite (it takes a few clicks of the mouse and builds painlessly), and am at 3.6.2. If you are using network shares as provided by the system sqlite, that capability shouldn't suddenly disappear at all unless you have made the huge mistake of writing over the factory installation (always install your own stuff under /usr/local/) The inconsistency also spreads to make some GUI apps support network share support (those that use Mac OS X's built in library or are smart enough to have fixed the omission in their included SQLite source code), while others don't (such as those powered by the Zentus JDBC which uses the default SQLite source code settings). Of course, if you want to disable network share support for some reason in your own compile, you'd be free to override the flag. My sense is that most users don't want network share support, hence it is not default. For the relatively few that do want, it exists as an option. Thanks, Tom BareFeet ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Puneet Kishor http://punkish.eidesis.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Open Source Geospatial Foundation (OSGeo) http://www.osgeo.org/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
My sense is that most users don't want network share support, hence it is not default. For the relatively few that do want, it exists as an option. I find that statement a bit ambiguous, so allow me to clarify my own interpretation: 1. Few or probably no users want to NOT have network share support. 2. It may be true that few users would ask for network share support, at least until they get a file locked error when using some SQLite GUI or using their own compiled code. I would argue that not having yet asked for it doesn't mean they don't want it, just that they don't know yet that they need it or can have it. In any case, it certainly doesn't mean that they want it to NOT be there (see 1). 3. All users have network share support built in with the SQLite that ships in Mac OS X and don't ask for it to be removed. Thanks, Tom BareFeet ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
Hi Dave, I'm experimenting with using networked files as sqlite databases (yes, I'm aware this is a questionable practice) It seems quite valid for remote access to make ad hoc small changes to large hosted database files, or to provide shared access to small user databases files via desktop GUIs. If the client is running on a mac, and the database file is not a local disk, database locked error is returned immediately. Yes, I've noticed and reported this same problem. It appears that the SQLite bundled in Mac OS X has a special flag set to allow opening database files on networked volume, and that works great. Unfortunately, it is not enabled by default in the SQLite source code. I have enabled it myself in the past and compiled my own later version of SQLite for Mac OS X, though I haven't tried it with recent releases and seem to recall someone else saying that the old method no longer works. I would really like to see the SQLite source code and downloadable Mac OS X binary have this flag enabled, so that it behaves predictably the same as the version distributed with Mac OS X. This has far reaching indirect consequences such as the developer of the Zentus JDBC SQLite driver matching their code also with the default distribution, so currently the dozen or so SQLite applications for Mac OS X that use the JDBC driver also fail to open networked database files. You can see some of the programs this limitation affects in my comparison table as Can open database file on AppleShare volume here: http://www.tandb.com.au/sqlite/compare/ Richard and co, please enable this flag by default. Thanks, Tom BareFeet ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Mac file locking
Yes, I've noticed and reported this same problem. It appears that the SQLite bundled in Mac OS X has a special flag set to allow opening database files on networked volume, and that works great. So what's the name of this special flag? ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] mac file locking
I'm experimenting with using networked files as sqlite databases (yes, I'm aware this is a questionable practice) If the client is running on a mac, and the database file is not a local disk, database locked error is returned immediately. I assume this means that the file lock mechanism failed, since there are no existing users sharing the database. Does anyone have information about this? On a related topic, XCODE seems to not be up to debugging the single file release - it gets very confused about where breakpoints are located. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
