Version: 0.8.0 beta2 (using KDE KDE 3.4.2) Installed from: Gentoo Packages Compiler: gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8) OS: Linux When loading digikam with a big pictures folder digikam gives the following output (debug): digikam: ScanLib: Finding non-existing Albums: 9 ms digikam: ScanLib: Finding items not in the database or disk: 143456 ms digikam: ScanLib: Updating items without date: 4 ms digikam: WARNING: sqlite_step error: database is full on query: REPLACE into Settings VALUES ('Scanned','2005-09-18T23:14:23'); digikam: WARNING: sqlite_step error: database is full on query: SELECT T.id, T.pid, T.name, A.url, I.name, T.iconkde FROM Tags AS T LEFT OUTER JOIN Images AS I ON I.id=T.icon LEFT OUTER JOIN Albums AS A ON A.id=I.dirid; digikam: WARNING: sqlite_step error: database is full on query: SELECT id, name, url FROM Searches; digikam: ImagePlugin_Core plugin loaded digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core and shows the application with empty albums tab. my pictures folder contains 6041 pictures and the total size is 9.5 giga.
database is full? Seems like a problem with harddisk space?
happens only when pictures folder is on NFS, when local folder works good.
See other bugreports about it. you could place the database on another place.
why not fixing it to support nfs? i dont think it's a big bug and maybe a simple solutions like: 1. writing db file in chunks instead of once (assuming this is how it is being done). 2. giving the ability to configure the location of the db file so it alone can be saved on local storage? any chance to address this issue?
the db writing part is handled by sqlite. for nfs based album library paths, have a look at --enable-nfs-hack flag for configure (./configure --help)