No subject

each root folder whose parentFolderId is zeroes) and determining if any 
inventoryitems are pointing at any of those subfolders (Clothes, Objects, 
Trash, Scripts, Clothes, etc.).

That would allow an identification of the scope of  the problem by a grid 
manager. From there a query to delete any that are empty, with what ever 
logical qualifiers might be useful.

In any case, perhaps I have or have not diagnosed the problem correctly, 
and any suggestions are appreciated.

Charles_______________________________________________
Opensim-dev mailing list
Opensim-dev at lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev


--=_alternative 003FD97485257432_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Charles</font>
<br>
<br><font size=2 face="sans-serif">I think you have captured the technical
consequences of having multiple inventory roots, but to resolve the issue
we need to properly understand the whys and wherefores of multiple roots.
Why do avatars have multiple roots? what are the functional differentiators?
I.e. why does it matter that we stop at the first? I was recently looking
through the new inventory/capabilities code and had had the same thoughts
as you expressed. It seems to me that there can be only one (apologies
to the Highlander) root directory. Given the information that is in it,
there is no reson for this directory to exist outside of an extant presence,
and all of the other hierarchies should exist as (apparent) subordinates
to this directory. This then raises questions of convenience as a result
of having something that is an unnecessary empty layer for the majority
of inventories where only one hierarchy exists; there are a number of ways
to address that such as collapsing any monotonous hierarchies. I assume
the overwhelmingly most important goal is that at the end of the day the
inventory is complete, predictable, and unambiguous.</font>
<br><font size=2 face="sans-serif"><br>
Best regards<br>
Alan<br>
-------------------<br>
T.J. Watson Research Center, Hawthorne, NY<br>
1-914-784-7286<br>
alan_webb at us.ibm.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Charles Krinke <cfk at pacbell.net></b>
</font>
<br><font size=1 face="sans-serif">Sent by: opensim-dev-bounces at lists.berlios.de</font>
<p><font size=1 face="sans-serif">04/20/2008 06:56 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
opensim-dev at lists.berlios.de</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">opensim-dev <opensim-dev at lists.berlios.de></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[Opensim-dev] multiple, empty, root
inventory folders</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3 face="Arial">The situation exists where a number of avatars
have multiple root inventory folders on OSGrid, and I suspect on other
grids as well. One of the implications is that this obscures the inventory
as our search stops at the first root inventory folder it finds, that is
the first one whose parentFolderId == zeroes.<br>
<br>
Having a query to identify and then remove completely empty root inventory
folders might help make this situation better, but it involves a fairly
complex mysql query that is currently beyond my abilities. I am hoping
someone could help out a little here with a query that can be used to identify
multiple root inventory folders in a grids mysql database and a query to
would allow them to be deleted, perhaps one by one, that would be fine.<br>
<br>
This query involves finding all those avatars with inventoryfolders entries
where more then one parentFolderID is zeroes.<br>
<br>