MySongs'); DROP TABLE meta_keys;--

While this certainly is possible, corrupted files on the file system level is actually extremely rare since OS X 10.5.steko wrote:Maybe one of your indexed directories/folders is corrupted, or contains (a) corrupted file(s. A tool like DiskWarrior would come in handy now…
That's why only mholloway is having this...Stromkraft wrote:While this certainly is possible, corrupted files on the file system level is actually extremely rare since OS X 10.5.
Of course - but if it still happens after deleting "files.db"?Stromkraft wrote:Naturally, the index process could itself have corrupted some database records on the database level or be inconsistent.
Rahad Jackson wrote:My Awesome Mix Tape #6
As I said, that's possible. I'd sooner suspect hardware about to give up than actual file system errors on a fully working disk though. That being said, there's obviously nothing wrong with running Disk Warrior or similar if one owns it.steko wrote:That's why only mholloway is having this...Stromkraft wrote:While this certainly is possible, corrupted files on the file system level is actually extremely rare since OS X 10.5.
If some process for some reason is writing erroneous data to the db, that may be recreated during use or attempts to rebuild the db.steko wrote: if it still happens after deleting "files.db"?
Rahad Jackson wrote:My Awesome Mix Tape #6
I wasn't thinking clone, but a rebuild. I actually had some corrupt Live presets just the other day and those crashed Live, which is a rare thing for me.steko wrote: 2. Corrupted files would get carried over to a clone, right?