| Summary: | Add support for handling Kexi database files on NFS | ||
|---|---|---|---|
| Product: | [Applications] KEXI | Reporter: | Andrew Ziem <andrewz> |
| Component: | General | Assignee: | Kexi Bugs <kexi-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | adam, inksi, staniek |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | All | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Andrew Ziem
2006-04-27 22:45:26 UTC
Thanks for raising this issue. I know this but not everyone. As you may know, Kexi files are built using SQLite libraries. See what SQLite creators say: http://www.sqlite.org/faq.html#q7 "But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem." I am sure we'll need to mentione this in our manual. BTW, To be able to connect to the same sqlite (here: kexi) db some people recommend to implement a small server that acts as a dumb proxy for multiple clients, so real file is accessed only by one process. This is already on our TODO. For instance, see this dicussion: http://groups.google.com/group/comp.lang.tcl/browse_frm/thread/acfb27d701be3de/2481b12b9457808d?tvc=1&q=sqlite+nfs#2481b12b9457808d In my case, I don't care at all about locking. I know I am the only one using the database. So maybe an option for complete disabling file locking is needed. This may be another thing I'd need to change in the original SQLite implementation. Possible, as we, predicting we WANT to have control over out SQLite backend, we have a copy of it's source code within Kexi. Summing up, I tend to set resolution to "LATER". Changed to wish. Proper link to the SQLite FAQ is: http://www.sqlite.org/faq.html#q5 |