Database Documentation (MySQL only)
From OpenSimulator
 |
Languages: |
|
|
|
This article or section contains obsolete and possibly misleading information. Please integrate this information into existing pages, update it to something more recent, or remove it. |
This is a running start at documenting the tables in the MySQL instances used on both grid and regions, and describing how they relate to each other in the context of an OpenSim grid.
SQLite is generally not apropriate for this use case and will not be covered here; however the table structures are very similar and most of what is here will be useful in that context as well.
Note that some of these tables may be artifacts, some may be planned for use, and some may see heavy use but have columns which are artifacts, not properly updated or not yet used at all. Alpha code FTW!! :D
-daTwitch aka Hiro Protagonist
The instances:
| Grid: | |
| agents | Records agent (Avatar/User) login details |
| assets | Comprehensive grid assets including textures and avatar inventories |
| avatarappearance | Persistence of the visual appearance of avatars between logins |
| inventoryfolders | Inventory folder-related details *excepting contents* |
| Contents are in the inventoryitems table and point back to inventoryfolders | |
| inventoryitems | All inventory item details (including folder associations) except contents - contents are referenced |
| in the assets table | |
| logs | Stores a record of logged events |
| logs_preTimestamp | Old format logs table? |
| migrations | Supports 'automagic' migration to new database formats |
| regions | Regions known to the grid |
| reservations | Region registration table. This table has no rows on OSGrid and is likely in place for future functionality |
| userfriends | Friends list registration |
Region: estate_groups estate_managers estate_map estate_settings estate_users estateban land landaccesslist migrations primitems prims primshapes regionban regionsettings terrain
This is a brief snip from an IRC discussion that pretty much sums things up:
<daTwitch> my next question involves the use of the files in trunk/OpenSim/Data/MySQL/Resources/ <daTwitch> If I understand correctly, assuming at minimum a previously unused instance on the db, execution of CreateAssetsTable.sql on the sql server, followed by the application of the files 001_AssetStore.sql thru 004_AssetStore.sql (as it stands now) will produce a current assets backstore <daTwitch> and similarly for the other tables <daTwitch> is that a valid assumption? <justinccWork> yep <daTwitch> bitchin' dude :D <daTwitch> <3 <justinccWork> got it in one :) <daTwitch> Thanks Man :D
