[Opensim-dev] Inventory loss

Melanie melanie at t-data.com
Mon Jul 27 12:07:08 UTC 2009


IMHO, inventory loss due to MySQL errors and/or corruption are below 
the radar.
Any losses would occur in OpenSim code, I believe.

Melanie

Colin B. Withers wrote:
> I wonder what proportion of inventory items that go astray are the result of the success/failure of an operation, or are due to database corruption issues.
> 
> Rock
> 
> -----Original Message-----
> From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-bounces at lists.berlios.de] On Behalf Of Melanie
> Sent: Monday, July 27, 2009 12:30 PM
> To: opensim-dev at lists.berlios.de
> Subject: Re: [Opensim-dev] Inventory loss
> 
> There is a question here of why inventory loss occurs at all. At 
> what stage do we actually lose (as opposed to failing to bump the 
> folder serial) inventory items at all, and why?
> 
> While a "deleted" flag and an undelete function do make an admin's 
> life easier, I believe the real focus should be on the inventory 
> code. It will be redesigned anyway and once that happens, I think a 
> strong focus needs to be placed on data integrity preservation.
> 
> That would then mae the undelete functionality largely unnecessary. 
> Current inventory code often doesn't check for success of an 
> operation at all. That needs to be revisited.
> 
> Melanie
> 
> Thomas Grimshaw wrote:
>> Hey folks.
>> 
>> Been thinking a lot about inventory loss in OpenSim, something that I 
>> think we should really do as much as possible to avoid. We've been 
>> experiencing numerous cases of lost inventory in K-Grid recently.
>> 
>> What i'd like to implement, is..
>> 
>> When an item is removed from inventory (deleted, or rezzed if it's 
>> no-copy), it is not actually deleted by instead an "available" flag is 
>> set in the inventory database.
>> All inventory queries will check for the flag and thus it will appear as 
>> deleted to the user, but it can be restored easily by an admin if 
>> needed.  A timestamp should also be set which indicates when the item 
>> was made unavailable, so that routine cleanup can be performed on items 
>> which were made unavailable a long time ago.
>> 
>> I wanted to get people's opinons of this before I implemented it in 
>> code. Can anyone think of any drawbacks or possible issues? Any further 
>> room for improvement?
>> 
>> Cheers
>> 
>> Thomas Grimshaw
>> (RemedyTomm)
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>> 
>> 
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
> 
> 



More information about the Opensim-dev mailing list