Verify Sqlite is thread-safe
Submitted by Jim Nelson
Link to original bug (#715206)
Description
---- Reported by jim@yorba.org 2009-05-18 14:42:00 -0700 ----
Original Redmine bug id: 266
Original URL: http://redmine.yorba.org/issues/266
Searchable id: yorba-bug-266
Original author: Jim Nelson
Original description:
Only necessary if/when background threads are implemented. Although FAQ states Sqlite3 is thread-safe, it is a compiler flag and should be checked at run-time.
Alternatively, build threads in such a way that all Sqlite activity occurs in the Gtk main loop.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:46:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 3 years ago
-
Target version deleted (
<strike>
__</strike>
) - Priority set to High
We now have background threads, so presumably now is the time to think about this. Upping to high.
Comment 2
Updated by Adam Dingle over 3 years ago
- Status changed from Open to 5
- Resolution set to wontfix
- % Done set to 0
It turns out that we never run Sqlite in the background thread, so we don't need to worry about thread safety at this time. Closing.
Comment 3
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:41 UTC ---
This bug was previously known as bug 266 at http://redmine.yorba.org/show_bug.cgi?id=266
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INVALID