photools:cameraname - is this something new - recently added - gives me problems

[ubacher]

I rename my files with a script. Afterwards I get the yellow pencil showing that photools:cameraname and XMPMM:PreservedFileNmae
need to be written out. I then run a script which, for some files, copies data from jpg to dng (GPS data ). This process now takes a long time
and I think produces the errors in the log. Log file attached.

Code Select Expand

01.08 10:46:04+  422 [12A0] 01  W> 'database table is locked' [6]  'v:\develop\imatch5\src\imsq\imsqlite.cpp(2530)'
01.08 10:46:04+    0 [12A0] 01  W> BEGIN IMMEDIATE TRANSACTION  'v:\develop\imatch5\src\imsq\imsqlite.cpp(2531)'
01.08 10:46:04+    0 [12A0] 01  W> 'database table is locked' [6]  'v:\develop\imatch5\src\imsq\imsqlite.cpp(2540)'
01.08 10:46:04+    0 [12A0] 01  W> BEGIN IMMEDIATE TRANSACTION  'v:\develop\imatch5\src\imsq\imsqlite.cpp(2541)'
01.08 10:46:06+ 1172 [0D08] 01  W> ETWARN:Warning: Sorry, photools:cameraname doesn't exist or isn't writable
Warning: Sorry, photools:cameraname doesn't exist or isn't writable
  'v:\develop\imatch5\src\imengine\ptetwrapper.cpp(3431)'
01.08 10:46:07+ 1375 [0D08] 05  I> ExifTool: Launching from 'C:\Program Files\photools.com\imatch6\exiftool.exe', using IMatch config file 'C:\Program Files\photools.com\imatch6\imatch_et.config' (C:\PROGRA~1\photools.com\imatch6\imatch_et.config)
01.08 10:46:08+ 1250 [07C4] 01  W> 'database table is locked' [6]  'v:\develop\imatch5\src\imsq\imsqlite.cpp(2530)'
01.08 10:46:08+    0 [07C4] 01  W> BEGIN IMMEDIATE TRANSACTION  'v:\develop\imatch5\src\imsq\imsqlite.cpp(2531)'
01.08 10:

[Mario]

This is not an error. This is just a warning. This was a change done maybe six months ago.
Sometimes the camera name slips through into the diff and then ExifTool warns that it does not know the tag. Nothing to be concerned about, just ignore it.
If I have a lot of time I might dig into this and see how this happens. I think it happens only when the original file has no metadata at all.

I see many warnings about database tables being locked. When does this happen, what does your script do to cause this?
This warning is only issued when modules in IMatch lock database tables for more than several seconds (!)...