aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Data (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Add 64 bit Windows sqlite3.dll and use this if running a 64-bit windows process.Justin Clark-Casey (justincc)2012-02-217-0/+20
|
* Parcel sales support to SQLiteBlueWall2012-02-172-1/+10
|
* Fillin missing SQLite support for TelehubsBlueWall2012-02-172-0/+118
|
* Fix: Lightshare Module(Windlight)-Region settings are not applicable for ↵PixelTomsen2012-02-142-305/+692
| | | | database sqlite mantis: http://opensimulator.org/mantis/view.php?id=5888
* Fix: MSSQLDB Grid - unable to register region ↵PixelTomsen2012-02-141-1/+8
| | | | http://opensimulator.org/mantis/view.php?id=5886
* Revert "Add GridStore migration for MSSQL."Justin Clark-Casey (justincc)2012-02-141-8/+0
| | | | This reverts commit 0b17a66e683f7ffca3877c1601c4179684b62144.
* Add GridStore migration for MSSQL.Justin Clark-Casey (justincc)2012-02-141-0/+8
| | | | This is done blind since I don't use MSSQL. If this doesn't work, then one will have to wait for it to be updated for the 0.7.3 opensim release.
* Fix: Unable to remove AV from friend list (sqldb-bug) ↵PixelTomsen2012-02-101-1/+1
| | | | http://opensimulator.org/mantis/view.php?id=3731
* Add default value to TelehubObjectBlueWall2012-02-041-0/+10
|
* Fix: Covenant changed time not set ↵PixelTomsen2012-02-036-8/+31
| | | | | | http://opensimulator.org/mantis/view.php?id=5869 Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
* Replace ParcelAccessEntry with a new struct, LandAccessEntry, which moreMelanie2012-02-024-20/+27
| | | | | | accurately reflects the data sent by the viewer. Add times bans and the expiration of timed bans. Warning: Contains a Migration (and nuts)
* Add the needed column in the regions table and a few tweaks.Melanie2012-01-301-0/+9
| | | | | Warning: Contains a Migration Warning: Cannot guarantee nut free
* Add ParcelImageID to RegionSettings so we can have that overlay.Melanie2012-01-302-2/+10
| | | | | Warning: Contains a Migration. Warning: May contain nuts.
* refactor: change RezScriptFromAgentInventory(), RezNewScript() and ↵Justin Clark-Casey (justincc)2012-01-261-6/+6
| | | | | | AddInventoryItem() to accept an agent id rather than a full IClientAPI. This stops some code having to make spurious client == null checks and reduces regression test complexity.
* Add a forgotten parameterMelanie2012-01-241-1/+1
|
* Change Telehubs to store only the data that is really needed and notMelanie2012-01-241-40/+13
| | | | additional redundant information.
* IMPORTANT!!!!! Please READ. DO NOT Use this version or any before it since theMelanie2012-01-231-12/+3
| | | | | | Telehub commits! They will eat your babies and corrupt your database while they munch. DO NOT use anything from the first Telehub commit to this one. FIRST GOOD COMMIT is the one FOLLOWING this one. You have been warned.
* Fix up some parameter namingMelanie2012-01-221-2/+2
|
* Finish connecting Telehub to databaseBlueWall2012-01-221-3/+19
|
* Hooking up new telehub data to the databaseBlueWall2012-01-221-0/+14
|
* Change the key name I missed in last commitMelanie2012-01-221-1/+1
|
* Move Telehub tables and data from EstateSettings to RegionSettings.Melanie2012-01-224-87/+95
| | | | | | | | | | This is damage control es EstateSettings is not the place this can be put. EstateSettings is nt unique to a region and therefore would introduce a hard limit of one telehub per estate, completely shutting off the option of having SL style telehubs, e.g. one per region. Whole estate teleport routing can still be implemented id desiresd, this way all options are open while the other way most options get closed off.
* Telehub Support:BlueWall2012-01-212-1/+86
| | | | Telehub settings now persist to the database and are saved across sim restarts. So-far this only works on MySQL. this is a work in progress, teleport routing is not yet implemented.
* Add beginning of ScenePresenceAgentTests.TestCreateChildScenePresence()Justin Clark-Casey (justincc)2011-12-031-9/+31
| | | | | This required an option to be added to NullRegionData via ConnectionString for it to act as a non-static instance, so that regression tests (which only load this class once) don't get hopeless confused and complex to compensate. Normal standalone operation unaffected.
* Get rid of the spurious [WEB UTIL] couldn't decode <OpenSim agent ↵Justin Clark-Casey (justincc)2011-11-191-2/+2
| | | | | | | 57956c4b-ff2e-4fc1-9995-613c6256cc98>: Invalid character 'O' in input string messages These are just the result of an attempt to canonicalize received messages - it's not important that we constantly log them. Also finally get the deregister grid service message working properly
* Remove mono compiler warnings. Fix problem with co-ordinate given in ↵Justin Clark-Casey (justincc)2011-11-191-5/+5
| | | | deregister region message
* Improve some grid region log messages to express regions at co-ordinate ↵Justin Clark-Casey (justincc)2011-11-191-0/+20
| | | | (e.g. 1000, 1000) rather than meter positions (256000, 256000)
* Add test for adding a friend whilst onlineJustin Clark-Casey (justincc)2011-11-141-1/+9
|
* Changes UpdateFlag in SOP to an enumeration of NONE, TERSE and FULL.Dan Lake2011-11-021-5/+0
| | | | | | | | | | | | | | | | | UpdateFlag is now referenced/used only within SOP and SOG. Outsiders are using ScheduleFullUpdate, ScheduleTerseUpdate or ClearUpdateSchedule on SOP consistently now. Also started working toward eliminating those calls to ScheduleFullUpdate, ScheduleTerseUpdate or ClearUpdateSchedule from outside SOP in favor of just setting properties on SOP and let SOP decide if an update should be scheduled. This consolidates the update policy within SOP and the client rather than everywhere that makes changes to SOP. Some places forget to call update while others call it multiple times, "just to be sure". UpdateFlag and Schedule*Update will both be made private shortly. UpdateFlag is intended to be transient and internal to SOP so it has been removed from XML serializer for SOPs.
* Plug a security hole in the inventory serviceMelanie2011-10-311-1/+2
|
* Null simulation data must return a non-null region settings or other parts ↵Dan Lake2011-09-201-2/+4
| | | | of the simulator expect
* Remove vestigal OpenSim.Data mono addins extension points that don't look ↵Justin Clark-Casey (justincc)2011-09-203-66/+0
| | | | like they've been active for at least 2 and a half years
* MSSQL Bug fix in user account retrieval, plus migrations for FriendsStore ↵Chris Hart2011-09-163-7/+71
| | | | and InventoryStore
* Reattaching a region was failing if the estate name had not changed (issue ↵Kevin Houlihan2011-09-164-140/+231
| | | | | | 5035). Using the RemoteAdmin API to close then recreate a region would fail if the estate name had not changed. If the estate name /was/ changed then the existing estate would be renamed rather than a new one being created. The problem really arose from a lack of distinction in the data storage layer between creating new estates and loading existing ones.
* Fix unit tests from RegionSettings commitJustin Clark-Casey (justincc)2011-09-091-0/+4
|
* Save the default terrain texture UUIDs for a new region instead of leaving ↵Justin Clark-Casey (justincc)2011-09-091-1/+0
| | | | | | | | | | | them as UUID.Zero. Leaving them at UUID.Zero meant that when a viewer 2 logged into a region that had been freshly created, it received UUID.Zero for these textures, and hence display the land as plain white. On a simulator restart, the problem would go away since when the database adapators loaded the new region settings, RegionSettings itself has code to use default textures instead of UUID.Zero. This commit resolves the problem by saving the default texture UUIDs instead of Zero. However, we currently have to do this in a roundabout way by resaving once the RegionSettings have been created by the database for the first time. This needless complexity should be addressed. This change will also have the effect of replacing any existing UUID.Zero terrain textures with the default ones. However, this shouldn't have any effect since the UUID.Zeros were already being replaced in memory with those same UUIDs.
* Remove code which was automatically deleting non-root prims from scene ↵Justin Clark-Casey (justincc)2011-09-012-32/+0
| | | | | | | objects that had previous been attachments. Looks like this code was accidentally uncommented in e1b5c612 from feb 2010. Appears to resolve the rest of http://opensimulator.org/mantis/view.php?id=5664
* minor: remove mono compiler warningJustin Clark-Casey (justincc)2011-08-311-1/+1
|
* refactor: move SOP.IsAttachment and AttachmentPoint up into SOG to avoid ↵Justin Clark-Casey (justincc)2011-08-271-4/+2
| | | | pointless duplication of identical values
* minor: remove some mono compiler warningsJustin Clark-Casey (justincc)2011-08-182-2/+2
|
* In the asset service, check that an asset exists before attempting to store it.Justin Clark-Casey (justincc)2011-08-171-2/+7
|
* Remove un-needed ATTACH command in migration script.BlueWall2011-08-151-3/+1
| | | | | | This was causing issues when using specified paths to database files by using a hard-coded name.
* minor: a little bit of log message correction/commenting outJustin Clark-Casey (justincc)2011-08-111-1/+1
|
* rename TestHelper => TestHelpers for consistencyJustin Clark-Casey (justincc)2011-08-064-44/+44
|
* refactor: Pull up Assembly of the SQLite classes as a protected property, so ↵Marck2011-07-166-11/+32
| | | | that it can be overwritten in subclasses. That way extensions can decide in which assembly migration resources should be looked up. This is a refactor similar to commit 9923a2ff1002d722ccebea8bf4d71718ed4e2a03 for MySQL -- no functional changes.
* Switched order of SQL statements in Friends migration -- resulted in the ↵Diva Canto2011-06-111-1/+1
| | | | wrong key
* For MySQL, migrate region tables to the MyISAM storage engine rather than InnoDBJustin Clark-Casey (justincc)2011-06-101-0/+16
| | | | | | | | Using MyISAM proves vastly faster for persisting scene objects. For instance, a scene object that took 9 seconds to persist before now takes 1. This also improves the experience of loading large OARs. We don't use any of the transactional features of InnoDB. The only thing that may have an impact is that InnoDB does row locking on inserts while MyISAM does table locking. However, field reports say there is no noticeable difference.
* This is the better solution: make the combined key be only on the first 36 ↵Diva Canto2011-06-011-1/+2
| | | | characters of each field -- that's the UUIDs. Thanks coyled. WARNING: Again, people who have gone through this migration and failed need to run it manually.
* It looks like there's a better solution for that problem.Diva Canto2011-06-011-2/+1
| | | | | | Revert "Changed Friends table to have 165-sized varchars on PrincipalID and FriendID. The reason for this number is the following: there is a combined key of these 2 fields; apparently MySql can't handle keys larger than 1000 bytes; when the table is created with utf8 encoding, this combined key is bigger than 1000 bytes, and the migration fails. WARNING: this is not a new migration! People who have gone through this migration and failed should update the sizes of these fields manually." This reverts commit 3fa54a156a83e498a7d5d0949a5f848fe82fe86f.
* Changed Friends table to have 165-sized varchars on PrincipalID and ↵Diva Canto2011-06-011-1/+2
| | | | FriendID. The reason for this number is the following: there is a combined key of these 2 fields; apparently MySql can't handle keys larger than 1000 bytes; when the table is created with utf8 encoding, this combined key is bigger than 1000 bytes, and the migration fails. WARNING: this is not a new migration! People who have gone through this migration and failed should update the sizes of these fields manually.