GNOME Bugzilla – Bug 477690
Crash on search
Last modified: 2007-09-18 07:31:14 UTC
Steps to reproduce: 1. Focus the browsing window, type "/" (without quotes) 2. Type anything into the appearing search field and wait or press enter. 3. F-Spot crashes on starting his search. Stack trace: Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id FROM photos WHERE (((id IN (SELECT id FROM photos WHERE name LIKE '%Street%' OR directory_path LIKE '%Streest%' OR description LIKE '%Street%'))) AND id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2)) ORDER BY photos.time Exception in Gtk# callback delegate Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception. Mono.Data.SqliteClient.SqliteSyntaxException: no such column: directory_path at Mono.Data.SqliteClient.SqliteCommand.GetNextStatement (IntPtr pzStart, System.IntPtr& pzTail, System.IntPtr& pStmt) [0x00000] at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000] at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior) [0x00000] at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader () [0x00000] at (wrapper remoting-invoke-with-check) Mono.Data.SqliteClient.SqliteCommand:ExecuteReader () at Banshee.Database.QueuedSqliteCommand.Execute () [0x00000] at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal) at GLib.Timeout+TimeoutProxy.Handler() at GLib.Timeout+TimeoutProxy.Handler() at Gtk.Application.gtk_main() at Gtk.Application.gtk_main() at Gtk.Application.Run() at Gnome.Program.Run() at FSpot.Driver.Main(System.String[] args) Other information: The SQL seems to be erroneous. There is no column `name` in the photos table and directory_path does not exist neither.
Created attachment 95713 [details] [review] Fixes the db query It seems that this search function used the db schema of an old version of f-spot. The patch should fix it.
fixed in r3371