aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Data/MySQL/Resources (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' into careminsterMelanie2012-01-241-12/+3
|\ | | | | | | | | | | Conflicts: OpenSim/Data/MySQL/MySQLSimulationData.cs OpenSim/Framework/RegionSettings.cs
| * 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.
* | Merge branch 'master' into careminsterMelanie2012-01-221-1/+25
|\ \ | |/ | | | | | | Conflicts: OpenSim/Framework/RegionSettings.cs
| * Change the key name I missed in last commitMelanie2012-01-221-1/+1
| |
| * Move Telehub tables and data from EstateSettings to RegionSettings.Melanie2012-01-222-22/+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.
| * Telehub Support:BlueWall2012-01-211-0/+21
| | | | | | | | 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.
* | Merge commit 'aadf7dd91cdeb98b48cd81c5db06481593aff993' into bigmergeMelanie2011-10-111-23/+0
|\ \ | |/
| * Remove vestigal OpenSim.Data mono addins extension points that don't look ↵Justin Clark-Casey (justincc)2011-09-201-23/+0
| | | | | | | | like they've been active for at least 2 and a half years
* | Merge branch 'master' into careminster-presence-refactorMelanie2011-06-131-1/+1
|\ \ | |/
| * Switched order of SQL statements in Friends migration -- resulted in the ↵Diva Canto2011-06-111-1/+1
| | | | | | | | wrong key
* | Merge branch 'master' into careminster-presence-refactorMelanie2011-06-111-0/+16
|\ \ | |/
| * 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.
* | Merge branch 'master' into careminster-presence-refactorMelanie2011-06-091-0/+7
|\ \ | |/
| * 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.
| * HG Friends working to some extent: friendships offered and accepted ↵Diva Canto2011-05-191-0/+6
| | | | | | | | correctly handled. Friends list showing correct foreign names. TODO: GrantRights.
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-12-061-0/+7
|\ \ | |/
| * Fixed some inconsistency with trailing /. Made debug messages consistent. ↵Diva Canto2010-12-051-0/+7
| | | | | | | | Changed the stored region names of HG regions. Increased the size of regionName in DB.
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-11-222-0/+17
|\ \ | |/
| * Added creator info across the board -- TaskInventoryItems and InventoryItems ↵Diva Canto2010-11-212-0/+9
| | | | | | | | | | | | 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.
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-11-021-0/+8
|\ \ | |/
| * Fix logins and avatar appearance. Contains a Migration. May contain nuts.Melanie2010-10-301-0/+8
| | | | | | | | | | | | This will cause visual params to be persisted along with worn items. With this, alpha and tattoo laters will be saved. Multiple layers MAY work, but not tested because I don't use Viewer 2.
| * Bump migration version on LastSeen field so it is actually runMelanie2010-10-181-1/+1
| |
| * Ensure no UUID.Zero region ID is ever written to presence. Add a MigrationMelanie Thielker2010-10-131-0/+8
| | | | | | | | to add a LastSeen field of type "Timestamp" to Presence for MySQL
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-08-301-2/+12
|\ \ | |/
| * 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>
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-08-061-1/+8
|\ \ | |/
| * add mysql support for media on a primJustin Clark-Casey (justincc)2010-07-261-1/+8
| |
* | Bump the migration version, ot it would never happenMelanie Thielker2010-06-211-1/+1
| |
* | Ensure no UUID.Zero region ID is ever written to presence. Add a MigrationMelanie Thielker2010-06-211-0/+8
| | | | | | | | to add a LastSeen field of type "Timestamp" to Presence for MySQL
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-06-161-2/+0
|\ \ | |/
| * * 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.
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-06-092-1/+9
|\ \ | |/
| * 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
| |
| * * Changed CreatorIDs consistently to varchar(128)Diva Canto2010-06-082-1/+9
| | | | | | | | | | * Deleted redundant migration for assets in SQLite * Rewrote XInventory migrations in SQLite in the new style
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-06-081-0/+6
|\ \ | |/
| * Add a migration to adjust types in the WL table. The new connector likes thatMelanie2010-06-081-0/+6
| | | | | | | | better
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-05-262-78/+81
|\ \ | |/
| * Merge branch 'unitests'Melanie2010-05-262-84/+81
| |\ | | | | | | | | | Signed-off-by: Melanie <melanie@t-data.com>
| | * MySQL Migrations: Minor correcton to Region/Estate splitAlexRa2010-05-232-6/+12
| | | | | | | | | | | | (some Estate SQL left behind in the Region migration)
| | * Split migrations for RegionStore and EstateStore (see WARNING!)AlexRa2010-05-232-78/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Merge branch 'master' into careminster-presence-refactorMelanie2010-05-241-1/+1
|\ \ \ | |/ /
| * | The 8th migration statement in AssetStore.migrations didn't look right.Diva Canto2010-05-231-1/+1
| |/
* | Merge branch 'master' into careminster-presence-refactorMelanie2010-05-2180-1066/+1275
|\ \ | |/
| * Cleaned up MySql migrations a bit more, got rid of all old-form migration ↵Diva Canto2010-05-205-32/+8
| | | | | | | | files. Restored Presence table to its taboo-breaking form.
| * MySQL: added CreatorID, moved asset_flag to migration scriptAlexRa2010-05-191-0/+8
| |
| * Converted MySQL migration history to the new formatAlexRa2010-05-1678-1002/+1228
| | | | | | | | | | Replaced all NNN_StoreName.sql migration resources with a more readable, single-file-per-store