Right up until you have to do anything remotely complex, when it turns into a nightmare of proprietary vendor extensions, (even more) messed up syntax and horrible performance (cursors, I'm looking at you!), et cetera.
Stored procedures (combined with update triggers) is an interesting idea, but personally I'm not a big fan of the database process spawning external tools, probably while in the middle of a transaction and everything... is the MySQL database even on the same computer as the media files being indexed?
-f0dder
Ouch! Sounds hard :/
Yes, media files & MySQL database are on same PC.
I don't know how stored procedures work, but if this was possible it would be preferable, I guess:
- when a new row is added, updated or deleted from database Thumbs --> table thumbnails, copy the relevant fields (path + filename) to another table in another database.
- when a row is deleted from database Thumbs --> table thumbnails, delete the corresponding line on the second database.
This second database, is not touched by ThumbsPlus, so fields can be added as needed.
a program / php script or whatever you find appropriate, would read line by line the table of the second database, and execute the external programs to collect data to insert.
The same program / php script or whatever you find appropriate would populate another table of this second database with the collected data.
Finally, another stored procedure, this one on the second database would copy the fields of the populated table of the second database to the main one, and delete the 2 rows of both tables in the second database.
I guess (and it is a guess!) this method would not compromise database speed/integrity, while a stored procedure starting a instance of an external something every time a line is added/updated on main database, would kill my PC, because ThumbsPlus might add a few thousand lines/minute, but my PC is not fast enough to compute crc32 and other data of big files (ex: DVDs) in real time
Again, sorry for my poor English. I try
Kiss kiss,
Tat