Difference between revisions of "Talk:Pager Nagger"
(clarification re mistaken warning -- sorry) |
|||
| Line 1: | Line 1: | ||
| − | |||
The big warning on this page seems a bit unfounded, especially the claims that sqlite is designed for one process at a time and that reads (SELECT) create locks. | The big warning on this page seems a bit unfounded, especially the claims that sqlite is designed for one process at a time and that reads (SELECT) create locks. | ||
| Line 8: | Line 7: | ||
Multiple processes can have the same database open at the same time. Multiple processes can be doing a SELECT at the same time. But only one process can be making changes to the database at any moment in time, however. [[User:JackieRipper|JackieRipper]] 01:26, 3 September 2009 (UTC)JackieRipper | Multiple processes can have the same database open at the same time. Multiple processes can be doing a SELECT at the same time. But only one process can be making changes to the database at any moment in time, however. [[User:JackieRipper|JackieRipper]] 01:26, 3 September 2009 (UTC)JackieRipper | ||
| + | |||
| + | You're right, my assumptions regarding locking all came from experience with older versions of sqlite (not sqlite3) and from jettero's initial report of findings. My mistake, and sorry for inadvertently maligning the script. I still think direct access to databases with sqlite3 is best avoided and a simple mojo app could do this better. --destinal. | ||
Re: warning (moved from main page) | Re: warning (moved from main page) | ||
I'm not entirely convinced the crash related to the nagger. My nagger is/was a daemon written in C that did pretty much the exact same thing as the shellscript (but also checked the email address of the 6245 SMS). I have attached a crashlog to [[JetsSelfInflictedWipeCrash | this page]]. --jettero | I'm not entirely convinced the crash related to the nagger. My nagger is/was a daemon written in C that did pretty much the exact same thing as the shellscript (but also checked the email address of the 6245 SMS). I have attached a crashlog to [[JetsSelfInflictedWipeCrash | this page]]. --jettero | ||
Latest revision as of 04:21, 3 September 2009
The big warning on this page seems a bit unfounded, especially the claims that sqlite is designed for one process at a time and that reads (SELECT) create locks.
Can multiple applications or multiple instances of the same application access a single database file at the same time?
Multiple processes can have the same database open at the same time. Multiple processes can be doing a SELECT at the same time. But only one process can be making changes to the database at any moment in time, however. JackieRipper 01:26, 3 September 2009 (UTC)JackieRipper
You're right, my assumptions regarding locking all came from experience with older versions of sqlite (not sqlite3) and from jettero's initial report of findings. My mistake, and sorry for inadvertently maligning the script. I still think direct access to databases with sqlite3 is best avoided and a simple mojo app could do this better. --destinal.
Re: warning (moved from main page)
I'm not entirely convinced the crash related to the nagger. My nagger is/was a daemon written in C that did pretty much the exact same thing as the shellscript (but also checked the email address of the 6245 SMS). I have attached a crashlog to this page. --jettero