aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Data/MySQL/Resources/RegionStore.migrations (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Partial port of Avination's support for the new physics parameters.Melanie2013-02-061-0/+13
| | | | | | | | Implements the parameters as properties, the serialization and database storage (MySQL only). Implements llSetPrimitiveParams for prim physics shape and the other 4 extra params. Only the prim shape type "None" is currently functional. No support for the Viewer UI (yet), that will be ported in due course. Lots more to port, this is a large-ish changeset.
* Stopped storing dynamic attributes in the PrimShapeOren Hurvitz2013-01-251-1/+0
|
* Implement dynamic attribute persistence on mysql and mssqlJustin Clark-Casey (justincc)2013-01-251-0/+9
| | | | mssql is untested
* Add a skeleton for a name value storage associated with regionsMelanie2012-08-151-0/+7
|
* Environment Module - allows Environment settings for Viewer3 warning: ↵PixelTomsen2012-05-231-0/+11
| | | | | | | | | | | | | includes database region store migrations for mssql, mysql, sqlite enable/disable this module: Cap_EnvironmentSettings = "localhost" (for enable) Cap_EnvironmentSettings = "" (for disable) at ClientStack.LindenCaps section (OpenSimDefaults.ini file) or owerwrite in OpenSim.ini mantis: http://opensimulator.org/mantis/view.php?id=5860 Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
* Add default value to TelehubObjectBlueWall2012-02-041-0/+10
|
* Fix: Covenant changed time not set ↵PixelTomsen2012-02-031-0/+5
| | | | | | 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-021-0/+6
| | | | | | accurately reflects the data sent by the viewer. Add times bans and the expiration of timed bans. Warning: Contains a Migration (and nuts)
* Add ParcelImageID to RegionSettings so we can have that overlay.Melanie2012-01-301-0/+6
| | | | | Warning: Contains a Migration. Warning: May contain nuts.
* 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.
* Change the key name I missed in last commitMelanie2012-01-221-1/+1
|
* Move Telehub tables and data from EstateSettings to RegionSettings.Melanie2012-01-221-1/+25
| | | | | | | | | | 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.
* 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.
* Added creator info across the board -- TaskInventoryItems and InventoryItems ↵Diva Canto2010-11-211-0/+1
| | | | | | themselves. Tested. Seems to be working, main tests pass. Nothing done for IARs or HG transfers yet -- this only works for OARs for the time being. New migration in inventory table in order to make CreatorID varchar(255).
* Global creator information working on MySQL DB and on load/save OARs. ↵Diva Canto2010-11-211-0/+8
| | | | | | | Creator name properly shown on the viewer as first.last @authority. New option added to save oar -profile=url. Migration on RegionStore making CreatorID be 255 chars. Moved Handling of user UUID -> name requests to a new module UserManagement/UserManagementModule.
* Implements parcel media setting persistence and packet / CAPS handlingJonathan Freedman2010-08-301-2/+12
| | | | | | properly for the new media settings. Signed-off-by: Melanie <melanie@t-data.com>
* add mysql support for media on a primJustin Clark-Casey (justincc)2010-07-261-1/+8
|
* * Deleted duplicated migration that was failing anyway.Diva Canto2010-06-141-2/+0
| | | | * Added an error message in initial estate owner creation that makes it clear what needs to happen.
* Add the BEGIN; I had missedMelanie2010-06-091-0/+1
|
* Re-add Migration version 32, which apparently got dropped completely.Melanie2010-06-091-0/+72
|
* Add a migration to adjust types in the WL table. The new connector likes thatMelanie2010-06-081-0/+6
| | | | better
* MySQL Migrations: Minor correcton to Region/Estate splitAlexRa2010-05-231-6/+0
| | | | (some Estate SQL left behind in the Region migration)
* Split migrations for RegionStore and EstateStore (see WARNING!)AlexRa2010-05-231-78/+0
| | | | | | | | | | | | ok, so the estate stores now want their own migration files, but as it happened the SQL definition were inside the Region migrations. It seems better/cleaner to keep each 'store' separately updatable. WARNING: any editing in the middle of the migration scripts (as opposite to just appending to them) has the potential of messing up updates of existing databases. As far as I can see, this one is (probably) safe, the worst that could happen is the EstateStore migration silently fail if the estate the tables are already there.
* Cleaned up MySql migrations a bit more, got rid of all old-form migration ↵Diva Canto2010-05-201-1/+4
| | | | files. Restored Presence table to its taboo-breaking form.
* Converted MySQL migration history to the new formatAlexRa2010-05-161-0/+806
Replaced all NNN_StoreName.sql migration resources with a more readable, single-file-per-store