https://bugs.kde.org/show_bug.cgi?id=363697
--- Comment #16 from Johannes Hirte <johannes.hi...@datenkhaos.de> --- (In reply to swatilodha27 from comment #15) > Is it possible to already have a "Fake Album" row when the DB is initially > created? > In the DB schema file, adding a query: > // > INSERT INTO AlbumRoots values(0, "Fake Album Root", 0, 0, NULL, NULL); > // > > This way the current UPDATE query in the makeStaleAlbum() would execute > without foreign key constraint failure. Did this manually and it seems to work. But I don't know if other parts of the code may get confused about this fake album. > Also, when deleteStaleAlbum() would be called, all those Albums would be > deleted from the DB. > It just need to be take care to include this function in a way that it gets > executed each time when digiKam is started. I don't really understand the mechanism of hints for now. Just calling deleteStaleAlbums() unconditionally will do, what you're suggesting. Maybe this is overkill and we can hook this in another place better. -- You are receiving this mail because: You are watching all bug changes.
