gaksland wrote:

 

I'm using LR4, the Develop module is very slow. The latest problem has presented real concern. In Develop Module I removed a photo and the whole file was deleated. I found the deleted file in the Windows recycle bin. I restored the file then reimported the file into LR4.

 

Now I'm concerned about doing work in LR4, I don't what will happen next.

When you try to delete a photo, you have two options: "Remove" or "Delete From Disk". Sounds like you clicked on Delete From Disk, that's the only way to have a photo wind up in the recycle bin.

Just happened to think to look in the Windows Recycle bin. I searched the bin for the file name I used in LR4. The search found the file (Storyland). I clicked restore file. I found the restored file in the LR4 directory in Windows right, were it should be. I then went into LR4 and used Import to bring the file in to LR4. I have just gone through the file and everything is there and I have been able to work with the file in Develop Module. This time I have used the flag for deletion option and that worked.

I did not want to lose any of the Grand kids images at Story Land!

Gene

gaksland wrote:

 

Yes, I have used the delete from disk before with no problem. This time Delete removed the whole file not just the selected image.

THere are multiple different types of selections in the Lightroom Library Module, unlike Windows where a file is either selected or not. You need to be careful to make sure only the file you want is selected (light grey) and others are not selected (medium gray) ... if you have photos selected with both light and medium gray when you do a delete, both selection will be deleted in that situation.

elcee52 wrote:

 

I never had a problem until now! I consider one catalog to be a Single Point Of Failure.

Not only are there bazillions of Lightroom users who haven't had a problem using a single catalog (okay, so thats an exaggeration, but I would guess there are hundreds of thousands of Lightroom users who haven't had a problem with a single catalog); but the solution is to make regular backups of your catalog. If my catalog goes bad today, I still have yesterday's catalog, and the day before -- not that my catalog has ever gone bad.

There are many many many benefits to having a single catalog; and many many many disadvantages to multiple catalogs. You have already come across one problem (human error) caused by multiple catalogs, something that will happen over and over again because us humans aren't perfect; but you are avoiding a failure mode that very rarely happens, and can be easily protected against.

It's your choice.